Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

RM - Both 2CUL partners currently have different ERM systems, increasing the number of complex systems staff across institutions will need to be skilled in using, and making common workflows significantly difficult to envision and implement.  Resource Manager is a robust e-resource management system, providing libraries with the ability to manage e-resource collections, record information about providers, licenses, and other data that is not easily handled by Voyager, and to easily include our holdings in various other Serials Solutions services such as Summon and 360 Link.  The implementation of RM in particular should be relatively low impact compared to what we would expect if we implemented an entirely different ERM system across 2CUL as both partners maintain most of their electronic holdings in the Serials Solutions knowledgebase knowledge base and staff from both CULs are already familiar with the system.

...

  • Record loads into III - requires considerable attention for week every month. wear and tear on body and soul. Impact on patrons (updated holdings, public display inaccurate and slow), staff (stress and ability to focus on other work) 10-20 hours per month.  Some of the time saved could be spent handling more frequent Serials Solutions MARC updates loads, keeping Voyager and the ERM in closer sync.  This will reduce delays between purchasing content and having that content appear in discovery tools such as Blacklight and Summon.
  • License, resource information already in knowledge base for many resources - III system is all hand entry for resource and license records.
  • Selectors will be able to access the system with relatively little training to view title lists, license terms, contact information.  As a web based tool, this will be possible remotely (during a conference).  III system has limited simultaneous connections and requires considerable training to get new users up to speed.
  • Reducing the number of systems involved in e-resource management without loss of functionality or access to information.  This has significant impact on training time, procedure retention, and ease of use.
  • Cleaner matching of resources between management and discovery systems.  This has significant impact on our ability to effectively troubleshoot resource access issues.
  • Knowledgebase Knowledge base Notifications alert us to changes in platforms, database titles, and other important maintenance issues.  This will allow for more pro-active work to reduce access problems.

...

  • Platform changes and other resource maintenance can often be time intensive projects. We can handle these tasks collaboratively and can make the changes for both institutions when both CULs have content in the same collections. 
  • Collaborative monitoring of Knowledgebase Knowledge base Notifications will be possible, thereby reducing duplicate effort.
  • Comparison of e-collections will be considerably easier.  This will set us up to engage in  cooperative collection development decisions, shared workflow.

...