| 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.
| 15 | All | | | |
| 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
| 45 | | | | |
| 3 | Go-Live coordination 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 | | 30 | Carlo, Tom | | | |
| 4 | Timeline review / PM update | Stay up to date on timeline / deadlines | 0 | Lena | Any questions on the timeline? 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. | | |