Localized Linking Prototype

CNI

April 10, 2001

Dale Flecker, Larry Lannom, Rick Luce, Bill Mischo, Ed Pentz

THE PROBLEM

Citation LINK

MAGICLINK

Cited Article

Citation

WHAT WE ALL WANT TO ACCOMPLISH

CLICK

Any old system

Any old system

CitationDOI

Step1

Step2 DOI Resolver

DOI

URL

Cited article

Search response

RepositoryURL

Article

Step3

HOW DOI DOES THIS

CLICK

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 ResolverDOI

URL?

Sciencedirect.com?

Ohiolink.edu?

Utoronto.ca? LANL.gov

A PROBLEM

DOI today cannot resolve to more than 1 copy

ACM

DOI (to Elsevier)

Ohio State User

ELSEVIER

Cited article

OhioLink

A BAD THING….

(or: “$25, please”)

CLICK

ARTICLECitation

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

10.1000/123

http://acme.com/pg1.html http://acme.com/pg1.html

10.1000/123

Handle Systemdx.doi.org

acme.pub

pg1.html

Article withCrossRef

Link

Client

XYZ University

Local copy

Contextualization: First Experiment (Hardcoded CrossRef)

10.1000/123?cookie

Redirect w/OpenURLto extended link server

Handle System

dx.doi.orgUnderstands Service Cookies

CrossRef

Metadata?

Metadata

localCopy.html

Article withCrossRef

Link

Client

Ext. Link Server

XYZ University

Contextualization: Second Experiment (MD Indirection)

10.1000/123?cookie

Redirect w/OpenURLto extended link server

Metadata location?

Meta1.com

XYZ University

Client

Article withCrossRef

Link

Ext. Link Server

localCopy.html

Metadata?Metadata

Meta2.comMetadata Collection Service

Handle Systemdx.doi.org

Understands Service Cookies

Meta1.comMetadata Collection Service

Meta3.comMetadata Collection Service

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

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

• 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)

• 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

OpenURL aware

References

DOI Proxy Server

DOI link

DOI

OpenURL

Metadata

DOI Handle ServerDOI

http://dx.doi.org/10.1093/toxsci/57.1.95

LANL LinkSeeker

(Local Service)

AppropriateLinks

OpenURL model for Alternative/Local resolution of CrossRef/DOI

CrossRef Link

INSPEC Abstract

INSPEC Abstract

AIP Article

Add LANLextended services

via SFX

Basic Example

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 clientClient

(Web Browser)

DOI Proxy

Illinois LocalLink Server

OpenURL

AwareLocal

AIP, IEE

CrossRefMetadataDatabase

dx.doi.org/10.1063/1234HandleServer

AIP

IEE

Elsevier

DOI

Metadata

LocalValueAdded

Nosfx=y

UIUC MetadataRegistry

OpenURL

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