The Open URL Framework for the Contextsensitive Provision

The Open. URL Framework for the Contextsensitive Provision of Service Links Herbert Van de Sompel Cornell University -- Computer Science Emory University – June 11 th 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

web-based scholarly information A&I e-print FTXT distributed OPAC herbert van de sompel FTXT A&I

web-based scholarly information A&I e-print FTXT range of authorities, technologies OPAC herbert van de sompel FTXT A&I

web-based scholarly information A&I e-print FTXT ¡¡ challenges re integrated access !! OPAC herbert van de sompel FTXT A&I

linking A&I e-print FTXT interlink related information OPAC herbert van de sompel FTXT A&I

reference links extended services

reference links full text

reference links full text

extended services citation databases Ulrich’s full text Medline

extended services Who is Who Books in Print Amazon. com

linking frameworks: problems not context-sensitive herbert van de sompel

citation databases contextualize extended services appropriate full text Inspec

linking frameworks: problems not context-sensitive limited scope closed herbert van de sompel • business agreements • type of extended services • do not allow for compensation of the problems

A solution: the Open. URL framework • concepts: • disconnecting metadata from services • introduce overlaying service components • the Open. URL as an interoperability specification • the Open. URL

resource 2 resource 3 default links resource 1 herbert van de sompel metadata plane

extended services plane app rop r iate Op en UR L service component 1 resource 2 service component 2 link s resource 3 default links resource 1 herbert van de sompel metadata plane

the Open. URL framework A&I • by value or by reference delivery of metadata on users’ request Open. URL OPAC local service component Open. URL • linking server • describes context FTXT herbert van de sompel FTXT

the Open. URL framework search A&I Open. URL result fetch metadata other dbase herbert van de sompel ) : - ) local service component

Open. URL example service component http: //sfx. aaa. edu/menu record in A&I AU ISSN VOLUME ISSUE PAGES PY DBASE-AN herbert van de sompel Smith, Paul 1234 -5678 12 3 1 -8 1998 ERL-BIOSIS 987641

Open. URL example Open. URL http: //sfx. aaa. edu/menu? genre=article&issn=12345678&volume=12&issue=3&spage=1&epage=8&d ate=1998&aulast=Smith&aufirst=Paul Open. URL http: //sfx. aaa. edu/menu? mpt=http: //erl. rug. ac. be/gat e? db=biosis&id=987641 herbert van de sompel

An open issue in the Open. URL framework • matching a user with a service component • pragmatic solutions • user profiles • cookiepusher • IP-address based

Deployment of Open. URL framework • draft Open. URL specs early 2000 • lots of interest from libraries, information providers • adopted by important information providers • Open. URL fast track NISO standardization 2001 • SFX server marketed by Ex Libris • DOI/Cross. Ref prototype: integration with Open. URL

Alternative resolution of identifiers & Open. URL framework

user clicks doi link herbert van de sompel proxy handle url

Open. URL user clicks doi link proxy handle aware user gets services metadata doi herbert van de sompel local service component

What’s next: alternative resolution of descriptors Extend the Open. URL framework: • from scholarly information objects to entities in general • from scholarly subsection of the Web to the Web

demo? questions?

what’s next? • notion of resolution system really only exists for an identifier/name • Open. URL 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 • Context. Object contains descriptors for: • entity for which services are required • refering entity • refering resource • requestor of services • service component - resolver

Open. URL-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

Open. URL-awareness 1. Cookie. Pusher, user-profiles, DLF certificate, . . . herbert van de sompel

Open. URL-awareness 2. for users with access to a service component, provide an Open. URL for each transported metadata-object herbert van de sompel

Open. URL-awareness 2. Open. URL: target = service component content = elements of the metadata, in a public syntax http: //www. sfxit. com/Open. URL herbert van de sompel

Open. URL examples service component = http: //sfx. aaa. edu/menu link = http: //dx. doi. org/10. 1000/6382 -1 Open. URL = http: //sfx. aaa. edu/menu? id=doi: 10. 1000/6382 -1

Open. URL status Open. URL => NISO herbert van de sompel

Open. URL status Firm commitment to Open. URL • EBSCO. • ISI. Web of Science v 4. 03 due for release in Q 4. • Institue Of Physics Publishing. Available now. • Silver. Platter (Web. SPIRS 5 - 2001. A solution is available today) • Los Alamos e-print Ar. Xiv. Available now. • SLAC/SPIRES (high-energy physics – Stanford). Available now.

Open. URL status Partial commitment to Open. URL a. Participation in SFX beta test: OCLC First Search & Ovid b. Other • Cambridge Scientific Abstracts. Implementation soon. • Pro. Quest/Bell+Howell. Plans to implement by end of 2000. Work is underway). • DOI/Cross. Ref. Experiments (Includes 44 Primary Publishers).

Open. URL status Open. URL implementation under discussion • Gale Group • Info. Trieve • Rowe. Com • Swets • Northern. Light • Ingenta

Part 2: specific the delivery of localized extended services • the SFX software herbert van de sompel

the SFX server A&I Open. URL OPAC Open. URL FTXT herbert van de sompel FTXT • one of many possible service components • currently in beta

the SFX server 1. accept Open. URL as input

the SFX server 2. collect object-metadata: • from the Open. URL [Open. URL parser] • via fetch from a resource [Source. Parsers]: • per sid & per namespace • http, z 39. 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 BIOSIS ar. Xiv APS/PROLA Inspec Compendex get_holdings get_abstract get_full_text cited_author TARGETS Medline Inspec Springer Sci Cit Bas OPAC OBJECTS 1234 -5678 3456 -8765 9876 -4321 2389 -6734 THRESHOLDS

SOURCES MEDLINE requests: get. Full. Txt get. TOC get. Author get. Cited. Author get. Abstract get. Web. Service get. Cited. Reference get. Cited. Journal COLLI TARGETS Springer provides: get. Full. Txt, get. TOC conceptual links that will be formed (for real) if certain requirements (Thresholds) are met … BIOSIS provides: get. Author, get. Abstract Wiley provides: get. Full. Txt, get. TOC WWW Search Engines provides: get. Web. Service Web of Science provides: get. Cited. Reference get. Cited. Author get. Author

the SFX server 5. compute service-links [Target. Parsers] • Per Target/Service

tools for SFX-configuration • SFXCTRL: 1. a graphical interface for configuring: 1. Sources 2. Targets 3. Services [where Sources and Targets meet] 2. 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 Open. URL-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 get. Author service would run a search in a target on an author’s name • A get. Full. Txt 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

demos http: //www. sfxit. com ; brochures in back http: //www. sfxit. com/Open. URL DOI experiment http: //sfxserv. rug. ac. be: 8888/public/xref/ Sources http: //www. sfxit. com/sources. html Targets http: //www. sfxit. com/targets. html reading http: //www. dlib. org

Cross. Ref DOI - Cross. Ref - Open. URL – SFX experiment http: //sfxserv. rug. ac. be: 8888/public/xref/