Professional services are doing their work before handing it to Migration.
Migration will begin to export SFX data, copy the NZ to a migration environment, and build the NZ starting then.
Most deliverables (and pre-cutover activities) are due on dates prior to Migration's start work.
The existing Alma campuses are doing their technical services freeze at EOD on July 9th - due to the fact the Migration team will begin copying their environment at that time.
So the answer is -- Cutover officially starts on Monday June 28th (although for HQ, this is our Sunday night, the 27th).
Reminder: Post cutover questions on Basecamp in the UCS Cutover Planning To Do list in the relevant action item. If there’s not an action item, use the message board.
Quick Q to already-Alma campuses: Did you get all the information you need about how to access your old environment post-go-live?
Let your website manager know that discovery links will need to reflect the change on July 27 (exact time TBD).
Decide as a team what time we want to go live on July 27th. How can we coordinate this to ensure we are all "open for business" at the agreed upon time? This could require weekend work. Are we willing/able to do that?
Sample searches to test Primo speed once we get our cutover instances:
should we all use the same search terms?
one search term that brings lots of results
one search term with few results
how many searches is enough? 5? 10? 100?
Share a spreadsheet so we can see results at a glance?
Possible next step: Create a draft sheet then consult with Discovery?
Please invite your EUOS member to your local imp team meeting to keep them informed.
Do the already-Almas have a checklist/countdown for go-live?
From Marci: The Go Live Readiness checklist is a version of what we sometimes refer to as generally as the Health Checklist. We’ll actually use the form formally two times during the full implementation portion of the project: once as you a readying for Go Live (so around the start of Cutover) and then a second time prior to the official Switch to Support. I have suggested to past projects for them to also use the form earlier on in the project themselves to track progress on what they have learned and completed implementing, and what areas may still need additional review. This helps both sides tremendously as we can work on focusing on earlier determined problematic areas. It’s also easier for your project team when it’s time to formally complete the checklist as it’s been already been “in progress” and could be kept up to date. Questions about Go Live Readiness Checklist and Certifications.
Laurie’s answer: A go-live job will be submitted for each campus but the jobs can be run simultaneously. In other words, all jobs are *not* submitted to a queue where one is run after the other; rather they can all be submitted at the same time and can all run at the same time.
6
Questions from slack
7
Other / Homework
0
Tom
8
Q&A (recurring)
Q&A during the IC meeting as a first stop before asking a question on Basecamp.
If it’s time-sensitive, post to slack (IC channel, SILS Chairs are good options)
Any issues that we want to seek broader input from other consortia?
TBD
Carlo
9
Questions for Ex Libris PM (recurring)
Post questions in Basecamp as they come up. It’s open 24/7!
Note: We lose in efficiency and we may lose in translation when questions go through the PMs. When topics come up that should logically go to Basecamp to the Ex Libris consultants, invite an IC (or appropriate person) to take point on that issue.
0
Lena
Answer from ExL: For reporting Alma or Primo slowness: Details are in the SalesForce Cases for Reporting Alma Slowness post from 5/7. It lists what information is to be included in the SF case.
10
Parking lot
0
UCD Escalation (3/17)
[from 5/6] Load and performance testing
(If needed) Best practices/guidelines for APIs.
Awareness that NA04-NA07 servers are being physically moved to a new location over Memorial Day weekend and there will be a scheduled downtime from May 29 6pm PT to May 30 6pm PT.