1 / 30

Gathering Data

Gathering Data. NISO E-Resource Management Forum Denver, Colorado September 24-25, 2007 Oliver Pesch EBSCO Information Services opesch@ebsco.com. Overview. The workflow The elements The entities Sources of the data Current and potential harvesting opportunities

ofira
Download Presentation

Gathering Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gathering Data NISO E-Resource Management Forum Denver, ColoradoSeptember 24-25, 2007 Oliver PeschEBSCO Information Services opesch@ebsco.com

  2. Overview • The workflow • The elements • The entities • Sources of the data • Current and potential harvesting opportunities • Standardization efforts and other initiatives

  3. Overview • The workflow • The elements • The entities • Sources of the data • Current and potential harvesting opportunities • Standardization efforts and other initiatives

  4. Making sure For whom Trial How much Location Consortium Library Acquisition License Product TheDeal What Terms Terms Resources Resources Resources Resources Interface Access Admin Expose Support

  5. Making sure For who Trail How much Location Consortium 315 Library Acquisition License Product TheDeal What Terms Terms Resources Resources Resources Resources Interface Access Admin Expose Support

  6. Trial Processing Consortium Trial Location Consortium Acquisition Library Acquisition Library License License Product TheDeal ENTITIES Terms E-Resource Terms Resources Resources Resources Resources Interface Access Admin Access Administration Contacts

  7. Trial Processing Consortium Trial Location 9 27 14 Consortium Acquisition Library Acquisition Library 24 16 License License Product TheDeal ENTITIES 23 Terms E-Resource Terms Resources Resources Resources 33 Resources Interface 71 Access Admin Access Administration Contacts 29 8 50

  8. Overview • The workflow • The elements • The entities • Sources of the data • Current and potential harvesting opportunities • Standardization efforts and other initiatives

  9. Sources of data • Library • Publisher/Provider • Agent/Jobber • Consortium • A-to-Z/Knowledge base supplier

  10. Overview • The workflow • The elements • The entities • Sources of the data • Current and potential harvesting opportunities • Standardization efforts and other initiatives

  11. E-Resource Entity

  12. Acquisition Entity * This data is available to the ILS via EDI, just not the ERM

  13. License Entity

  14. Terms Defined Entity

  15. Access Entity

  16. Administration Entity

  17. Overview • The workflow • The elements • The entities • Sources of the data • Current and potential harvesting opportunities • Standardization efforts and other initiatives

  18. Current Data Harvesting opportunities • Usage data • COUNTER and SUSHI • E-Resource information - Bibliographic • MARC records from content providers • MARC records from knowledge base vendors • E-Resource information – Holdings • Spreadsheets from vendors, agents, publishers • Downloads from knowledge base vendors • Spreadsheets, XML (ONIX SOH) • Financial • Spreadsheets or Invoice load (EDI) from agent • Access/Admin data • Reports (spreadsheets) from vendor

  19. Current Standards initiatives Existing • COUNTER/SUSHI (usage) • ONIX SPS (serials products and subscriptions) • ONIX SOH (holdings) • ONIX for Serials Coverage Statements • ICEDIS (EDI) In development • ONIX PL (License Expression Group) • ERMI-2 ILS/ERM interoperability • TRANSFER

  20. COUNTER • A Code of Practice for making usage statistic consistent, credible and comparable • Dictates, terminology, processing of logs, formatting of reports and delivery of usage data • Vendors must now undergo usage audit to be compliant • Revision 3 will be released next year, focus on Consortium reports, XML and SUSHI • Relevance to this discussion is consistent usage data provides hope of ERMs to offer usage consolidation • Status: Released

  21. SUSHI (NISO Z39.93) • Standardized Usage Statistics Harvesting Initiative • Automates harvesting of usage data using “Web 2.0” approach • ERM/Usage consolidation, can automatically connect to and retrieve usage data from any content provider with a SUSHI server • Advantages • Completely automates usage harvesting from compliant content providers • Saves hours upon hours of staff time • Challenges • Lack of consistent identifiers (not always possible to map the given usage to the correct resource in the ERM) • Adoption • Status: Released (Just approved by NISO Membership!)

  22. ONIX SPS • Serials Publications and Subscriptions • Used for communicating information about subscription products • Designed for communicating price catalogs • Advantages • Does allow for some financial data • Allows for title lists to be included in packages • Challenges • Does not accommodate price breakdown by component of a package, just the package itself • Status: Draft

  23. ICEDIS / EDI • A series of formats to communicate order and activation data • Latest revision expands message to include IP addresses and other components appropriate for e-resources • Current format built on fixed data model • Work being considered to upgrade to XML • Advantages • Used by many publishers and agents and ILS systems • Challenges • Lack of XML limits interoperability options • Web service approach cannot be used easily (needed for real-time exchange of data) • Fixed format nature makes implementation expensive • Status: Released

  24. ONIX SOH • Serials Online Holdings • Used for communicating holdings information about electronic resources • Includes coverage, URLs, embargos, etc. • Version 1.1 accommodates ONIX Coverage Statements • Advantages • Excellent for transfer of holdings from one knowledge base to the next • Challenges • Lack of consistent identifiers of vendors, packages and even titles limit interoperability opportunities • Status: Released

  25. TRANSFER • A working group formed to address the problems caused by transfer of titles between publishers • A set of guidelines for publishers to follow • Ensure libraries have continuous access • Considering a central repository of “transferred” titles • Status: Under development

  26. ONIX PL (License Expression Working Group) • An XML schema that allows the terms of a license to be exchanged in a machine readable form • Work also being performed on a license editor • One goal was to allow negotiation to take place by exchanging and editing a license • Advantages • Captures the terms of a license • Challenges • An “ONIX” license represents the agreement and does not necessarily map to elements in the ERMI license element • Interpretation of the license still needed (An “implementation” of ONIX PL is being experimented with to communicate the ERMI interpretations”) • Status: In development

  27. SERU • Shared E-Resource Understanding • An alternative to a license when librarians and publishers agree a license is not necessary • Documents expectations of behavior on part of publisher, libraries and their users • Advantages • Simplifies the acquisition of e-resources • Eliminates delays and complications by avoiding license negotiation (and approval) • Challenges • Will not fit every deal • Does not explicitly “grant” every right a library may want • Status: In trial through end of 2007

  28. ERMI-2 ILS Acquisitions and ERM Interoperability • Allow for the exchange of a core set of financial data between the ERM and the ILS • Facilitate collection analysis by providing data for Cost-per-Use calculations • Advantages • Automate harvesting of data for collection analysis • Challenges • Identifiers • Cost allocation for packages • Status: Beginning stages

  29. Summary • An ERM is intended to be a single site to access all there is to know about an e-resource • As such, the data needs are varied and complex • DLF/ERMI data dictionary lists 315+ data elements and 25+ entities • The data comes from many sources • Providers, agents, knowledge base vendors, consortia • It is unlikely that one source will supply all data • Some automated feeds exist today and many more are possible • Standards are key to interoperability and smooth data exchange

  30. SUSHI Thank you! Oliver Pesch opesch@ebsco.com

More Related