lita/alcts erm interest group june 24, 2011 tim jewell ([email protected])

25
NISO ERM Data Standards and Best Practices Review Update LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell ([email protected])

Upload: conor-folger

Post on 28-Mar-2015

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

NISO ERM Data Standards and Best Practices Review

Update

LITA/ALCTS ERM Interest GroupJune 24, 2011

Tim Jewell ([email protected])

Page 2: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Gateway to Improving ERM System Deliverables:

NISO ERM Data Standards and Best Practices Review

Page 3: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Deberah EnglandElectronic Resources LibrarianWright State University

Welcome!

Bob McQuillanSenior Product ManagerInnovative Interfaces

Page 4: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Ivy Anderson (co-chair, California Digital Library)

Tim Jewell (co-chair, University of Washington)

Jeff Aipperspach (formerly Serials Solutions) Deberah England (Wright State University) Rafal Kasprowski (Rice University) Tim McGeary (Lehigh University) Bob McQuillan (Innovative Interfaces) Angela Riggio (UCLA)

ERM Data Standards and Best Practices Review

Page 5: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Workshop co-sponsored by NISO and the Digital Library Federation (DLF) in 2002

ERMI evolved under the guidance of DLF to:

“Develop common specifications and tools for managing the license agreements, related administrative information, and internal processes associated with collections of licensed electronic resources”

Electronic Resource Management Initiative (ERMI), Phase I

Page 6: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Functional Requirements Support the “Life Cycle” of electronic

resources:◦ Selection and acquisition◦ Access provision◦ Resource administration◦ User support and troubleshooting (staff and end-

users)◦ Renewal and retention decisions

E-Resource Acquisitions Workflow

Page 7: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

DLF ERMI 2004 Report Relationships

(Data Model)◦ Packages and their

constituent parts◦ Knowing which

resources share the same interface, license terms, business terms, etc.

Page 8: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

DLF ERMI 2004 Report Information

(Data Dictionary)◦ License permissions

and constraints◦ User ID, passwords,

administrative info, etc.

◦ Contacts for support and troubleshooting

◦ Cancellation restrictions, price caps, etc.

Page 9: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

DLF ERMI 2004 Report Workflows

(Functional Requirements)◦ Mounting Trials◦ Routing Licenses◦ Placing Orders◦ Implementing access◦ Notifying relevant

staff

Page 10: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

SUSHI

CORE

License Mapping

Data dictionary review

Electronic Resource Management Initiative (ERMI), Phase 2

Page 11: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

ALA Midwinter 2009 ERM Gap Analysis Focus Group ERMI 1 & 2 participants addressed future of

ERMI data dictionary and related issues:◦ Libraries need help with workflows & best practices◦ Existing ERM Systems

Under-developed Need more functionality

Import / export data Support everyday business activities / functions

◦ Data exchange is critical◦ ERMI data model still important◦ Data dictionary key to functionality &

interoperability◦ License elements / values need simplification

Page 12: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

“Gap analysis” regarding ERM-related data, standards and best practices

Review ERMI Data Dictionary◦ Map elements to other relevant standards

projects Consult with vendors, libraries using ERM

systems and other stakeholders for additional feedback◦ Data requirements◦ Implementation◦ Standards

The “Plan”

Page 13: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Recommend future of ERMI Data Dictionary Describe challenges libraries face with

current ERM systems and services Identify gaps in interoperability and best

practices Report to be delivered to the NISO Business

Information Topic Committee and made publicly available

Project Deliverables

Page 14: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Progress and Pain Points– Results of Recent ERM Surveys General, including Satisfaction and

Dissatisfaction Problems areas:

◦ System implementation◦ Workflows, internal communication◦ Licensing◦ Consortial services◦ Cost per use / evaluation◦ Ebooks

Potential bearing on Standards

Page 15: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Why Standards? Reduce re-keying Reduce maintenance cost & disruption Durability of data Avoid supplier lock-in Easier development path Platform for collaboration Whole system economies

Source: “The Business Case for Standards” (JISC)

Page 16: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Standards vs. Best Practices? NISO Standards

◦ Balloted – e.g., MARC, ONIX-SOH, Z39.50 Formally designated Best or Recommended

Practices◦ E.g., CORE, KBART, SERU

“Local” Best Practices Vendor and product identity management is

a major problem:◦ Represent vendor-resource-holdings relationships◦ Manage resource and holdings in standardized,

shareable way

Page 17: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

1. Link resolvers & knowledge bases2. The Work, manifestations &

access points3. Integration of usage & cost-

related data4. Coding license terms & defining

consensus5. Data exchange using institutional

identifiers

Standards & Best Practice Categories

Source: R. Kasprowski: “Best Practice & Standardization Initiatives for Managing Electronic Resources,” ASIST Bull., Oct/Nov 2008

(v. 35 no. 1, pp. 13-19)

Page 18: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

OpenURL (OCLC)

KBART (NISO)◦ Knowledge Base And Related Tools

IOTA (NISO)◦ Improving OpenURLs Through Analytics

1. Link resolvers & knowledge bases

Page 19: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

DOI (International DOI Foundation) ◦ Digital Object Identifier

MARC 21 (The Library of Congress) ONIX for Serials (EDItEUR)

◦ SOH (Serials Online Holdings)◦ SPS (Serials Products and Subscriptions)◦ SRN (Serials Release Notification)

ONIX for Books PIE-J (NISO)

◦ Presentation and Identification of E-Journals Transfer Code of Practice (UKSG)

2. The Work, manifestations & access points

Page 20: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

CORE (NISO)◦ Cost Of Resource Exchange

COUNTER (UKSG)◦ Counting Online Usage of NeTworked

Electronic Resources

SUSHI (NISO)◦ Standardized Usage Statistics Harvesting

Initiative

3. Integration of usage & cost-related data

Page 21: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

ONIX-PL (EDItEUR)◦ ONIX for Publications Licenses

SERU (NISO)◦ Shared Electronic Resource Understanding

4. Coding license terms & defining consensus

Page 22: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

I2 (NISO)◦ Institutional Identifiers

Shibboleth (Internet2 Middleware Initiative)

vCard (Internet Mail Consortium)

5. Data exchange using institutional identifiers

Page 23: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Much to applaud, build on from wide variety of standards and best practices work

Future of ERMI data dictionary still unclear

Major problem areas remain, including

◦ License complexity, expression/encoding

◦ Workflow support

Takeaways so far . . .

Page 24: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

Immediate (by end of June) Provide access to full, original version of Collins/Grogg ERM

survey article

Near-term (July/August)◦ Complete, release “discussion paper”◦ Provide access to documents

Standards “mapping” spreadsheets Workflow documents

Bibliography Internal documents from selected libraries

◦ Complete summary/highlights version for NASIG Proceedings

Project loose ends . . .

Page 25: LITA/ALCTS ERM Interest Group June 24, 2011 Tim Jewell (tjewell@uw.edu)

More Information

ERM Data Standards and Best Practices Review Working Group

http://www.niso.org/workrooms/ermreview