The tables below will be used to capture important notes for Cutover including actions that must be taken prior to migration as well as your library’s data migration preferences. Please follow the instructions included with each table. Please complete sections for colleges by April 29th.

Notes for Cutover (For Ex Libris and Colleges to Complete)

...

Issue Description	Action Items/Due Date (check when done)	Ready for Cutover?
Missed library/location combinations on migration form caused items to end up in UNASSIGNED	Ex L [action]; due 10 Jan 2022 College [action]; due 07 Jan 2022	Yes No
Some 852 fields in bib file have empty $a in addition to $a<library code)>causing them to go to UNASSIGNED	Ex L Olivia will manually remove the empty $a from the bib file if the number continues to be low. due - when EXL checks data and forms College [action]; due 07 Jan 2022	Yes No
item policies not created in migration	ExL See https://3.basecamp.com/3765443/buckets/23965261/messages/4585913518#__recording_4616563318 Migration has determined the cause of the problem--it will be fixed at Cutover. College Confirm item policies are created and applied when Cutover data is delivered in Alma	Yes No
Change local fields for migration	ExL Add 590 as local Add 500 as local Add 990 as local Add 991 as local College Confirm designated local fields on the BASELINE Migration Form once received

Migration Preferences (For Colleges to Complete)

Indicate your library’s migration preferences by selecting the appropriate check boxes below. Use the links in the header row to find background information and documentation to assist with each decision.

SERC_TITLE_KEY
SISAC_ID
OTHER:
I do need to identify specific parameters for SERC_TITLE_KEY or OTHER as described in the Backgrounder (OCLS and Ex Libris will follow up with you)