Mitchell Memorial Library’s 7 th Annual E-Resource Workshop

1. Library Standards and E-Resource Management:A survey of current initiatives and standards efforts Mitchell Memorial Library’s 7th AnnualE-Resource Workshop July 20, 2007Oliver PeschEBSCO Information Services opesch@ebsco.com

2. Overview • Background • Standard development organizations and their standards • E-Journal Life Cycle • Relating standard to the life-cycle • Some observations • Focus on specific standards (COUNTER, SUSHI, SERU)… time permitting

3. Overview • Background • Standard development organizations and their standards • E-Journal Life Cycle • Relating standard to the life-cycle • Some observations • Focus on specific standards (COUNTER, SUSHI, SERU)… time permitting

4. Background • Management of e-journals is very challenging • Many organizations are working on ways to help • A myriad of standards and initiatives exist • Its not always easy to match a standard to a problem • Presenting them in a familiar context can help • ERMI developed the e-journal life-cycle • This presentation will map standards to the life-cycle

5. Overview • Background • Standard development organizations and their standards • E-Journal Life Cycle • Relating standard to the life-cycle • Some observations • Focus on specific standards (COUNTER, SUSHI, SERU)… time permitting

6. Standard development organizations • NISO • Accredited by ANSI; develops standards related to information management. • Editeur • Focus on developing the standards infrastructure for e-commerce of books and subscriptions. Standard carry the ONIX brand. • COUNTER • A collaboration between libraries, publishers and aggregators to ensure provision of usage statistics that are credible, consistent and comparable.

7. Standard development organizations… • Digital Library Federation • A consortium of libraries and related agencies pioneering the use of electronic information technologies and collections. • ICEDIS (International Committee on EDI for Serials) • Brings together publisher and subscription agents with the goal of creating industry standards to facilitate the journal subscription business. • UKSG (United Kingdom Serials Group) • An interest group to promote the free exchange of ideas on electronic and print serials and the process of scholarly communication.

8. NISO Standards and initiatives (selected)

9. ONIX standards from Editeur (selected)

10. COUNTER

11. DLF (E-Resource Management Initiatives)

12. ICEDIS

13. UKSG

14. Overview • Background • Standard development organizations and their standards • E-Journal Life Cycle • Relating standard to their life-cycle • Some observations • Focus on specific standards (COUNTER, SUSHI, SERU)… time permitting

15. ACQUIRE Prices Title Lists Subscription Lists Business terms Cataloging License Terms Title Lists PROVIDE ACCESS Orders Holdings lists RENEW Business terms Invoices Proxy support Renewal orders Registration & activation Invoices Searching & Linking Use rights & restrictions Usage data Holdings changes Title list changes Cost data EVALUATE Check-in ADMINISTER Contacts Claims Trouble shooting SUPPORT

16. Overview • Background • Standard development organizations and their standards • E-Journal Life Cycle • Relating standard to their life-cycle • Some observations • Focus on specific standards (COUNTER, SUSHI, SERU)… time permitting

17. Standards related to the life-cycle: Disclaimers In the following slides we provide more details on the life-cycle from the perspective of information transfer and, in particular, the potential for that transfer to be from machine to machine. In this regard: • The discussion is not exhaustive • The parties indicated are intended to represent parties most likely to engage in machine-to-machine transfer of data (e.g. make use of the standards) • The standards identified are those which define or enable automated data exchange. • Standards are listed due to their potential to help solve the problem, in many cases these standard have not been fully adopted or may still be in draft form.

