Sirsi Resolver at the University of Leicester

1

• Sirsi Resolver at the University of Leicester

Jonathan Field Sept 3rd, 2004 EUUG, Amsterdam
2
An overview of OpenURL Resolution

• OpenURL is a syntax for URLs
• OpenURL embeds metadata like ISSN, journal title,
  article title, etc.
• More and more vendors are using the OpenURL
  standard
• OpenURL Resolution maximize your investment in
  E-Resources, because they bring users in contact
  with resources

3
What are the pieces that make up an OpenURL?

• The OpenURL includes a base URL plus a query,
  which contains the metadata for the item
• The OpenURL may include DOI (digital object
  identifiers) or other unique identification
  numbers

4
What does an OpenURL look like?

• Below is an example of an OpenURL
• http//somedatabase.vendor.com/ represents the
  base URL
• The remainder of the OpenURL includes the
  querymenu?genrearticleissn12345678volume15
  issue6date20010908spage67aufirstIvanaaul
  astReedabook

http//somedatabase.vendor.com/menu?genrearticle
issn12345678volume15issue6date20010908 sp
age67aufirstIvanaaulastReedabook
5
Sounds great!

• And it is, but, its out of our control
• The vendors are determining where these links are
  going
• The patron sees a link to the full text, but
  then gets led to a database that the library does
  not subscribe to

6
(No Transcript)
7
(No Transcript)
8
What does a link resovler do?

• Link resolvers allow us to control where the
  OpenURL ultimately resolves
• The OpenURL passes through the link resolver, i.e
  the Sirsi Resolver
• The Resolver returns a menu of choices, based on
  the resources that the library has defined as
  their profile within the Knowledgebase, i.e where
  the full text, or appropriate copy of the item
  may be found

9
Search of Database A
Citation
LinkResolver
Publishers site
Database
Database
OPAC
ILL request form
10
Customer Profile example in Sirsis Resolver
Knowledgebase
11
Citation Reedabook, Ivana. How do link
resolvers actually work? Better Research
Quarterly, Vol. 13 (1992) No. 6, pp. 65-71
Better Research Quarterly Holdings Info
12
Lets See it in Action!

• Search
• Retrieve
• Resolve
• Receive

13
Lets See it in Action!

• Lets start the users exploration in the
  Leicester Geology Room

14
Lets See it in Action!

• Search

15
(No Transcript)
16
Lets See it in Action!

• Receive

17
(No Transcript)
18
Lets See it in Action!

• Resolve

19
(No Transcript)
20
Lets See it in Action!

• Receive

21
(No Transcript)
22
Lets See it in Action!

• Lets see it again, but this time with the user
  starting from the OPAC

23
Lets See it in Action!

• Search

24
(No Transcript)
25
Lets See it in Action!

• Retrieve

26
(No Transcript)
27
Lets See it in Action!

• Resolve

28
(No Transcript)
29
Lets See it in Action!

• Receive

30
(No Transcript)
31
Lets See it in Action!

• One last time. Lets say the user knows the
  article they want, and has the issue information
  in hand.

32
Lets See it in Action!

• Search

33
(No Transcript)
34
Lets See it in Action!

• Receive

35
(No Transcript)
36
Lets See it in Action!

• Ok, one more How about integrating local print
  holdings into the knowledge base? Lets say the
  user starts in the A-Z List

37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
Lets See it in Action!

• Fibbed again What if the user starts in the
  vendors native interface?

41
(No Transcript)
42
(No Transcript)
43

• Sirsi Resolver at the University of Leicester

Jonathan Field Sept 3rd, 2004 EUUG, Amsterdam