570 likes | 694 Views
The OpenURL Framework for the Context-sensitive Provision of Service Links. H erbert V an de S ompel Cornell University -- Computer Science. Emory University – June 11th 2001. Problem statement context: web-based scholalry information environment concepts:
E N D
The OpenURL Framework for the Context-sensitive Provision of Service Links Herbert Van de Sompel Cornell 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 FTXT FTXT e-print A&I A&I web-based scholarly information distributed herbert van de sompel
OPAC FTXT FTXT e-print A&I A&I web-based scholarly information range of authorities, technologies herbert van de sompel
OPAC FTXT FTXT e-print A&I A&I web-based scholarly information ¡¡challenges re integrated access !! herbert van de sompel
OPAC FTXT FTXT e-print A&I A&I linking interlink related information herbert van de sompel
reference links extended services
full text reference links
full text reference links
citation databases Ulrich’s full text Medline extended services
Who is Who Books in Print Amazon.com extended services
not context-sensitive linking frameworks: problems herbert van de sompel
appropriate full text Inspec citation databases contextualize extended services
business agreements • type of extended • services not context-sensitive limited scope closed • do not allow for compensation of the problems linking frameworks: 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
default links resource2 resource3 resource1 metadata plane herbert van de sompel
appropriate links OpenURL default links extended services plane service component1 service component2 resource2 resource3 resource1 metadata plane herbert van de sompel
OpenURL • by value or by reference • delivery of metadata on • users’ request FTXT FTXT A&I OPAC local service component OpenURL OpenURL OpenURL • linking server • describes context the OpenURL framework herbert van de sompel
) A&I :- local service component fetch metadata other dbase the OpenURL framework search ) result OpenURL herbert van de sompel
record in A&I AU Smith, Paul ISSN 1234-5678 VOLUME 12 ISSUE 3 PAGES 1-8 PY 1998 DBASE ERL-BIOSIS DBASE-AN 987641 OpenURL example service component http://sfx.aaa.edu/menu herbert van de sompel
OpenURL 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 example 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
user clicks doi link proxy handle url herbert van de sompel
OpenURL user clicks doi link proxy handle aware user gets services local service component metadata doi herbert van de sompel
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
what’s next? • 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
OpenURL-awareness 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 herbert van de sompel
OpenURL-awareness 1. CookiePusher, user-profiles, DLF certificate, ... herbert van de sompel
OpenURL-awareness 2. for users with access to a service component, provide an OpenURL for each transported metadata-object herbert van de sompel
OpenURL-awareness 2.OpenURL: target = service component content = elements of the metadata, in a public syntax http://www.sfxit.com/OpenURL herbert van de sompel
OpenURL examples service component = http://sfx.aaa.edu/menu link = http://dx.doi.org/10.1000/6382-1 OpenURL = http://sfx.aaa.edu/menu?id=doi:10.1000/6382-1
OpenURL status OpenURL => NISO herbert van de sompel
OpenURL status • 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. Implementationsoon. • ProQuest/Bell+Howell. Plans to implement by end of 2000. Work isunderway). • DOI/CrossRef. Experiments (Includes 44 Primary Publishers).
OpenURL status • OpenURL implementation under discussion • GaleGroup • InfoTrieve • RoweCom • Swets • NorthernLight • Ingenta
Part 2: specific • the delivery of localized extended services • the SFX software herbert van de sompel
OpenURL OPAC FTXT FTXT A&I OpenURL OpenURL • one of many possible service components • currently in beta OpenURL the SFX server herbert van de sompel
the SFX server 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 4.compute relevant localized extended services [SFX database]
SFX database definition of potential services information about the local collection rules supporting a decision on the relevance of services
SOURCES SERVICES TARGETS BIOSIS arXiv APS/PROLA Inspec Compendex Medline Inspec Springer Sci Cit Bas OPAC get_holdings get_abstractget_full_text cited_author OBJECTS 1234-5678 3456-8765 9876-4321 2389-6734 THRESHOLDS
conceptual links that will be formed (for real) if certain requirements (Thresholds) are met … COLLI TARGETS SOURCES Springer provides: getFullTxt, getTOC MEDLINE requests: getFullTxt getTOC getAuthor getCitedAuthor getAbstract getWebService getCitedReference getCitedJournal BIOSIS provides: getAuthor, getAbstract Wiley provides: getFullTxt, getTOC WWW Search Engines provides: getWebService Web of Science provides: getCitedReference getCitedAuthor getAuthor
the SFX server • 5.compute service-links • [TargetParsers] • Per Target/Service