...
Batch loading - Cornell batch processing and IT staff will need to review batch loads that involve the current ERM system
Public Interfaces
Staff time for migration - estimations
Data entry and matching:
- 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
License Entry - need to enter at least what Cornell currently has in III. Develop checklist for license record entry and maintenance.
Batch loading cost data - 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:
- Public Interfaces - Cornell's Database Name and EJournal searches are currently utilizing the Innovative ERM. These will need to be updated as described in appendix ???.
- Data Migration - Assistance from Columbia staff member
Appendix 1: Costs
Licensing the products:
...
- MARCIVE records? How do these fit in? Other sources of records?
- 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:
- 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
License Entry - need to enter at least what Cornell currently has in III. Develop checklist for license record entry and maintenance.
Batch loading cost data - 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:
- Public Interfaces - Cornell's Database Name and EJournal searches are currently utilizing the Innovative ERM. These will need to be updated as described in appendix ???.
- Data Migration - Assistance from Columbia staff member