1 / 17

UC’s Electronic Resources Management System

Learn about the UC libraries' vision to integrate collection development and e-resource management, providing campuses with data access and improving version control. Follow the ERMS implementation progress and the challenges faced.

cfaust
Download Presentation

UC’s Electronic Resources Management System

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. UC’s Electronic Resources Management System Users Council, May 11, 2007 Heather Christenson

  2. The Problem • CDL centrally licenses electronic resources, no way for campuses to see ERM data • No way for anyone to see across campuses and do comparisons • Electronic resources becoming more prominent in general, hard for any of us to manage

  3. The Vision • Collection development and e-resource management will be integrated across UC using a common set of data • Campuses will have the ability to view each other's local resources • There will also be "authority" in the data – reducing the problems with version control, outdated lists, etc.

  4. The ERMS will be • A technical services staff tool • A shared system • An authoritative database for licensing terms and conditions

  5. In general, the ERMS will not be • An end-user discovery tool • An acquisitions system • Used for print resources

  6. A Brief History • October 2003: CDL “Electronic Resource Management Assessment” report • April 2004: Two-day UC-wide discussion with stakeholders • July 2004: RFP responses • August 2005: Ex Libris Verde 1.0 • January 2007: Verde 2.0 test installation

  7. Who is working on this right now? • CDL technical & licensing groups • SOPAG-appointed implementation team (member from each campus) • Functional experts from some campuses (UCB, UCD, UCLA, UCSC, UCSD)

  8. CDL in action • Technical aspects of installation and configuration • Initial population of data • Workflows and ongoing use

  9. Implementation team in action • Overall principles to guide decision-making • Best practices & guidelines • Checklist for campus readiness

  10. Testing… Testing… • Verde 2.0 was successfully installed at CDL • Testing: Access was given to test participants, SOPAG implementation team and some CDL staff • Test report to SOPAG, May 30th

  11. Some advantages of Verde • Offers consortium functionality • Standards-based • Operates with our link resolver, SFX

  12. Challenges • Very complex • Workflow changes to adapt to an ERMS • Still a young, evolving product

  13. Questions? Project Web Site http://www.cdlib.org/inside/projects/erms/index.html Project Manager heather.christenson@ucop.edu

More Related