...
Tom Bustos , co-chair
Carlo Medina (Unlicensed) , co-chair
Lena Zentall (Unlicensed) , PM, need to leave by 3:15
guest, Adrian Petrisor
Discussion items
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: Two all-staff email templates have been drafted, one to celebrate go-live on July 27 (page 1), and another with delay messaging should your campus need to pivot (page 2). These were conceptualized as messaging from each UL, however we recognize individual campuses may wish to channel through an alternate communicator who was involved with the SILS project. In the successful launch email on page 1, the customizable areas are:
We are all optimistic that the delay message template found on page two will be a moot point by this time next Monday. However, it is important to have a backup plan, and it exists as a resource to be easily-customizable by your local implementation team. In the unlikely event that the delay email is sent to your staff early next week, the go-live message should be sent on the new launch date. We recognize the enormous crunch you are experiencing in this final week before go-live. If there is a local colleague you feel should be taking the lead on this communication, please forward and invite them to contact us with any questions or concerns. | 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.
| 20 | |||||||||
24 | Go-Live coordination
|
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.
| 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! | All | On #3: 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.
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? Create a matrix with when you can do configuration changes and data changes. | The ICs didn’t see any flags with the RMFG moratorium proposal. |
” You do not need to sign off on the Primo VE environment acceptancebefore we can makemaking data changes/config changes
| 3and/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? Update on MOU for API key use: Email is coming soon. Special meetings Thu, Jul 22: Office Hours Questions due by EOD Mon July 19th
Special meetings
| 4
| ||||||
6 | Parking lot | 0 |
| |||||||||
57 | TOTAL | 90/90 | Review decisions and actions. |
...