| 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 | Followup Qs: Will we be in “red” when we go live as we saw with other customers in the report Omri showed us or will the use of the warmup tool make our go-live faster so we don’t start out in the red? (We think the answer is “no” but just confirming.) What did your testing of the warmup tool show?
| | |
| 3 | Q&A (recurring) - urgent questions | Do you have a question to discuss at the meeting? Add it below with your name. (Caitlin) Problem Reporting & Tracking subgroup will be making a “report a problem” page draft that will be up on the CDL website for Go Live. May we add the roster info for the ICs as campus contacts to that page? (Jackie) In the initial report from ExL about Primo slowness sent to us on 4/22, the warm-up tool will be ready and deployed to prod in the July release. Was there a change from that report? (Gem) NERS voting; discussion
| 20 | | Problem reporting & tracking: May we add the roster info for the ICs as campus contacts to that page? If you want to identify someone else, that’s fine. Yes. Know that the process will be iterative. This primary focus today is on MVP month 1. Caitlin and Claudia will share a draft of the final document with the ICs.
Answered above NERS voting, round 2 (shorter list of items since it’s been narrowed in round 1): What method should we use? UCSC liked 10 items and split their vote 10 points across each of the 10 items. Gem proposes for those with more than 20 votes, give heavier weight and then spread out the points over the others. Agreement from ICs with this method. We’ll revisit how we do NERS voting in the future. We needed to get this done quickly this time.
| Agreement to add the roster info for the ICs as campus contacts to that page. Let Caitlin/Claudia know if someone else should be named instead of the IC. NERS voting: Gem will give heavier weight to those items ICs allocated more than 20 points to on the enhancements voting sheet, and then spread out the remaining vote points over the other items ICs gave points to. Agreement from ICs with this method. | |
| 4 | Go-Live coordination | RMFG would like to ask the ICs to consider the following proposed moratorium: https://docs.google.com/document/d/17mjkSciGMa82PKwUrwVVsAwkXkk6QEK9IYvykl6DAg0/edit after our environments are delivered. It would be much shorter than Vanguard or Test Load and will hopefully be lifted on 7/27 - Looks good. Communicate on the all-cohort channel - any issues that need to be known broadly. Also, announce when you are live on Alma, and then live on Primo. Actions from risk mitigation to followup on. New column added to Go Live Status sheet for “OK to test”. Share with your local imp team…anyone who changed data in their ILS after the tech services freeze should know that search results may have discrepancies as you are comparing search results in Alma to your old ILS. Make sure everyone who is doing testing knows this at your campus. (Laurie also mentioned this at the Alma Data Review meeting mid-July.) “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. The WG approved the Go Live Decision Plan. One bullet point was added: “Tuesday, July 27: As each campus goes live on Alma and Primo VE, the IC should post a Slack all-cohort message and update the go live sheet. Any other activities to call out specifically (or generally) in the sheet? PMs to share with ICs that campuses should have a backup plan/checklist or response plan in the event they do not go live on 7/27 (removing website search boxes, links, etc.)
| | All | Lena will check the actions from risk mitigation and flag anything that needs to be done. Move Primo environment acceptance column before Go Live in the Go Live status sheet. Done! Do we need to sign off on Primo environment acceptance before we can make data changes/config changes? Create a matrix with when you can do configuration changes and data changes.
| | - Lena Zentall (Unlicensed) will check the actions from IC risk mitigation and flag anything that needs to be done.
- Lakshmi Arunachalam will ask EXL if we need to sign off on Primo environment acceptance before we can make data changes/config changes
- Lena Zentall (Unlicensed) to create a matrix showing when you can do configuration changes and data changes (considering signoffs and bib moratorium).
|
| 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: Email is coming soon. Special meetings | | Lena Zentall (Unlicensed) to report to ExLPM and IT that ICs will need to see the Qs specific to their campus in advance to know if they can demo their data for the Analytics workshop. |
| 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. | | |