...
1. What is the problem we need to address?
Different systems used at each CUL for various functions is a Our team has identified that having different systems in place for managing our electronic resource collections is a significantly greater barrier to successful collaboration than simply having different workflows. E-resources work relies heavily on Electronic Resource Management systems and currently, Cornell and Columbia have different systems. The official delay of Alma implementation has highlights highlighted the need to find an interim solution that will allow us to develop more common workflows, identify and perform shared work, and be better able to troubleshoot and solve e-resource problems across 2CUL.
2. How will the product address this problem?
Resource Manager RM -
360 COUNTER - Data in a common place for joint data analysis, potential shared maintenance, and to take advantage of future enhancements in the 360 COUNTER system.
...
3. Has a trial taken place? What were the results?
Columbia has been using SSRM (2007) RM and 360 COUNTER (2009) systems in production since 2007 and 2009 respectively. Several Cornell staff have had read access to Columbia's systems for six months.
Cornell has had an active trial to SSRM RM since September 2013 and 360 COUNTER since mid-January 2014.
- 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 Resource Manager 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 SSRM, and the SSRM 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 SSRM 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 SSRM to Voyager. Either way, we save some time or keep systems in better sync.
- System hosting - 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. Resource Manager 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 SSRM service.
- 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.
2CUL has not had an opportunity to trial the consortial aspects of SSRMRM-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.
...
Yes. Resource Manager and 360 COUNTER already in place at Columbia. Both products are needed at Cornell to maximize common systems. Additionally, we propose to add a consortial layer allowing more interactivity between the partner institutionsadding the RM-CE layer requires that both partners be operating on the RM system.
5. What staff will use the product?
...
Costs (More details in appendix 1: Costs):
Licensing the products:
SSRM RM at Cornell - 11,693/year plus one time set up $1969 (includes data population services) and a onetime consultation fee of $3990
...
- Innovative ERM License fee - currently approximately $7,500-$8,000/year. This is paid until September 31, 2014.
- Innovative ERM server - Once we get through the migration to the linux VM, our server cost for the III ERM will be about $2000/year as the server is currently spec'd. (We may need to adjust its provisioning depending on actual performance once it's up and running in production.) The support contract with III is in the ballpark of $10K/year. Let me know if you need more specific numbers than that - chris
Summary: The net co
Staff time for migration - estimations
...