| | | | | | | |
---|
1 | Start recording! | Welcome! | 0 | All | | | |
2 | Quick announcements | | 0 | | | | |
3 | SILS co-chairs update | Awareness of project status in key areas. | 10 | Günter | |
|
|
4 | Go Live Readiness | Discuss questions and concerns with go-live testing. Awareness of risk mitigations. Discuss proposed process for reporting and tracking problems.
| 30 | Lena, Christine, Caitlin, Claudia | Reminder to FG chairs to make sure all testing needed is identified and communicated to teams. What questions or concerns do you have? Going live with Alma v. Primo, what’s the difference? Once you touch the data in Alma, you are in effect “live”/operational With Primo, you need to make the link to UC Library Search for it to be “live”
Refer to the cutover checklist and bring your questions to the cutover review on 7/15
Risk assessment & mitigations by ICs Identified the need to complete data acceptance and deliver fulfillment data by Sunday July 25 at 5pm at the latest (could be earlier, just not later). ExL has staff scheduled to do the work on Sunday (Israel time) Have a detailed test/QA plan and go-live checklist - know how long is needed. Time will be limited! Have a backup person who can do your work if needed. For the next 3 weeks, be available to do work and answer questions promptly (including on go-live weekend July 24-25) Lower risk: have a plan if internet or power is out.
Reporting & Tracking problems subgroup update (Caitlin, Claudia) Proposed process, with MVP for Go-Live Does this path make sense (roughly)? What constitutes an issue? Is it a bug or an opportunity to harmonize? e.g. are there patterns of issues that may be mitigated by a harmonized approach? (from chat) From chat: Is the problem reproducible? I like emphasizing reproducing it with someone else (as part of due diligence) What is the pathway for patrons to report problems?
From chat: Is the subgroup’s next step to make a proposal for the assumptions? Or is that a question for SILS Chairs? From chat: AEFG discussions have been re: discerning between electronic resources access reporting (our usual types of things that will persist in Alma) - what things are particular to migration and may or may not intersect w/ e-res troubleshooting. Will bring into the E-Res Subgroup Launch Session. Can you live with the MVP we are proposing? (1-3 weeks post Go-Live)
| | |
5 | Timeline review (recurring) Reminder: Implementation Timeline on Confluence for staff without access to Basecamp. | Awareness of what’s happening / coming soon in the project | 0 | PMs | | | |
6 | Communication Operation Leads update (recurring) | Awareness of communications activities. | 10 | Ben, Adrian | Escalation letter - has it been sent at your campus? Have staff been identified to handle messages? How we’ll communicate about go live (Com Leads) Can we add Outbound Linking to the 8/2 TH to get the word out to folks?
| | |
7 | Flagging any significant issues (recurring) | | 0 | | | | |
8 | Parking Lot Feel free to add a topic to the Proposed agenda topics page on Confluence | Capture important topics for future discussion | | | | | |
9 | | | 50/50 | | | | |