The OpenURL Framework for the Context- sensitive Provision of Service Links Herbert Van de Sompel...
-
Upload
rosaline-noreen-hicks -
Category
Documents
-
view
224 -
download
2
Transcript of The OpenURL Framework for the Context- sensitive Provision of Service Links Herbert Van de Sompel...
The OpenURL Framework for the Context-sensitive Provision of Service Links
Herbert Van de SompelCornell University -- Computer Science
Emory University – June 11th 2001
Problem statement
• context: web-based scholalry information environment• concepts:
• reference links / extended service links• closed and non-context sensitive linking frameworks
herbert van de sompel
OPAC
web-based scholarly information
FTXT
FTXTe-printA&I
A&I
distributed
herbert van de sompel
OPAC
web-based scholarly information
FTXT
FTXTe-printA&I
A&I
range of authorities, technologies
herbert van de sompel
OPAC
web-based scholarly information
FTXT
FTXTe-printA&I
A&I
¡¡ challenges re integrated access !!
herbert van de sompel
OPAC
linking
FTXT
FTXTe-printA&I
A&I
interlink related information
herbert van de sompel
reference links
extended services
full text
reference links
full text
reference links
full text
Ulrich’s
citation databases
extended services
Medline
Who is Who
Books in Print
Amazon.com
extended services
linking frameworks: problems
not context-sensitive
herbert van de sompel
appropriate
full text
Inspec
citation databases
contextualize extended services
linking frameworks: problems
not context-sensitive
limited scope • business agreements• type of extended services
closed • do not allow for compensation of the problems
herbert van de sompel
A solution: the OpenURL framework
• concepts:
• disconnecting metadata from services
• introduce overlaying service components
• the OpenURL as an interoperability specification
• the OpenURL
metadata planeresource1
resource2 resource3
default links
herbert van de sompel
metadata plane
extended services plane
resource1
servicecomponent1
servicecomponent2
default links
appropriate links
Ope
nURL
resource2 resource3
herbert van de sompel
the OpenURL framework
FTXT
FTXT
A&I
localservice
component
OpenURL
OpenURLO
penU
RL O
penUR
L
• by value or by reference delivery of metadata on users’ request
• linking server • describes context
herbert van de sompel
OPAC
):-search
resultOpenURL
otherdbase
fetch metadata
)
the OpenURL framework
A&I
localservice
component
herbert van de sompel
OpenURL example
service component http://sfx.aaa.edu/menu
AU Smith, Paul ISSN 1234-5678VOLUME 12ISSUE 3PAGES 1-8PY 1998DBASE ERL-BIOSISDBASE-AN 987641
record in A&I
herbert van de sompel
OpenURL example
http://sfx.aaa.edu/menu?genre=article&issn=1234-5678&volume=12&issue=3&spage=1&epage=8&date=1998&aulast=Smith&aufirst=Paul
OpenURL
http://sfx.aaa.edu/menu?mpt=http://erl.rug.ac.be/gate?db=biosis&id=987641
OpenURL
herbert van de sompel
An open issue in the OpenURL framework
• matching a user with a service component
• pragmatic solutions
• user profiles
• cookiepusher
• IP-address based
Deployment of OpenURL framework
• draft OpenURL specs early 2000
• lots of interest from libraries, information providers
• adopted by important information providers
• OpenURL fast track NISO standardization 2001
• SFX server marketed by Ex Libris
• DOI/CrossRef prototype: integration with OpenURL
Alternative resolution of identifiers & OpenURL framework
proxy handle url
herbert van de sompel
doi link
user clicks
OpenURL
aware
proxy handle
doi
metadata
herbert van de sompel
doi link
user clicks
servicesuser gets
localservice
component
What’s next: alternative resolution of descriptors
Extend the OpenURL framework:
• from scholarly information objects to entities in general
• from scholarly subsection of the Web to the Web
demo? questions?
• notion of resolution system really only exists for an identifier/name
• OpenURL framework: • can ask for services using both metadata and identifiers as input to the service component• this can be regarded as the resolution of metadata and identifiers into services
what’s next?
• extend identifier to descriptor
• descriptor describes an entity by means of:• identifiers of the entity• identifiers of metadata of the entity• metadata for the entity• pointers to metadata for the entity
• open linking: resolve descriptors into services via service components
what’s next?
• more information is required than only the descriptor of the entity for which one wants services
• ContextObject contains descriptors for:• entity for which services are required• refering entity • refering resource• requestor of services• service component - resolver
what’s next?
1. implement a technique to make a resource understand the difference between a user that has access to a service component and one that does not
OpenURL-awareness
herbert van de sompel
1. CookiePusher, user-profiles, DLF certificate, ...
OpenURL-awareness
herbert van de sompel
2. for users with access to a service component, provide an OpenURL for each transported metadata-object
OpenURL-awareness
herbert van de sompel
2. OpenURL:target = service componentcontent = elements of the metadata, in a public syntax
OpenURL-awareness
http://www.sfxit.com/OpenURL
herbert van de sompel
link = http://dx.doi.org/10.1000/6382-1
OpenURL examples
OpenURL =http://sfx.aaa.edu/menu?id=doi:10.1000/6382-1
service component = http://sfx.aaa.edu/menu
OpenURL status
OpenURL => NISO
herbert van de sompel
Firm commitment to OpenURL
• EBSCO.
• ISI. Web of Science v4.03 due for release in Q4.
• Institue Of Physics Publishing. Available now.
• SilverPlatter (WebSPIRS 5 - 2001. A solution is available today)
• Los Alamos e-print ArXiv. Available now.
• SLAC/SPIRES (high-energy physics – Stanford). Available now.
OpenURL status
Partial commitment to OpenURL
a. Participation in SFX beta test: OCLC First Search & Ovid
b. Other
• Cambridge Scientific Abstracts. Implementation soon.
• ProQuest/Bell+Howell. Plans to implement by end of 2000. Work is underway).
• DOI/CrossRef. Experiments (Includes 44 Primary Publishers).
OpenURL status
OpenURL implementation under discussion
• Gale Group
• InfoTrieve
• RoweCom
• Swets
• NorthernLight
• Ingenta
OpenURL status
Part 2: specific
the delivery of localized extended services
• the SFX software
herbert van de sompel
OPAC
the SFX server
FTXT
FTXT
A&I
OpenURL
OpenURLO
penU
RL O
penUR
L
• one of many possible service components• currently in beta
herbert van de sompel
1. accept OpenURL as input
the SFX server
2. collect object-metadata: • from the OpenURL [OpenURL parser]• via fetch from a resource [SourceParsers]:
• per sid & per namespace• http, z39.50, OAI interface, ... fetch• parsing of reply• configuration via table
the SFX server
3. augment object-metadata
the SFX server
the SFX server
4. compute relevant localized extended services [SFX database]
definition of potential services
information about the local collection
rules supporting a decision on the relevance of services
SFX database
BIOSISarXivAPS/PROLAInspecCompendex
SOURCES
MedlineInspecSpringerSci Cit BasOPAC
TARGETS
get_holdingsget_abstractget_full_textcited_author
SERVICES
OBJECTS
1234-56783456-87659876-43212389-6734
THRESHOLDS
TARGETS
MEDLINE requests:getFullTxtgetTOCgetAuthorgetCitedAuthorgetAbstractgetWebServicegetCitedReferencegetCitedJournal
Springer provides: getFullTxt, getTOC
BIOSIS provides:getAuthor, getAbstract
Wiley provides:getFullTxt, getTOC
WWW Search Engines provides:
getWebService
Web of Science provides:getCitedReference
getCitedAuthorgetAuthor
SOURCES
conceptual links that will be formed
(for real)if certain
requirements (Thresholds)
are met …
COLLI
the SFX server
5. compute service-links [TargetParsers]
• Per Target/Service
tools for SFX-configuration
• SFXCTRL: • a graphical interface for configuring:
• Sources• Targets • Services [where Sources and Targets meet]
• and for making small-scale edits to the SFX-base• TEMPLATES: basic, generic, flexible pre-configurations• SFXLOADER: a tool for object administration• STATISTICAL measures
Sources
• Where a user is coming from, beginning a search• Examples:
• OPAC• A&I database• Online journal
• Sources must be OpenURL-enabled!
Librarian must decide what Sources are available in the library environment and what Services would be desired by users.
Targets & Target/Services
• Where a user “lands”• Services are the facilities:
• A getAuthor service would run a search in a target on an author’s name
• A getFullTxt service would link to the full text of a particular article from a Target publisher
• Targets must have a link-to syntax that supports the Service
Threshold administration
• Thresholds aid in the process of evaluating the appropriateness of delivering a real link based on a conceptual link:• Objects: ISSN numbers in an A&I database• Rules: metadata needs an ISBN number
Templates
• Material to support typical or generic scenarios• Contain: services, parsers, objects and thresholds• Constantly updated and distributed by Ex Libris• Subscribing library “localizes” to match library’s
subscriptions and conditions
http://www.sfxit.com ; brochures in back
demos
http://www.sfxit.com/OpenURL
http://sfxserv.rug.ac.be:8888/public/xref/DOI experiment
http://www.sfxit.com/sources.htmlSources
http://www.sfxit.com/targets.htmlTargets
http://www.dlib.orgreading
CrossRef
DOI - CrossRef - OpenURL – SFX experiment
http://sfxserv.rug.ac.be:8888/public/xref/