ICs to do local risk assessment and share select risks before Jul 1
Go Live Risks sheet (feel free to make a copy for your local imp team risk assessment)
On Jul 1: Brainstorm mitigations together with ICs
Context: Timeframe for risks is from now until go-live and a little beyond, but not the transition to ongoing shared gov or CDL as OC. We aim to meet our day 1 MVP -- we won’t have everything decided and integrated. SILS will be a work in progress.
What is data acceptance? All of the written acceptances during Cutover are a way to inform EXL that you have reviewed your data/environment - and you are ready to move on to the next phase of Cutover. If a problem is found during your initial review, you must report your problems to EXL ASAP and EXL will work with you to find a resolution. You would however still have the ability to conditionally accept the data along with documenting the issues found and be able to move forward with the Cutover process. If a problem is found *after* Go Live, you would also notify EXL so we can work with you to find a resolution.
QUESTION: Does a non-Alma campus have a choice of whether to provide their fulfillment data before or after go live?
RESPONSE: No, this is *not* an option. If they want to migrate their fulfillment cutover data, it must be provided to ExL by the deadline of 5pm, July 26
QUESTION: could they go live and upload/enter the data themselves later?
RESPONSE: Once campuses are live, they can enter any data they want in Alma but post go-live, ExL is *not* able to migrate any additional data or assist with loading patron data other than:
Assisting campuses with troubleshooting the loading of their offline circ files if they used the Alma offline circ utility
Assisting campuses with troubleshooting SIS integration
[Hold for after 6/25] Clarification on Alma/Primo known issues page on Confluence: We have a suggestion to use it for product issues (Alma/Primo) that are controlled by Ex Libris; not for known issues as a result of CDL’s data clean-up and campus-level e-resources management (or non-migration related access issues that also may surface/be tracked).
Does everyone agree with this approach? Yes.
Do we need another list for internal known issues? Who manages it? Set it up decision page style so each group has one and it feeds into a consolidated view? (may be too much overhead?) - Return to this Q
Post go-live: Decide which IZ(s) to use for the analytics workshop (in addition to the NZ). Nothing will be edited during the demo. One suggestion from the trainer is to use a different IZ each day.
Would you like your IZ demo’ed in the analytics workshop? (Polled on slack)
Yes: UCB, UCSF, UCSC
No: UCR, UCSB
In preparation for the eventual switch from implementation to support (and to Salesforce exclusively), new-to-Alma ICs should consider who should have Salesforce accounts (have it in place before go-live). Understand best practices in opening cases. Ex Libris has a template. See Basecamp post.