| Item | | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | IC’s role in the ExL payment process | Review the ICs role in the ExL payment process and answer any Q’s. | 15 (at 2:00) | Chris Shaffer, SILS co-chair | | | |
| 2 | Communication to all-staff | Respond to any questions about the communication to all-staff about SILS go live | 15 (at 2:30) | Adrian Petrisor, Com Leads | | | |
| 3 | Q&A (recurring) - urgent questions | Do you have a question to discuss at the meeting? Add it below with your name. Alison: Another surprise configuration activity for IZs: “Custom linking for Central Index databases”; preferably before (or very close to) PrimoVE golive Naxos Music + Jazz: replace ‘INSTITUTIONID’ with ‘univportal’ GaleGroup: change <Service_ID> to primo & <Location_ID> with your campus value
| 20 | | | | |
| 4 | Go-Live coordination | Confirm what it means to be “live” on Alma and Primo. See Go Live Status sheet - definitions at bottom of the sheet. 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. PMs to share with ICs that campuses should have a response plan/checklist in the event they do not go live on 7/27 (e.g., remove library website search boxes and links; inform stakeholders, etc.)
Lena will check the actions from IC risk mitigation and flag anything that needs to be done. Done! ICs have been reminded of all actions. Followup: Do we need to sign off on Primo environment acceptance before we can make data changes/config changes?
(posted on BC 7/20)Create a matrix with when you can do configuration changes and data changes: https://docs.google.com/spreadsheets/d/1P758aBoQQ7AxfLxDJFUHfutfBPrYQam-_h1TR60kx9g/edit#gid=0
(posted draft on BC 7/20 to check if it’s accurate)All Done!
| | All | On #4: Response from ExL on when data and configurations can be made https://3.basecamp.com/3765443/buckets/15553579/todos/3849458782 It has always been EXL’s suggestion to not make any changes in Alma (data or configuration) until after all acceptances have been completed. In the case of the UCS, there has however been a demand for making changes to both data and configuration earlier if and when possible. In terms of data, the chart is accurate. Existing Alma campuses can make data changes AFTER Alma data acceptance. New-to-Alma campuses can make data changes AFTER Fulfillment data acceptance (which happens following their Alma data acceptance and Fulfillment Cutover).
In terms of configuration changes, it is still EXL’s best suggested practice to make changes only after Alma and Fulfillment data acceptances are complete (the latter applicable for the new-to-Almas). If there any configuration changes made prior to Fulfilment Cutover acceptance, please avoid making any changes that would affect Fulfillment data or its subsequent testing. Question: “Do we need to sign off on Primo environment acceptance before we can make data changes/config changes?” You do not need to sign off on the Primo VE environment before making data and/or configuration changes in Alma – HOWEVER be sure that your Primo VE testers are aware of any changes that you are making in Alma while they are testing and working to accept Primo VE. | | |
| 5 | Timeline review / PM update | Stay up to date on timeline / deadlines | 0 | Lena | Any questions on the timeline? 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. | | |