...
Appendix 2: Implementation Details
Cornell Database Names - Responsible parties - Discovery & Access Team (interface design and implementation), E-Resource Staff (Record management and license entry)
- 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
Responsible parties - Discovery & Access Team (interface design and implementation), E-Resource Staff (Record management and license entry)
****eJournals - D&A or Serials Solutions A-Z list?
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.
Batch Loading - Responsible parties - Batch Loading ( Pete Hoyt, Chris Manly), Gary Branch, Heather Shipman, Jesse Koennecke )- This group will address any issues that arise related to batch loads between Serials Solutions / Voyager / ERM interaction899 Codes, Voyager, and the Innovative ERM. We expect the required changes to be minimal although there may be potential to overhaul the processes more thoroughly in the future.
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.
...
- How do we handle resources where we get records from other third parties? I.E. MARCIVE, OCLC, Vendors?
- Does Columbia data as "parent" help or hinder?
- Workflow - what goes in CE layer, what goes in local? Are there one or more clear scenarios for this?
Staff time for migration - estimations
Data entry and matching collections - These aspects of migration from Innovative to RM, and connecting Cornell and Columbia's RM collections to the parent RM-CE records to be the most labor intensive aspects of implementation. Most of this work can be accomplished by e-resource staff. The goal is to sync as much as possible between the 2CUL collections records. The following staff will be essential for making this work smoothly and quickly:
- Columbia position - Columbia has offered to contribute the services of a full-time staff position to assist Cornell in making the transition to RM. This position will assist in the move to the Consortial version of RM as well. The position is at the same level as the current staff in Electronic Resources at Columbia.
- Various other E-Resources staff - All of Cornell's E-Resources Unit staff are prepared to spend time in the coming months. They are eager to see this work well and the process of updating data will give them valuable experience using all of the systems. Columbia's E-resources staff will help guide the process with their experience in the systems and well also concentrate on ensuring that Columbia's records match properly in the RM-CE.
License Record Entry - Cornell staff will need to enter license data to match at least what Cornell is currently has entered in III. Develop checklist for license record entry and maintenancethe Innovative system. Some of this will be able to be migrated, but there will also be some manual entry and updating required.
Batch loading cost data - This is not necessary during implementation, but should be started
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
Cornell Resource Manager and 360 COUNTER Implementation plan:
...
as early as possible to have resource cost data included in the system. This data can then be examined across 2CUL collections and utilized by the 360 COUNTER Service to estimate cost-per-use.