| Item | | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | Q&A (recurring) - urgent questions | Do you have a question to discuss at the meeting? Add it below with your name. (Jackie) NCIP security issue (Lynne) API keys & security update
| 15 | All | Jackie noticed an NCIP security issue on the Alma list. Jackie will open a SF case. Data Privacy task force will make recommendations to the WG in a couple of weeks. One of those recommendations is an MOU for CDL to have access to campus APIs.
| | |
| 2 | Go Live Risk Assessment | 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.
| 45 | All | Understand if a campus is done with data verification, can they move onto functionality testing? Is there anything else that would change data that would affect others? What is the list of things to avoid? Confirm with ExL. Do you need a confirmation from ExL before you start doing any configuring? Or, does that happen implicitly once you sign off on data acceptance and fulfillment data (for non-almas) How much advance notice does ExL need to be able to run fulfillment data earlier? e.g., run it Friday night rather than Sunday night. Still some confusion about go live steps and dependencies. Run through the timeline with what happens at each step of go live so each step and dependencies are clear. How soon would we get a report with what data failed in fulfillment data load? If instances are delivered earlier, we would like fulfillment processed earlier. At least one campus is aiming to provide their fulfillment data on Friday. They would like it run Friday night.
| | |
| 3 | Go-Live coordination https://docs.google.com/spreadsheets/d/1iMBYDcm2-FwgPU7hsVTptaUgznoLPbHsxhtqRUhEFGU/edit#gid=0 - Tracking major deliverables https://docs.google.com/spreadsheets/d/1olDkcAsvX3pp1W-GY4MJvpu0C2I5Krkts_0wIN96fGI/edit#gid=1252460463 Alison’s go-live (day-of) countdown with hour by hour CDL work See reminders on 6/24 meeting notes | Discuss Go Live Decision Draft 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. | 30 | All + Chris and Günter, SILS co-chairs | | | |
| 4 | Timeline review / PM update | Stay up to date on timeline / deadlines | 0 | Lena | Any questions on the timeline? Lockout tip Premium sandboxes EXL is creating and refreshing Alma & Primo VE premium sandboxes 2x a year (2nd Sunday in February and August). Since the Go Live for UCS is expected July 27th, your premium sandboxes creation start will begin on Sunday August 8th.
Fulfillment data Special meetings | | |
| 5 | Parking lot | | 0 | | [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. 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.
| | |
| 6 | | TOTAL | 90/90 | | Review decisions and actions. | | |