18. ACQUIRE WHAT: Package and price info PARTIES: publisherlibrary publisheragent agentlibrary STANDARD: ONIX SPS Prices Title Lists Subscription Lists WHAT: List of content included in the transaction PARTIES: publisherlibrary publisheragent agentlibrary STANDARD: ONIX SPS; ONIX SOH Business terms License Terms PROVIDE ACCESS Orders RENEW WHAT: List of current subscriptions (also needed for packages) PARTIES: librarypublisher publisheragent STANDARD: ONIX SPS Invoices WHAT: Orders and proof of payment PARTIES: agentfulfillment STANDARD: ICEDIS WHAT: Start date, term, price and payment terms, etc. PARTIES: publisherlibrary publisheragent agentlibrary STANDARD: ONIX PL; SERU WHAT: Detailed invoice for subscriptions PARTIES: agentlibrary (ILS) agentlibrary (ERM) library (ILS)library (ERM STANDARD: <none> EVALUATE ADMINISTER WHAT: License terms and conditions (terms of use) PARTIES: publisherlibrary publisheragent agentlibrary STANDARD: ONIX PL; ERMI license terms; SERU SUPPORT

19. ACQUIRE WHAT: Bibliographic data PARTIES: agentlibrary (OPAC) publisherlibrary (OPAC) EAMSlibrary (OPAC) STANDARD: Z39.2 (MARC) Cataloging PROVIDE ACCESS Holdings lists RENEW WHAT: Holdings data with URLs and coverage PARTIES: agentlibrary publisherlibrary EAMSlibrary STANDARD: ONIX SOH Proxy support Registration & activation Searching & Linking WHAT: Proxy configuration info (list of domains) PARTIES: agentlibrary EAMS library STANDARD: <none> EVALUATE ADMINISTER WHAT: Order details for e-journals PARTIES: agenthost agentfulfillment fulfillmenthost STANDARD: ICEDIS WHAT: Searching of collection PARTIES: librarycontent provider metasearchcontent provider STANDARD: Z39.50; MXG; Z39.91; Z39.93 WHAT: Context sensitive linking PARTIES: content providerlink resolver STANDARD: Z39.88 (OpenURL) SUPPORT

20. ACQUIRE WHAT: Interpretations of rights and restrictions of use PARTIES: agentlibrary (ERM) publisherlibrary (ERM) library (ERM)library (AtoZ) STANDARD: ERMI license terms; ONIX PL PROVIDE ACCESS RENEW WHAT: Holdings data including URLs and coverage PARTIES: agentlibrary publisherlibrary EAMSlibrary STANDARD: ONIX SOH; Z39.2 (MARC) Use rights & restrictions WHAT: Titles moving between publishers PARTIES: publisheragent publisherlibrary agentlibrary STANDARD: TRANSFER Holdings changes Title list changes EVALUATE Check-in ADMINISTER Claims WHAT: Alerts on new issues PARTIES: publisheragent publisherlibrary agentlibrary STANDARD: ONIX SRN WHAT: Alerts on missing issues PARTIES: library (ILS)agent agentpublisher library (ILS)publisher STANDARD: <none> SUPPORT

21. ACQUIRE WHAT: Who to contact for various needs (sales, technical, etc.) PARTIES: publisherlibrary publisheragent agentibrary STANDARD: <none> PROVIDE ACCESS RENEW WHAT: Information on triage and solving problems. PARTIES: publisherlibrary (ERM) agentlibrary (ERM) STANDARD: <none> EVALUATE ADMINISTER Contacts Trouble shooting SUPPORT

22. ACQUIRE WHAT: Usage data PARTIES: content hostlibrary (ERM) usage servicelibrary STANDARD: COUNTER; Z39.88 (SUSHI) PROVIDE ACCESS RENEW WHAT: Cost information including breakdown by content item PARTIES: agentlibrary publisherlibrary library (ILS)library (ERM) STANDARD: ONIX SPS Usage data Cost data EVALUATE ADMINISTER SUPPORT

23. Overview • Background • Standard development organizations and their standards • E-Journal Life Cycle • Relating standard to their life-cycle • Some observations • Focus on specific standards (COUNTER, SUSHI, SERU)… time permitting

24. Observations The message versus the transfer of the message • Seamless integration of systems requires a message and a means of transferring that message • Many standards focus on the message (e.g. ONIX, COUNTER XML schema, etc.) • Yet don’t prescribe how two systems should exchange the message. • Opportunities exist for continued development of exchange protocols like SUSHI and OpenURL (which focus on the exchange of messages that may be defined by another standard.)

25. Observations Evolving definitions of business needs • Growing sophistication of ERMs require additional data • Cost information • Packages costs broken out by title • Fund information • Some existing standards don’t handle these new needs (e.g. ONIX SPS does not allow for cost at title level) • Existing standards will need to be updated • Standards processes need to be light to allow adaptation in a timely manner

26. Observations Standards are more important than ever • Concepts like Web 2.0 are about seamless integration of sites and services • To make things appear simple on the surface requires un-seen complexity behind the scenes • This complexity needs standards for successful scaling • Collaboration and community involvement is key!

27. Overview • Background • Standard development organizations and their standards • E-Journal Life Cycle • Relating standard to their life-cycle • Some observations • Focus on specific standards (COUNTER, SUSHI, SERU)… time permitting

28. Focus on specific standards • COUNTER • SUSHI • SERU

29. Non-profit organization includes librarians, publishers and aggregators • Lead in the standardization of usage • How use is counted • How use is reported • “Consistent, credible, comparable” http://www.projectcounter.org/

30. COUNTER Code of Practice • Code of Practice first released Jan 2003 • Release 2 released Jan 2006 • Code of Practice Addresses: • Terminology • Layout and format of reports • Processing of usage data • Delivery of reports http://www.projectcounter.org/code_practice.html

31. COUNTER Usage Reports Journal Reports: • JR1: Full Text Article Requests by Month and Journal • JR2: Turnaways by Month and Journal Database Reports: • DB1: Total Searches and Sessions by Month and Database • DB2: Turnaways by Month and Database • DB3: Searches and Sessions by Month and Service Books and Reference Works: • Title Requests, Section Requests, Searches and Turnaways

32. Journal Report 1:Number of Successful Full-Text Article Requests by Month and Journal

33. Explicit report layout – “consistent”

34. “Credible” – COUNTER Audit • Beginning 2007, an audit must be passed for a vendor’s service to be compliant • Conducted by auditor certified accountant or by organization accredited by COUNTER (ABCE) • At vendor expense

35. Overview • COUNTER • SUSHI • SERU

36. SUSHI: Objectives • Solve the problem of harvesting and managing usage data from a growing number of providers. • Promote consistency in usage formatting (XML) • Automate the process

38. SUSHI: What is it? • An XML Message • Methods to transfer the message between two systems • Implemented as a Web service • Using SOAP (Simple Object Access Protocol)

39. SUSHI : The Exchange • Report Request <Requester> <Customer Reference> <Report Definition> • Report Response • <Requester> • <Customer Reference> • <Report Definition> • <Report as payload>

40. SUSHI Architecture • The next series of slides graphically show a SUSHI transaction • Library system requests a usage report • SUSHI client makes the request • SUSHI server processes request • SUSHI server prepares COUNTER report • SUSHI server “packages” and returns response • SUSHI client processes COUNTER report

41. The SUSHI request is sent to the Content Provider. The request specifies the report and the library the report is for. Library Content Provider ? ERM Internet Request Request SUSHI Client SUSHI Server (web service) Usage Data

42. The COUNTER report (XML) is created and added to the Response as its payload. The response is sent to the client. Library Content Provider ? ERM Response Internet SUSHI Client SUSHI Server (web service) COUNTER Usage Data

43. The SUSHI client processes the response and extracts the COUNTER report. Library Content Provider ? ERM Response Internet SUSHI Client SUSHI Server (web service) COUNTER Usage Data

44. SUSHI: from concept to standard in record time! • The SUSHI Steering Committee • Nov. 2004 - Meetings between Cornell & Innovative • July 2005 – Cross-Industry Committee forms: Libraries; ILS vendors; Content providers • Fall 2005 – Technical discussions • Winter 2006 – Live harvests • Spring 2006 – NISO involvement • September 2006 – Draft standard for trial use • May 2007 – Successful trial period ends • Summer 2007 – Z39.93 presented for ballot

45. SUSHI: Adoptions and future • Release of final standard later this year • COUNTER Release 3 • Consortia reports • New COUNTER Schema • SUSHI compliance • Extendible design • Other reports • Other “payloads”

46. SUSHI: Status of Z39.93 200x • Trial period ended in May 2007 • Successful implementations • A few minor technical adjustments were made • Revisions to the standard have been finalized • Standard is at ballot – closes September 1

47. Founding Members: EBSCO Ex Libris Innovative Interfaces, Inc. Swets Information Services Thomson Scientific Newer members: Endeavor Information Systems Florida Center for Library Automation College Center for Library Automation (CCLA) from the State of Florida Community Colleges Otto Harrassowitz OCLC Project Euclid Serials Solutions SirsiDynix SUSHI: Contributing Partners

48. SUSHI: Resources • NISO Website: http://www.niso.org/committees/SUSHI/SUSHI_comm.html • SUSHI Schemas: http://www.niso.org/schemas/sushi/index.html • SUSHI FAQ: http://docs.google.com/View.aspx?docid=d2dhjwd_63tkkwf • What is the relationship of the COUNTER payload schema to the SUSHI schema? • What variable information has to be supplied in a SUSHI (client) request? • What variable information has to be supplied in a SUSHI (server) response? • What COUNTER reports can be delivered with SUSHI? • Does SUSHI support older Releases of the COUNTER reports?

49. Overview • COUNTER • SUSHI • SERU

50. SERU • Shared Electronic Resource Understanding • Intended to “stop the madness” of e-journal licenseing (or at least reduce the madness) • A mutual understanding on how e-resources will be acquired and used • Allows transactions to take place without the need for a formal license • Does not replace all license agreements (only works when the understanding is mutual and agreeable) • Is NOT a standard license or license of adhesion (e.g. click-through)