Typically, Marci and migration consultant work directly with the PM on the client side on the project plan for cutover. For UC, that conversation is happening directly with the ICs and PPC since UC has set up a process that brings ICs into the process for timeline approvals.
Laurie gave an overview of the cutover migration process for IZs and freezes. She will share her powerpoint as a preview to the May 6 meeting.
ExL is still working to see if they can provide access after go-live to former production environments. It’s an ongoing conversation and Marci will add a line item to the Cutover plan to reflect the final decision.
Why can’t we do testing on NA07 after the lockout/copy is made. ExL has had problems in the past with this. Even with a single project implementation, it’s complex. People have made changes to configs after the lockout/freeze that have been problematic. Laurie added if migration analysts can progress faster, they may start copying early. You don’t want anyone in the environment making changes.
Deadlines are always by 5pm Pacific Time
Tech Svcs freeze is when the library ceases all updates to its catalog/inventory, e-resources, acquisitions and course data.
Fulfillment freeze
for fulfillment freeze, do we know whether that includes bills (fines/fees) in addition to open charges/recalls/holds? It includes everything
Data extracts and forms deadlines
live Almas: June 18 (MARC bib records only) for building the NZ
Non-Almas: June 18 All ILS data
360 (UCLA, CDL): June 18
Non-Almas, fulfillment extracts only: July 26
Data review and testing on NA07: July 23-26
Laurie is working on the timing of updating the CName to direct to new production environment on NA07.
Basecamp Cutover List
About the FY rollover, Laurie said that EXL needs to know if it takes place before the cutover or after the cutover. Which cutover date is that?: June 18th or July 9th?
Keep libraries, locations, vendors in NA07 in sync with your ILS. (They are only added once at Test Load and must be updated in Alma if anything is added/changed later in your ILS)
What does frozen mean for SFX? It includes jobs too. They could interrupt a data extraction.
Any recommendations for us if one campus finds something and wants to share in case other campuses find the same thing? Laurie has seen it managed with a document shared by all. Marci recommends sharing what was found at Test Load since it could be similar things at cutover.
Jeremy asked “At cutover on July 9th, does our Primo turn off as well, or does it remain online? if it remains online, then we would need to turn off requesting and other electronic services, right?” Marci will get the answer from Laurie.
The plan is tight. Most projects have 1-2 days for testing. If environments are delivered early you can signoff and give fulfillment data earlier than Monday Jul 26. At the time you pull the fulfillment data is when it’s frozen.
If we’re doing all this work on July 27, what does that mean for patrons and staff that are expecting us to be live on July 27? We need to set the expectation. No one is expecting go live is 5pm on July 27
Primo will still be available after freeze but you have to turn off requesting. Will link resolving work? It should work but Laurie will confirm.
Q&A will have questions added to it and Marci will post it on Basecamp since others are likely to have the same questions. Marci has noted all the chat questions to be answered later. Laurie will start a BC thread with open Primo questions separately.