| Item | | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | ILSDC | Update on ExL suppressing records - will ExL continue to do this post-go-live? | 10 | TJ, Catherine | | | |
| 2 | Update on slowness concerns/meeting with Ex Libris | Very productive meeting. Ex Libris is very invested in ensuring our response times are good. We were told that ExLibris will be actively and closely monitoring our implementation for performance issues. If we have any issues during implementation, we should use the “Generate Tracking ID” option in Alma. Once we switch from “project implementation” to “support”, the process for reporting will change. Speed will vary from campus to campus based on utilization rates. The warm-up tool was for the test-load, not for “warming up” the production systems.
| 10 | Lena | | | |
| 3 | Q&A (recurring) - urgent questions | Do you have a question to discuss at the meeting? Add it below with your name.
| 20 | | | | |
| 4 | Go-Live coordination | Actions from risk mitigation to followup on. New column added for “OK to test”. “Live” in Alma is once you have done data acceptance, fulfillment acceptance, and you start making changes, you are essentially live in Alma. And you decide not to go live, we must let Ex Libris know.
| | All | | | |
| 5 | Timeline review / PM update | Stay up to date on timeline / deadlines | 0 | Lena | Any questions on the timeline? Update on MOU for API key use. Special meetings | | |
| 6 | Parking lot | | 0 | | 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.
| | |
| 7 | | TOTAL | 90/90 | | Review decisions and actions. | | |