...
- Cornell license and implement the Resource Manager (RM) system. This will replace Cornell's Innovative Interfaces ERM system. Columbia already licenses this product.
- Cornell license and implement the Serials Solutions 360 COUNTER usage statistics service. This will effectively take the place of Cornell's current usage stats wiki updating process. Columbia already licences licenses this product.
- 2CUL license and implement the Resource Manager Consortial Edition (RM-CE).
- We effectively communicate with key stakeholders before, during, and after the transition.
Cost / Savings (detail provided in Costs section below): We estimate that the overall costs of implementing these systems across 2CUL will be recovered amortized over the first two years, mostly in the form of opportunity saving from staff time that can be dedicated to other e-resource efforts*.*
Costs to Cornell:
- $26,143 year one license fees, $7,651 implementation fees, $8,200 implementation staff time
- $26,143 year two+ license fees
...
- $10,000 annually for Innovative contract and server maintenance fees
- $37,600 annual opportunity cost savings by freeing staff time with RM efficiencies, usage stats management efficiency,and 2CUL collaborative efforts
Savings to Columbia:
- stats management efficiency, and 2CUL collaborative efforts. This could potentially be greater.
Savings to Columbia:
- $12,000 annual opportunity cost savings by freeing staff time with 2CUL collaborative efforts. This could potentially be greater.
In addition, we feel that the following benefits are very important for our work together as 2CUL, but are difficult to assign dollar value to at this time:
- System migration costs will be lower if we are migrating together from a shared system to Alma.
- The acquisitions migration in general will be less rocky if we have worked together toward a common goal. Acquisitions has been the most difficult function to migrate and it should not be compounded by needing to learn how to work with each other and understand each others' different systems and workflows.
- It will be easier to collaborate on purchasing and trouble shooting.
- There will be substantial costs in staff morale and buy-in if we delay deep collaboration in this area. We have critical staff support right now.
- A shared system develops a common vision for e-resource work. This saves time in cross training and project planning.
- We have Serials Solutions staff on board right now to help and there is a price break. Delay might change this landscape.
- We would be able to provide better service to our users. Shared problem solving, expertise and staff freed from some manual tasks will make response to problems more timely and efficient.
- Running reports would be simplified, allowing ready access to data for further cost saving initiatives.$12,000 opportunity cost savings by freeing staff time with 2CUL collaborative efforts
Timeline: Ideally, we require a decision to move forward with this by mid-March in order to be able to migrate to the new systems by the summer 2014.
...
License fees: $10,450/year plus onetime set up $688
Funding sources: Collection Development and Research & Assessment will benefit the most from 360 COUNTER.
Benefits and potential savings:
...
Benefits and potential savings: We estimate that starting with year 2, 2CUL will begin to see opportunity savings in the form of staff time freed to perform other activities. There are many opportunities to put this time to better use on other e-resource activities that have been unachievable previously. The initial areas listed below will be the first priorities to tackle as 2CUL work, and we estimate approximately 250125+ hours per year (5 hours per week) of savings from these efforts for each partner totalling totaling approximately $26$25,000 across 2CUL.
- 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 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 and shared workflow.
...
- 948 field: webfeatdb indicates that it is part of the list curated by the Database Review Committee
- 653 subject fields used to facilitate browsability by curated subjects.
- Various other subject, alternate titles, and description fields used for broader searching capabilities
- License terms to be held in RM, linked to from appropriate records . using License Data API
Cornell eJournals - There is potential to use the Serials Solutions journal A-Z list to provide this service. If not, the Discovery & Access team will have to decide if this is essential and how to implement it. The data to produce it is available in the relevant Voyager records and via the License Data API from RM. Currently, 899 codes are used in Voyager to match journals in a collection to their parent collection.
...
Consortial System Implementation - The specific details are still being worked out. The current plan is to replicate Columbia's Resource Manager data to populate the Consortial layer's "parent" 2CUL database, then linking that to the two "child" databases for Cornell and Columbia. Many resources will match up relatively easily after this first pass as the 2CUL partners have significant overlap in collections. We will identify project work to match other resources as appropriate. This may be a great area for Columbia's proposed staff member to work on. Time Estimate: 40 hours testing across e-resources staff. This is expected to continue to take some time from existing e-resource staff as we ideinfy identify and implement best practices.
...