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)
Question from ExL: Is it OK to demo your IZ during the analytics workshop if Q’s arise that relate specifically to your campus' data? (for patron data or financial - no.) ICs will need to see the Qs to know if they can demo the data. (Added to ExLPM agenda to share with IT & ExL 7/20)
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.
Would you like your IZ demo’ed in the analytics workshop? (Polled on slack)
Yes: UCB, UCSF, UCSC
No: UCR, UCSB
ICs will need to see the Qs specific to their campus in advance to know if ExL can demo their IZ to answer the Q.
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.