Primary funding is provided by the JISC and ESRC. Based at Manchester Computing, The University of Manchester. 1 1 OpenURL – why? Ross MacIntyre & Ann Apps MIMAS The University of Manchester

OpenURL – why? STM Overview Linking through the ages NISO OpenURL Stakeholder views ‘Sources’ & ‘Targets’ Novel uses & trends Summary

OpenURL – why? STM How does the Web work? 3 simple protocols: Data Formats HTML (HyperText Markup Language) provides the data format for native documents Addressing URLs (Uniform Resource Locator) provides an addressing mechanism for web resources Transport HTTP (HyperText Transfer Protocol) defines transfer of resources between client and server Data Format HTML Addressing URL Transport HTTP Brian Kelly, Web-Focus, UKOLN

OpenURL – why? STM

OpenURL – why? STM URL-based Linking Mechanisms explicit filename derived filename, e.g. ISSN script, e.g % %2926%3A3%3C%3AFM%3E2.0.CO%3B2-O toc3&issn= &volume=003&issue=09

OpenURL – why? STM Ye Olde Linking Link Source Link Destination Link. Resource Resolution of Links Provision of Links Oren Beit-Arie, ExLibris

OpenURL – why? STM CrossRef/DOI resolution References Metadata DOI DOI link URL to Publisher DOI

OpenURL – why? STM OpenURL (v0.1) format ::= Base URL ? Query Base-URL = web address of the link resolver i.e. the address to which the OpenURL is being sent &volume=12&issue=3&spage=1&epage=8 &date=1998&aulast=Smith&aufirst=Paul Query = the metadata that the link resolver uses to identify and link to appropriate targets

OpenURL – why? STM OpenURL linking Link Source OpenURL. Resource Service Component Resolver/Link Server Provision of Hooks Resolution into Links Context Sensitive Link Destination Link Link Destination Link Link Destination Link Link Destination Link Hook Appropriate Oren Beit-Arie, ExLibris Router

OpenURL – why? STM OpenURL in action

OpenURL – why? STM OpenURL Framework ANSI/NISO Z Goals: –Formally address shortcomings (of v0.1) –Controlled evolution –Ensure wider acceptance Outcome: –Defines the general framework for bundling contextual metadata and introduces concepts of: ContextObject Formats and other elements and contextual entities –Defines the Registry –Defines the notion of Community Profiles Oliver Pesch EBSCO

OpenURL – why? STM The “ContextObject” contains… ServiceType Referent Resolver ReferringEntity Referrer Requester Administrative Version control, character encodings, timestamp, etc. Item being referenced. E.G. bibliographic reference in full text article. “User” making the request Service creating the link. E.G. where the user found the reference. The item which contains the reference. E.G. the article in which the bibliographic reference was found. The target of the link. E.G. the link server of the user’s institution The desired services from the Resolver. E.G. Full text, ILL, Abstract, etc. Oliver Pesch EBSCO

OpenURL – why? STM Stakeholder #1 - Readers “Give it me now” Expectation of direct connection Simple & consistent interface Usability & utility –Eason: ‘Ready-to-hand’ (Heidegger) –Mooer: ‘More painful to not have than to get’ –Zipf: ‘Least effort’

OpenURL – why? STM

OpenURL – why? STM

OpenURL – why? STM

OpenURL – why? STM Stakeholder #2 - Libraries Direct users to highest quality resources ↑ Access ≡ ↑ ROI (Discuss) Library branding ‘Backroom’ benefits Meeting user expectations “Extension of library itself” Frank Cervone, Computers in Libraries, Oct2005, Vol. 25 Issue 9, p10, Publisher: Information Today.

OpenURL – why? STM

OpenURL – why? STM Stakeholder #3 – Funding Bodies Defined Information Architecture e.g. JISC Information Environment –Step 1: Expose metadata about your content Support searching using Z39.50 Support harvesting using the OAI Protocol for Metadata Harvesting –Step 2: Share news/alerts using RSS –Step 3: Become an OpenURL source –Step 4: Become an OpenURL target –Step 5: Use persistent URIs

OpenURL – why? STM Stakeholder #4 – Publishers “Why help readers leave?!” Market requirement –Critical customer requirement –Competitive pressure Competitive cooperation for mutual benefit (e.g.CrossRef) Reduce/remove onus for linking Streamline linking infrastructure 2 nd ary Publishers © 2005 Mark Lentczner and John Horigan.

OpenURL – why? STM Are you there yet? OpenURL Sources What’s wanted? Below supplied by SMUG-UKI 28/11/05: LexisNexis Professional & Academic Westlaw IEE Digital Library & IEE Explore Scitation Research Alerts Construction & Building Abstracts Foodline Web ABELL Factiva Metapress (covering T&F, Springer, etc), Sage, Highwire – “as these are searchable sites which include titles we don’t subscribe to electonically, but may have print subscriptions.”

OpenURL – why? STM Are you there yet? OpenURL Targets What’s wanted? Below supplied by SMUG- UKI: –WestLaw –LexisNexis –Early English Books Online –Business Insights –DIALOG –Oxford Reference –LION - (e-books) –Taylor & Francis ebooks Targets currently in the (SFX) Knowledge Base but without article level linking: –IEEE Xplore Journals –Thomas Telford Journals –Chadwyck Literature Online –Walter de Gruyter Publishing –Times Higher Education Supplement

OpenURL – why? STM Novel Uses: ContextObject Endorsed for bibliographic citation by DCMI NISO Metasearch Initiative Latent OpenURLs –COinS -> CiteULike, Citebase, Zetoc… –Harvesting COinS via OAI-PMH RSS

OpenURL – why? STM

OpenURL – why? STM Lorcan Dempsey, OCLC: “Everything is in 3 generations” Gen 1 –Z39.50, ISO-ILL –S2S –Library niche Gen 2 –OpenURL, OAI-PMH, SRU, … –B2B –Web services idiom Gen 3 –Leverage G2 infrastructure: lightweight services on top of SRU/OpenURL/OAI –COinS –Bridges to generic approaches and desktop frameworks RSS Bookmarklets... O'Reilly, T. (2005).

OpenURL – why? STM Summary Static & proprietary Predicatable & parameterised Persistent (Publisher-controlled) OpenURL prototype->standard ContextObject: Locator -> Identifier Pre-coordination->Post-coordination

OpenURL – why? STM Thanks! web: