1 / 26

Localized Linking Prototype

Localized Linking Prototype. CNI April 10, 2001 Dale Flecker, Larry Lannom, Rick Luce, Bill Mischo, Ed Pentz. THE PROBLEM. WHAT WE ALL WANT TO ACCOMPLISH. Any old system. Citation. Citation. LINK. CLICK. LINK. MAGIC. Cited Article. HOW DOI DOES THIS. Any old system. Step 1.

joshua
Download Presentation

Localized Linking Prototype

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Localized Linking Prototype CNI April 10, 2001 Dale Flecker, Larry Lannom, Rick Luce, Bill Mischo, Ed Pentz

  2. THE PROBLEM

  3. WHAT WE ALL WANT TO ACCOMPLISH Any old system Citation Citation LINK CLICK LINK MAGIC Cited Article

  4. HOW DOI DOES THIS Any old system Step 1 Citation Search response DOI CLICK Step 2 DOI DOI Resolver URL Repository URL Step 3 Cited article Article

  5. BUT -- WHAT IF MORE THAN 1 COPY EXISTS? • Elsevier journals, for example, are on-line at: • Elsevier ScienceDirect • OhioLink • University of Toronto • Los Alamos National Laboratory

  6. WHICH URL? DOI DOI Resolver URL? Sciencedirect.com? Ohiolink.edu? Utoronto.ca? LANL.gov

  7. A PROBLEM DOI today cannot resolve to more than 1 copy

  8. A BAD THING…. Ohio State User ACM ARTICLE Citation DOI (to Elsevier) CLICK ELSEVIER (or: “$25, please”) OhioLink Cited article

  9. THE APPROPRIATE COPY • When more than 1 copy exists, specific populations frequently have the right to access specific copies • Some systems today can do this tailored linking (ISI, for instance) • But... it must be done by EVERY system from which links can come • Can we expect every citation source to do this???

  10. A WIDELY DISCUSSED PROBLEM…. • Explored in a series of meeting hosted by DLF, CrossRef, IDF, SSP, NFAIS, NISO • Agreement last year to a demonstration project based on an OpenURL architecture • Participants include IDF, CNRI, CrosssRef, Ex Libris, University of Illinois, LANL, OhioLink, Ohio State • With observers from NISO, DLF, and a number of publishers

  11. Contextualization: Current XYZ University 10.1000/123 10.1000/123 http://acme.com/pg1.html http://acme.com/pg1.html dx.doi.org Handle System Client pg1.html acme.pub Article with CrossRef Link Local copy

  12. Contextualization: First Experiment (Hardcoded CrossRef) XYZ University 10.1000/123?cookie dx.doi.org Understands Service Cookies Redirect w/OpenURL to extended link server Client Handle System Metadata? Ext. Link Server Article with CrossRef Link Metadata localCopy.html CrossRef

  13. Contextualization: Second Experiment (MD Indirection) XYZ University 10.1000/123?cookie dx.doi.org Understands Service Cookies Redirect w/OpenURL to extended link server Client Handle System Ext. Link Server Metadata location? Meta1.com Article with CrossRef Link Metadata? Metadata localCopy.html Meta1.com Metadata Collection Service Meta2.com Metadata Collection Service Meta3.com Metadata Collection Service

  14. OpenURL Terminology • OpenURL framework - a concept and architecture for linking, enabling context-sensitive, or localized, resolution of links • OpenURL - a syntax for transporting metadata and identifiers within URLs • SFX - the first OpenURL-aware server capable of providing localized resolution

  15. OpenURL • Copy should come from location other than default link location • Library uses different server location or has local repository • An OPEN protocol -- not proprietary • Used to create localization based on a user’s incoming URL • Recognized by CrossRef and the DOI handle system • A basic component of the SFX software

  16. How OpenURL works • Information is “pushed” into the URL to allow recognition that there is a service component (SFX, etc) with access parameters available • A unique OpenURL is constructed for each metadata object (citation, etc.) • OpenURL components: • BASE-URL : service component address • Content : elements of the metadata, in a public syntax

  17. OpenURL will solve the appropriate copy problem Publisher article link will go to correct localized copy SFX uses OpenURL to present extended services beyond just the appropriate full text…. From OpenURL to SFX

  18. SFX - what is it? • Service component software which provides context sensitive localized services • Includes, but is not limited to, appropriate copy full text • Each library activates and defines which services will be offered to their users • Services are dynamically available based on locally defined parameters

  19. Article full text (many publishers) Document request/ILL Author search in all local databases Cited author search Cited paper search PubMed - genome search / abstract PubList information Local holdings (OPAC) Author email search Ask a librarian (email ref questions) SFX and OpenURL • Services determined by citation metadata / identifiers and by objects which exist in the SFX database • OpenURL is used to refer back to the SFX database for localization LANL localized services

  20. OpenURL model for Alternative/Local resolution of CrossRef/DOI DOI link DOI Proxy Server DOI Handle Server OpenURL aware Metadata DOI References DOI OpenURL LANL LinkSeeker (Local Service) Appropriate Links http://dx.doi.org/10.1093/toxsci/57.1.95

  21. Basic Example INSPEC Abstract AIP Article INSPEC Abstract CrossRef Link Add LANL extended services via SFX

  22. Los Alamos Experience - Issues • Concept proven, put into production March 30 • Setting cookies - user “shortcut” bookmarks which avoid the library path = no way to set the cookie • Publisher must do IP check • Not many DOI’s yet • LANL situation different due to large locally loaded collections on site • Much more useful for sites that don’t have local loading • What about grey literature?

  23. Illinois Local Link Server • Local Testbed of AIP, APS, ASCE, IEE full-text journals from DLI-I and CNRI D-Lib Test Suite. • Local copy identified from a DOI metadata registry (database). • Implementation via Cookie-Pusher and .asp server-side scripting. • Part of Local Link Server project that: • knows our local and licensed resources; • understands OpenURL syntax. • Developing generic mechanism for understanding and describing local resources (XML Schema). • Developing filter (XML syntax) to resolve OpenURL to local/licensed resource.

  24. DOI Proxy OpenURL Client (Web Browser) AIP Handle Server dx.doi.org/10.1063/1234 IEE Nosfx=y Cookie on client Aware Elsevier Local AIP, IEE OpenURL Local Value Added Illinois Local Link Server DOI CrossRef Metadata Database Metadata UIUC Metadata Registry

  25. Issues • Library Issues • Identifying Users with Local Service Component (setting cookies)/IP Filtering? • What about non-DOI content? • What’s displayed to users? • Network traffic/performance/scalability • CrossRef Issues • Publisher opt-out/Control of linking • Policy - terms to supply metadata/trusted servers • What metadata? More than DOI Kernel

More Related