Reference LinkingTechnologies

1
Reference LinkingTechnologies

William H. Mischo w-mischo_at_uiuc.edu Grainger
Engineering Library Information
Center University of Illinois at
Urbana-Champaign March 2, 2001
2
Outline

• Digital Object Identifier (DOI).
• DOI Resolution
• CrossRef.
• Appropriate Copy issues.
• Local Resolver.
• SFX and OpenURL.
• Local Service Providers.

3
Digital Object Identifier (DOI)

• DOI is both a unique identifier of a piece of
  digital content AND a system to access that
  content digitally. Persistent object identifier.
• The ISBN for the 21st Century -- Norman Paskin
  of the IDF.
• DOI system has two main parts (the identifier
  and a directory system) and a third logical
  component, a database.
• Developed by AAP (Association of American
  Publishers), now managed by International DOI
  Foundation.

4
DOI Construction

• Open standard for persistent object
  identification.
• DOI is a dumb number that identifies a digital
  object
• 10.1063/S000369519903216
• 10 Registration Agency Prefix
• 1063 Publisher Prefix
• S000369519903216 Suffix (Publisher-assigned
  ID)
• Suffix can be SICI or PII.
• The DOI and the URL pointing to the digital
  object, is registered with the International DOI
  Foundation, e.g
• 10.1063/333 http//www.pub.org/apr99/artl1.pdf

5
Using a DOI

• DOIs are resolved using the Handle System
  developed by CNRI (Corporation for National
  Research Initiatives).
• Retrieval of object is two step process link is
  sent to central Handles directory where current
  Web address is stored, location is sent back to
  browser with special message to redirect to
  address, e.g
• dx.doi.org/10.1063/333 redirects to
  www.pub.org/apr99/artl1.pdf

6
Reference Linking

• If publisher changes the location URL, only the
  central directory needs to be updated.
• Much previous reference linking has relied on
  algorithmic links.
• Cooperative bilateral agreements between AIP,
  APS, Elsevier, ISI, INSPEC (proprietary linking
  mechanisms).
• Proprietary linking technologies still being
  used.

7
CrossRef

• Collaborative reference linking service.
• Began in 1999 with major STM professional society
  and commercial publishers forming PILA
  (Publishers International Linking Association).
• Now over 60 publishers, 3,000 journals, 2.1
  million article records. All areas of scholarly
  publishing.
• Three services depositing metadata including
  DOIs, submission of article references for the
  purpose of obtaining DOI, creation of links using
  DOIs.

8
CrossRef

• Depositing of article metadata in XML format into
  database. Minimal article metadata (e.g. one
  author name). Reverse lookup by DOI implemented.
• CrossRef registers DOI and URL in central DOI
  directory.
• System design calls for one URL for each DOI
  leading to Appropriate Copy problem. Underlying
  Handles technology can handle multiple URNs
  however.

9
Appropriate Copy Problem

• Issue Directing users to locally held or
  licensed version of Digital Object (might be
  locally loaded or from Aggregator like Ebsco,
  Ovid).
• Harvard problem, Appropriate Copy problem, now
  Local Reference Linking.
• Additional desire to direct users to local
  value-added services local print holdings and
  call numbers, interlibrary borrowing, other
  articles in A I Services.
• Proxy server issue.

10
Local Resolver

• Four meetings have been held on Appropriate Copy
  issue last two in DC, Boston.
• Demonstration Project at Illinois, OhioLink (Ex
  Libris SFX), Los Alamos.
• Local Article Resolution for AIP, ASCE, Elsevier,
  other publishers.
• Use of CrossRef Metadata Database for obtaining
  metadata from DOI and linking to Local Copy, A
  I Services, Library Assistance, print holdings,
  etc.
• OpenURL Protocol, CookiePusher vs. IP Addresses.
• Opt out option for publishers.

11
DOI Proxy

• Cookie on client

OpenURL
Client (Web Browser)
AIP
Handle Server
dx.doi.org/10.1063/1234
IEE
Nosfxy
Aware
Elsevier
Local AIP, IEE
OpenURL
Local Value Added
Local Resolver
DOI
CrossRef Metadata Database
Metadata
UIUC Metadata Registry
12
OpenURL

• OpenURL syntax is HTTP GET request in the form
  of
• OpenURL BaseURL ? Query
• In Local Resolver at UIUC
• http//bolder.grainger.uiuc.edu/lr/lr.asp?iddoi1
  0.1063/333
• Original idea of OpenURL added by information
  providers to their metadata displays to be used
  for local services
• issn1234-5678date1999volume41issue2page12
  
• Providers can create their own services that can
  accept OpenURLS as input.

13
Local Service Providers

• SFX developed at Ghent by Herbert van de Sompel.
• SFX Licensed by Ex Libris.
• Goal is to provide context-sensitive services,
  such as links to distributed resources, including
  local information.
• Examples local holdings/call numbers,
  interlibrary loan information, expanded access to
  A I services, Web resources.
• OpenURL framework, submitted as NISO standard.
  Tool for the description and transfer of metadata
  to local service components.