Using the Enhanced OpenURL Framework: Upgrading from Version 0.1 to 1.0 Ann Apps MIMAS, University of Manchester, UK

Using the Enhanced OpenURL Framework: Upgrading from

Version 0.1 to 1.0Ann Apps

MIMAS, University of Manchester, UK

2003-10-29 NISO OpenURL Workshop 2

Using the OpenURL Framework

• Support for scholarly information community

• Upgrade from v0.1

• Practical use of OpenURL within a scholarly information application

• Conformance requirements


The OpenURL Framework for Context-Sensitive Services

• Generalisation and formalisation of v0.1

• ContextObject: referenced resource and associated resources in context of reference

• OpenURL: method of transporting ContextObject


ContextObject Example

• In e-journal application Elsevier ScienceDirect, Ann Apps at Manchester University finds– McArthur, JG “p27-p16 Chimera…” Molecular Therapy 3(1) 8-13

• References

– Bergelson, J. “Isolation of…” Science (275) 1320-1323

• ContextObject contains 6 entities:– Referent: Bergelson paper

– ReferringEntity: McArthur paper; Referrer: ScienceDirect

– Requester: [email protected]; ServiceType: full text

– Resolver: http://sfx.mimas.ac.uk/sfxmanx


Describing Entities

• Descriptors– Identifier: info:doi/10.1126/science.275.5304.1320

– Metadata• By-value

• By-reference

• Formats– Key / Encoded Value (KEV)– XML


Using ContextObjects

• Transports– Flavours of OpenURL (by-value, by-reference,

inline)

• Community Profiles– San Antonio Profiles Level 1 and 2 for

scholarly information– Dublin Core Profile

• Core components in OpenURL Registry


San Antonio Profile Level 1

• Key/Encoded Value• Namespaces:

– URI/URN, eg. http, mailto, ISSN, ISBN

– info, eg. DOI, PubMed Id, SICI

• Metadata Formats: – journal, book, patent, dissertation

• Service Types:– abstract, citation, full text, holdings, ILL


zetoc

• Current awareness and document delivery service for journal articles and conference papers in every imaginable subject

• Based on British Library’s Electronic Table of Contents

• Available to researchers and learners in UK Higher and Further Education; England and Scotland National Health Service


Using zetoc

• Search via Web interface

• Email alert

• zetoc full record provides citation details

• Article can be ordered from BL or by ILL

• Users want electronic full text of article if they have valid subscription





Default Location

• OpenURL link to MDL LitLink

• Not an appropriate copy but many have access to major resources

• “It’s worth a try but access can’t be guaranteed”

• OpenURL linking well used and no complaints


zetoc OpenURL v0.1

• Translate citation metadata into a URL linkhttp://sfx.mimas.ac.uk/sfxmanx?

sid=mimas:zetoc

&genre=article

&atitle=Phase compositions…

&title=Scripta Materialia&issn=1359-6462

&aulast=Apps&auinit=P.J.&date=2003

&volume=48&issue=5&spage=475&epage=481


OpenURL v1.0

url_ver=Z39.88-2003

&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx

&rfr_id=info:ofi/rfr:db:mimas.ac.uk:zetoc

&rft_val_fmt=info:ofi/fmt:kev:mtx:journal

&rft.genre=article

&rft.atitle=Phase compositions…

&rft.jtitle=Scripta Materialia&rft.issn=1359-6462

&rft.aulast=Apps&rft.auinit=P.J.&rft.date=2003

&rft.volume=48&rft.issue=5&rft.spage=475&rft.epage=48


Upgrade v0.1 to v1.0

• San Antonio Profile Level 1 (KEV) and Inline OpenURL– Add url_ver key

– Add url_ctx_fmt key to indicate KEV

– Change sid to rfr_id and use rfr:db: scheme

– Add rft_val_fmt: referent by-value journal metadata

– Prefix metadata keys by rft.

– jtitle preferred for journal title

– Change id to rft_id with info:, eg info:doi/10...


Entities and Descriptors in OpenURL v0.1

• Referent: referenced article• Referrer: origin description (sid)• Resolver: base URL (link server)• Requester, ReferringEntity, ServiceType:

– in local identifier zone with private identifier (pid)

• Identifier descriptor: global identifier (4)• Metadata Format: object metadata (journals /

conferences)


Hybrid OpenURLs

• Upgrade transition period

• Problem for Referrers

• Solution: create hybrid OpenURLs

• Combined v1.0 and v0.1

• Resolvers expected to deal gracefully with foreign keys


Hybrid OpenURL

http://sfx.mimas.ac.uk/sfxmanx?

url_ver=Z39.88-2003&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx

&rfr_id=info:ofi/rfr:db:mimas.ac.uk:zetoc&sid=mimas:zetoc

&rft_val_fmt=info:ofi/fmt:kev:mtx:journal

&rft.genre=article&genre=article

&rft.atitle=Phase compositions…

&atitle=Phase compositions…

&rft.jtitle=Scripta Materialia &title=Scripta Materialia

...



OpenURL Trial

• Draft standard for trial use

• Trial April - November 2003

• Sources, Resolvers, End-users

• zetoc: source SAP1 KEV inline OpenURLs

• Tested with several resolvers






Other Example Scenarios

Examples listed in SAP1 Implementation Guidelines– Inline, by-value, by-reference OpenURL

• Article referenced from electronic journal article in e-journal service

• Conference paper referenced from e-journal article, or A+I service

• Book referenced from a book, or shopping service• Journal referenced from serials directory




SAP1 Source OpenURLs

• Provided by Referrers, eg. e-journals, A+I services, library OPACS

• Provide as much information as available

• Provide a Referrer Identifier– Defines provenance of data

• Service type requests are guideline only

• Private data discouraged


SAP1 Resolver Conformance

• Target of activated OpenURL source link

• Support all selections from Registry defined as part of SAP1

• Resolver behaviour not prescribed– Handle gracefully:

• Namespaces and metadata formats cannot resolve

• Foreign keys

• Continue to accept v0.1 OpenURLs


Beyond San Antonio

• OpenURL already well used in scholarly information environment

• Potential to provide intelligent ‘appropriate copy links’

• OpenURL Framework very general. Potential for use in diverse domains with new Profiles

Documents

Using the Enhanced OpenURL Framework: Upgrading from Version 0.1 to 1.0 Ann Apps MIMAS, University of Manchester, UK