2021-07-22 Meeting notes
Date
Jul 22, 2021 2-3:30 pm
Attendees
@Tom Bustos , co-chair
@Carlo Medina (Unlicensed) , co-chair
@Lakshmi Arunachalam
@Ramon Barcia
@Susan Boone
@Greg Ferguson
@Jackie Gosselar
@Lynne E. Grigsby
@Robin Gustafson
@Jeremy Hobbs
@Gillian Keleher
@Sarah Lindsey
@Caitlin Nelson
@Alison Ray (CDL)
@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 |
|
|
|
|
4 | Go-Live coordination
|
|
| 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?” 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 |
|
|
|
|
7 |
| TOTAL | 90/90 |
| Review decisions and actions.
|
|
|
20
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu