Title: LOCALIZED REFERENCE LINKING PROJECT
1LOCALIZED REFERENCE LINKING PROJECT
- Dale Flecker
- NFAIS/NISO Linking Workshop
- February 24, 2002
- Philadelphia
2THE PROMISE OF CITATION LINKING
Any old system
Citation
Citation
LINK
CLICK
LINK
MAGIC
Cited Article
3HOW DOI PERFORMS MAGIC
Any old system
Step 1
Citation
Search response
DOI
CLICK
Step 2
DOI
DOI Resolver
URL
Repository
URL
Step 3
Cited article
Article
4BUT -- WHAT IF MORE THAN 1 COPY EXISTS?
- Elsevier journals, for example, are on-line at
- Elsevier ScienceDirect
- OhioLink
- University of Toronto
5WHICH URL?
Handle Server
DOI
URL?
Sciencedirect.com?
Ohiolink.edu?
Utoronto.ca?
6A PROBLEM
DOI today cannot naturally resolve to more than
1 copy
7A BAD THING.
Ohio State User
ACM
ARTICLE
Citation
DOI (to Elsevier)
CLICK
ELSEVIER
(or 25, please)
OhioLink
Cited article
8WHY MULTIPLE COPIES
- Local loading
- Aggregators
- Mirror sites
- Paper copies
- E-print archives??
- Preservation archives??
9THE APPROPRIATE COPY
When more than one copy exists, specific
populations frequently have the right to access
specific copies
10CROSSREF/DLF LINKING PROTOTYPE
- Group of research libraries (coordinated by DLF)
approached CrossRef on the appropriate copy
issue - Series of discussions between publishers, DOI,
CrossRef, libraries, service providers, NISO - Prototype to test localization of linking using
OpenURL Framework
11PARTICIPANTS
- International DOI Foundation/CNRI
- CrossRef
- Los Alamos National Laboratory
- University of Illinois
- Ohio State/OhioLink
- Ex Libris
12OpenURL FRAMEWORK
NOT
LINK
TARGET
RATHER
TARGET A
LINK
SERVICE
TARGET B
TARGET C
13LINKING SERVICE
- An agent for the user
- Knows what the link is for
- OpenURL transports information to the service
about the link - Knows the users context
- therefore can localize the link
- Reasons about the appropriate target(s) for a link
14OpenURL
Transports metadata to a service
http//serv.univ.edu/iddoi123/4567
Identity of local service
Metadata about link
15DESIGN ISSUES IN LOCALIZING LINKS
- How to identify which users need localization
- How to insert the service agent in DOI resolution
to do localization - How does the agent know what a DOI identifies
- How does the agent know how to appropriately
resolve the DOI
16REMEMBER HOW DOI PERFORMS MAGIC
Any old system
Step 1
Citation
Search response
DOI
CLICK
Step 2
DOI
DOI Resolver
URL
Repository
URL
Step 3
Cited article
Article
17PROTOTYPE ARCHITECTURE
Any old system
Step 1
Citation
Search response
DOI
CLICK
Step 2
DOI
DOI SERVER Does user have localization?
N
DOI Resolver
Y
LOCALIZATION SERVICE
18PROTOTYPE ARCHITECTURE
DOI
DOI web proxy Does user have localization?
N
DOI (Handle) Resolver
DOI with localization switch no
Y
OpenURL with DOI
or
LOCALIZATION SERVICE
CrossRef
Address of alternate copy to User
Metadata in XML
19DESIGN ISSUE 1
- How to identify which users need localization
- solution cookie
- users institution must implement method of
getting appropriate cookie on user workstation - transparent to the user
- highly controversial
- how to set? keep set? avoid setting
inappropriately? - butwhat alternative?
20DESIGN ISSUE 2
- How to insert localization service in DOI
resolution - put a filter in front of DOI resolution service
which looks for cookie - if no cookie, just resolve DOI as usual
- if cookie, redirect transaction to local agent,
using an OpenURL containing the DOI
21DESIGN ISSUE 3
- How does a service agent know what a DOI refers
to? - University of Illinois service did not need to
- just keep a list of DOIs for articles in the
local system - other implementations retrieved descriptive
metadata from CrossRef
22DESIGN ISSUE 4
- How does the service agent know how to
appropriately resolve the DOI - up to the local agent
- look up DOI in local database which gives local
address - look up journal in local database, giving linking
syntax - send search to opac
- Can resolve to locally stored digital copy, local
paper copy, aggregator service, document delivery
service, original publisher.
23IMPLEMENTATION
- CNRI implemented a cookie pusher, and filter
for resolution requests - LANL and Ohio State used SFX as the localizing
agent - Illinois wrote a localizing agent
- All three libraries implemented a script to
trigger cookie pushing - CrossRef implemented reverse look-up (DOI to
metadata)
24EXPERIENCE
IT WORKS!!!!
25A COUPLE OF REMAINING ISSUES
- Cookies the big issue
- how to consistently get them on user machines,
maintain them - Locating metadata not addressed in prototype
- will become an issue as other DOI registration
agencies come on-line - need to know which agency to ask for the metadata
26STATUS -- DOI LOCALIZATION
CrossRef and International DOI Foundation
committed to support localization model
27STATUS -- OpenURL
NISO workgroup on fast-track to standardize
format
Many companies already committed to support
OpenURL EBSCO, OCLC, Gale, IOP SilverPlatter,
Ovid, Bowker, Wilson, ProQuest.
28STATUS -- LOCALIZING AGENTS
Two commercial products available Ex Libris SFX
and Endeavors LinkFinderPlus -- these provide
liking options beyond appropriate copy -- many
working installations of SFX already OhioLink
and University of Illinois have implemented
custom agents
29MORE DETAIL?
On the prototype D-Lib Magazine, September,
2001 www.dlib.org On OpenURL library.caltech.edu
/OpenURL