1 / 11

Break-out Session

Break-out Session. In this break-out session, librarians, publishers, and vendors discuss together their ERM priorities. Break-Out Questions. What are the most important aspects of interoperability / the most pressing standards in need of development?

lumina
Download Presentation

Break-out Session

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. Break-out Session In this break-out session, librarians, publishers, and vendors discuss together their ERM priorities.

  2. Break-Out Questions • What are the most important aspects of interoperability / the most pressing standards in need of development? • What functions are we still missing in an ERM? Should these be included in an ERM or elsewhere?

  3. Break-out Questions • What problems does your library need to resolve in your ERM practices? If you’ve implemented an ERM, have those problems been addressed? • Have we allowed ourselves to reach a state of crisis and what steps do we need to take immediately to remedy the situation?

  4. Question 1 - Group 1 Responses • Between acquisitions client & ERM -- regardless of provider -- PO, invoice, status, payment, cost, etc. • Ability of link resolvers and ERMS to have communication between them (regardless of provider) • Data that could get from subscription agents that would have a lot of value--in some sort of standard way to populate system with that data set. Format, license terms, validation of access.

  5. Question 1 - Group 2 Responses • Same as group 1 • Wish list: • Generate automated messages to give to publishers (e.g., when you change IPs) • Automated way for publishers to communicate title ownership (e.g., when a title is given up by one and taken over by other) • Way to communicate system down-time -- ERM acts accordingly

  6. Question 2 - Group 1 Responses • Interoperability encouraged with tiered cost system • Interface with campus & ILS financial systems • Calculate % inflation rate for forecasting • Retrospective cost data -- perhaps development of index so libraries can do budgeting • Aside: what is the inflation rate of ERMS? :) • Common licensing terms across customers (that the licensing agents would use)

  7. Question 2 - Group 1 (cont.) • Reporting flexibility with ability to do calculations with that information • Usage statistics reporting • Which systems do A-Z lists, support web services, etc. • Ability for ERMS to communicate with campus systems (e.g., Banner) -- is that desirable? • Ways to export (standarized) information to these kinds of systems

  8. Question 2 - Group 2 Responses • True consortial support, specifically ways to share info that reflects granularity of view & access information. Related: issue of confidentiality of licenses. • UKSG’s report on problem of knowledge-based maintenance. Need for vendors to communicate holdings, and libraries’ need to push for that info. • Problem of licensing overload. Perhaps helped by emerging licensing standards--and want to see more support for those. • Interoperability • Is our worst enemy us??

  9. SERU • Shared E-Resource Understanding • Draft Best Practice (not a standard, not a license) • www.niso.org/committees/SERU • Visit the registry online!

  10. Question 3 - Group Response • How to develop the ownership of the ERM & its data, and how to identify the benefits of ERMS to staff? • Central Knowledge Base -- get away from KBs for various products, and have one that is shared (?)… (different vendors) • Communicating license terms to staff/public • Sharing outage info. • Share w/ staff & patrons where resource is in procurement cycle/lifecycle of resource, and what next steps are (what still needs to happen)

  11. Question 4 - Group Response • The Crisis is all around us! • No clear-cut, best ERM on market • Remarkably few e-resource staff (and there are so many dedicated to print) • Serials agents struggling to find out their role in this (Swets trying to take a lead by providing SPS reports)

More Related