Versions Compared

Key

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

The In response to Phase 1 objective: Make a specific recommendation on whether to implement the Consortial Version of Serials Solutions at both institutions or hold off on integrating e-resource management and data migration until we have a shared LMS, the 2CUL TSI E-Resources Team proposes that 2CUL implement a common e-resource management system in order to facilitate collaboration across the range of e-resource activities. We believe that the most effective path to take is with the suite of tools provided by the Serials Solutions (a ProQuest company) Resource Manager system as both partners are already using some or all of the Serials Solutions system in their day to day work, minimizing the implementation effort required to be up and running together quickly.  The transition will require that:

...

  • E-Resources Unit (Liisa Mobley, Rebecca Utz, Sally Lockwood, Heather Shipman, Jesse Koennecke) - Tested the general functionality, workflow features, and data management aspects of the RM system from a Cornell specific perspective.  The e-resources staff are already familiar with the Serials Solutions staff interface while working with the currently subscribed Serials Solutions services (MARC Updates, 360 Link, and Summon).  Adding ERM features to this existing workflow, rather than in a completely different system will likely show some increased efficiency in some areas of e-resources work.   Members of the unit have reported overall satisfaction with the system and they have unanimously expressed a desire to make the change.  The response from this team suggests that Cornell would consider migrating the the Resource Manager system even if 2CUL were not a factor.
  • Discovery & Access Team - Two public interfaces at Cornell rely on the Innovative ERM system currently.  D&A has been considering updating these services to utilize the Integration Layer data or other systems, rather than Innovative.  They are examining this in depth during their February sprint.  It is likely that they will be able to replicate these services using a combination of Voyager data incorporated into the integration layer, the License Term API provided by RM, and the RM journal A-Z list interface.  More detail about this can be found in Appendix 2: Implementation Details.
  • Technical and Data loading group (Gary Branch, Heather Shipman, Peter Martinez, Pete Hoyt, Chris Manly) -
    • Record loads - The group discussed how the current processes for updating Voyager, Innovative, and Serials Solutions will be affected by the transition.  They raised no concerns about making the change to RM and feel that any changes that are required in scripts or processes will be minimal.  Heather feels that the record loads into the Innovative ERM currently account for up to 24 hours every month.  This time can potentially be recouped, or used to manage more frequent updates from RM to Voyager.  Either way, we save some time or keep systems in better sync.
    • System hosting (Chris Manly) - The Innovative ERM system is locally hosted on a Cornell IT server.  This requires regular maintenance and updates in addition to a $2000/year fee.  RM and 360 COUNTER are cloud-hosted systems, managed by Serials Solutions.  The cost for this service is included in the annual fee structure for the services.
  • Usage Statistics group (Rich Entlich, Sally Lockwood) - Looked at the 360 COUNTER product.  Cornell Trial began 1/22.  Detailed feedback may not come until Feb 7 or later.  The initial assumption is that it will benefit 2CUL to have the COUNTER data from both partners in the same system.  The testing team is determining if there are any show-stopper issues that would impact operations.
  • 2CUL TSI E-Resources Team - Our team concentrated on the overall picture and have been impressed with the potential we see for our TSI work.  We particularly focused on articulating how the RM-CE layer will be initially populated and workflow issues that arise from working in a consortial system. 2CUL has not had an opportunity to trial the consortial aspects of RM-CE, the pricing offer provided by Serials Solutions (see pricing below) assumes that the first year of work in the consortial environment will be a pilot.  We have worked out an implementation model with Serials Solutions and will test various use cases in a sandbox version before going live.

4.       Is the product needed at both institutions?

...

Batch loading cost data - not necessary during implementation, but should be started

Statement from original charge:

Make a specific recommendation on whether to implement the Consortial Version of Serials Solutions at both institutions or hold off on integrating e-resource management and data migration until we have a shared LMS

Summary:

The 2CUL TSI E-Resources Team strongly recommends that 2CUL license and implement the Serials Solutions Resource Manager system at the consortial level.  This will involve Cornell implementing the Serials Solutions RM and 360 COUNTER systems locally as well.

Expectations

  • Get the partner libraries onto a common e-resource management system as soon as possible to:
    • Develop and implement joint workflows
    • Organize data for future transition to Alma

...