370 likes | 496 Views
UKSG Serials Resource Management for 21 st Century Getting Technical - Linking. Robert Bley Ex Libris UK Ltd. Jargonbusting agenda!. The basics of the web Linking D.I.Y. DOI & CrossRef OpenURL Searching NISO Metasearch (Not too much on) authentication!
E N D
UKSG Serials Resource Management for 21st CenturyGetting Technical - Linking Robert Bley Ex Libris UK Ltd.
Jargonbusting agenda! • The basics of the web • Linking • D.I.Y. • DOI & CrossRef • OpenURL • Searching • NISO Metasearch • (Not too much on) authentication! • Open Archives Initiative – ‘e-prints’ • Usage statistics • Electronic Resource Management • The future…(!)
Data Format HTML Addressing URL How does the Web work? 3 simple protocols: Data FormatsHTML (HyperText Markup Language) provides the data format for documents AddressingURLs (Uniform Resource Locator) provides an addressing mechanism for web resources TransportHTTP (HyperText Transfer Protocol) defines transfer of resources between client and server (currently) Transport HTTP Brian Kelly, Web-Focus, UKOLN
How does the Web work? The Netsofthome page 1User clicks on link to the address (URL)http://www.netsoft.com/hello.html 2 Browser converts link to HTTP command (METHOD): Connect to computer at www.netsoft.com GET /hello.html 3Remote computer sends file Welcome to Netsoft Web server <HTML> <TITLE>Welcome</TITLE>.. <P>Welcome to <B>Netsoft</B> Web Browser 4Local computer displays HTML file
Other key jargon • HTML – Hypertext Markup Language. A document format that allows text to be interpreted by web browsers (Internet Explorer etc) as web pages - e.g.
Other key jargon • XML - Extensible Markup Language - allows creators of web documents to define their own customized tags for defining and transmitting data between applications and/or organizations
Other key jargon • SOAP - Simple Object Access Protocol. An XML-based protocol for information exchange • “Web services” - describes a standardized way of integrating Web applications. XML is used to tag the data, SOAP is used to transfer the data
Other key jargon… • ONIX for Serials - a collection of XML format standards for (among many other things!) communicating electronic serials holdings details using XML. (See http://www.editeur.org/onixserials.htm).
Linking Mechanisms URL-based include: • explicit filename http://www.ariadne.ac.uk/issue24/intro.html • derived filename, e.g. ISSN, SICI http://www.jstor.ac.uk/journals/10624783.html • script, e.g. http://www.esajournals.org/esaonline/?request=get-abstract&issn=00129658&volume=077&issue=08&page=2302
Linking Mechanisms • The Digital Object Identifier (DOI): • A unique identifier assigned to a digital object. • A way of accessing an object (e.g. a full text article) without having to know its URL - the DOI identifies the object itself, not the place where it is stored. • Persistent - as long as the object exists, so does the DOI.
DOI: Dumb Old Identifier “Dumb” number - doesn’t relate to the object, couldn’t be guessed – similar idea to a phone number. 10.1000/1A3X-56BZ9 Prefix - given to the rights owner e.g. the publisher Suffix - any unique alphanumeric string e.g. 10.1074/jbc.M004545200
DOI link URL to Publisher DOI Metadata CrossRef/DOI resolution References DOI http://dx.doi.org/10.1093/toxsci/57.1.95
OpenURL (ANSI/NISO Z39.88) Pat Harris, Executive Director of NISO: "One message we hear is that the new business model will be enabled by information technology with standards at the core. This is where NISO fits in. …over five hundred years ago Guttenberg fundamentally changed communication and learning. Today NISO's challenge is to create those standards that will enable the modern day Guttenburg Moment. Could it be the OpenURL?"
OpenURL format ::=Base URL?Query Base-URL = web address of the link resolver i.e. the address to which the OpenURL is being sent http://LinkFinderPlus.library.edu?genre=article&issn=1234-5678&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
Traditional linking – the old way http://publish.aps.org/abstract/PRA/v63/p062103
http://sfx.aaa.edu/menu?genre=article&issn=0036-8075 &volume=12&issue=3&spage=1&epage=8&date=1998 &aulast=Smith&aufirst=Paul Smart linking with the OpenURL (e.g.full text or pay-per-view etc) (e.g. OPAC or A&I database)
A & I resource as link source… Source Menu Target
Searching • Huge array of library resources – different interfaces and different search syntaxes • Libraries act as “gatekeepers” to these resources • One method – simple library web page listing those resources
Another answer: Cross-resource searching? Diverse information resources Query form ? metasearching = federated searching = cross database searching = parallel searching = broadcast searching = integrated searching
Cross-resource searching - standards • Z39.50 – Old (pre-web) US standard for bibliographic information retrieval - defining a standard way for two computers to communicate and share information. Still the most commonly standard used by library system OPACs, publishers and database providers etc. • ZING – Z39.50 Next Generation. Has produced two standards: • SRU and SRW are similar protocols http://www.loc.gov/z3950/agency/zing/zing-home.html • SRU (“search & retrieve URL”) is done as a basic HTTP request (it can be in the format of a URL) whereas the search in • SRW (“search & retrieve web”) is sent as an XML document wrapped in SOAP. • NISO Metasearch initiative
A few words about the dark art of authentication! • Distinction between- authentication (publishers (etc.) asking “are you who you say you are”)…and…- authorization(publishers (etc.) asking “what are you entitled to access, now that we know who you are?”) • Most publishers have “IP authentication” • Every address on the Internet has a numeric equivalent – e.g. 212.58.224.55 = www.bbc.co.uk • An institution may “own” a range – e.g. 212.58.224.x • Publishers may register a range or individual workstation addresses • Numeric to alphabetic lookup available at http://www.ripe.net/fcgi-bin/whois? • Drawbacks for off-campus users, mean alternative password-based solutions exist – e.g. Athens • Other options = Proxy address (legal “IP spoofing”!) and Shibboleth
Getting technical All sorted then? Pig courtesy of Tom Bishop, Royal College of Surgeons
The Open Archives Initiative • 1999 Universal Preprint Service (UPS) • Multi-disciplinary collection of technical reports, conference papers, articles, e-print servers, etc. • Services provided on “harvested metadata” • Data Providers / Service Providers • Not ‘Cross-Searching’ • OAI is only about metadata – not full text • OAI is neutral about nature of metadata and the resources described
OAI - Protocol for Metadata Harvesting • Simple mechanism for sharing metadata records • Records shared over the web (ie HTTP as XML) • ‘Client’ can ask metadata server for • all records • all records modified in last ‘n’ days • info about sets, formats, etc. • Specific application: self-archiving via e-print servers in/for all institutions • “SHERPA” – UK project - http://www.sherpa.ac.uk/
Consistent, Credible & Compatible Usage Statistics • Code of Practice for: • Data elements to be measured • Definitions of these data elements • Output report formats/delivery/frequency/granularity • Methods for measurement and use • AAP, ALPSP, ARL, ASA, EDItEUR, JISC, NCLIS, NISO, PA, STM, UKSG
152 member organisations • Code of Practice Jnls & Dbs Rel 1 • Over 30 vendors compliant (in part) • Developing Auditing standards & processes • XML DTD for Usage Reports developed • Release 2 consultation – due early 2005 • Code of Practice eBooks & eReference
Electronic Resouces Management - ERM • Basic ERM Data Elements • Descriptive: Title fields, holdings, publisher, and ISSN • Licensing: Authorized users, archiving rights, and cancellation allowances • Financial: Price and inflation rate • Administrative & Support: Administrative password and vendor contact information. • Access: Authorization method and local access URI • Usage or Evaluative: Number of full-text article downloads and number of searches
An E-Resources Management System: the vision “A system that supports management of the information and workflows necessary to efficiently select, evaluate, acquire, maintain, renew/cancel and provide informed access to e-resources in accordance with their business and license terms” - Ivy Anderson, Robin Wendler (Harvard University Library) and Ellen Duranceau (MIT Libraries)
DLF ERMI entity-relationship model! http://www.library.cornell.edu/cts/elicensestudy/home.html
What next? • agga Acknowledgement: Greg Raschke and Suzanne Weiner (netConnect) The Library Journal -- 7/15/2004 • SOAP & XML – tools for integration • Standards and partnership between all players!
Thanks! email: robert.bley@exlibris.co.uk web: http://www.exlibrisgroup.com/