Instructions for Serials solutions to spin up our live CE set-up. Assumptions I have for this are:
...
Do not copy and contacts as they were pretty mangled in the sandbox – we will use the Contact upload tool to load Columbia'sColumbia’s, then Cornell'sCornell’s. - yes
Do not copy any licenses over. Phase 2 License entry will handle entering licenses and/or any uploading we can manage. - yes
Do not copy Notes – these will be handled on a case-by-case basis- yes
Some of these assumptions are based on the following proposed workflows:
Contacts Workflow – All Contacts will be managed in CE and shared. Each local RM will inherit those that are needed and attach them to resources.
License Workflow – All Licenses will be input at CE (with the exception of Cornell's Cornell’s Phase 1 work). These will be shared to both CULs, and inherited as needed. These CE versions will be copied in the local RM, edited for local information (scanned license URL, Auth Users, other exceptions), then the copy will be attached to appropriate resources. Assumption: We will always need to copy the CE version of the license in the local RMs as we will have some local data to encode (Auth users, etc...)
...
§ Exactly the same content at each CUL and/or databases that do not have variation in title level access – manage at CE, share and inherit as needed. Examples- Springer eBook collection, EconLit, etc...etc…
§ Differing content – Manage at the local level. Examples – subscribed titles lists with Elsevier/Wiley.
...