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
Cited Article
MAGIC
HOW DOI DOES THIS
Any old system
Step
1
Search response
Citation
DOI
CLICK
Step
2
DOI
Step
3
URL
DOI Resolver
URL
Repository
Article
Cited article
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
WHICH URL?
DOI
DOI Resolver
URL?
Sciencedirect.com?
Ohiolink.edu?
Utoronto.ca?
LANL.gov
A PROBLEM
DOI today cannot resolve
to more than 1 copy
A BAD THING….
Ohio State User
ACM
ARTICLE
Citation
DOI (to Elsevier)
CLICK
ELSEVIER
(or: “$25, please”)
OhioLink
Cited article
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???
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
Contextualization: Current
XYZ University
10.1000/123
10.1000/123
http://acme.com/pg1.html
http://acme.com/pg1.html
dx.doi.org
Client
Handle System
pg1.html
Article with
CrossRef
Link
Local copy
acme.pub
Contextualization: First Experiment
(Hardcoded CrossRef)
XYZ University
10.1000/123?cookie
Redirect w/OpenURL
to extended link server
dx.doi.org
Understands Service Cookies
Client
Ext. Link Server
Metadata?
Article with
CrossRef
Link
Metadata
localCopy.html
CrossRef
Handle System
Contextualization: Second
Experiment (MD Indirection)
XYZ University
10.1000/123?cookie
Redirect w/OpenURL
to extended link server
dx.doi.org
Understands Service Cookies
Client
Handle System
Metadata location?
Ext. Link Server
Meta1.com
Article with
CrossRef
Link
Metadata
Metadata?
localCopy.html
Meta1.com
Metadata Collection Service
Meta3.com
Metadata Collection Service
Meta2.com
Metadata Collection Service
OpenURL Terminology
• OpenURL framework - a concept and
architecture for linking, enabling contextsensitive, 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
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
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
From OpenURL to SFX
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….
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
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
• 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)
OpenURL model for Alternative/Local
resolution of CrossRef/DOI
DOI
link
DOI
References
DOI
Proxy
Server
DOI
Handle
Server
OpenURL
aware
OpenURL
Metadata
DOI
LANL
LinkSeeker
(Local Service)
http://dx.doi.org/10.1093/toxsci/57.1.95
Appropriate
Links
Basic Example
INSPEC Abstract
AIP Article
INSPEC Abstract
CrossRef Link
Add LANL
extended services
via SFX
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?
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.
Cookie on
OpenURL
Client
client
(Web Browser) dx.doi.org/10.1063/1234
DOI Proxy
Nosfx=y
AIP
Handle
Server
IEE
Aware
Elsevier
Local
AIP, IEE
OpenURL
CrossRef
Metadata
Database
DOI
Illinois Local
Link Server
Metadata
UIUC Metadata
Registry
Local
Value
Added
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