Update on ExL suppressing records - will ExL continue to do this post-go-live?
10
TJ, Catherine
2
Update on slowness concerns/meeting with Ex Libris
Very productive meeting. Ex Libris is very invested in ensuring our response times are good.
We were told that ExLibris will be actively and closely monitoring our implementation for performance issues.
If we have any issues during implementation, we should use the “Generate Tracking ID” option in Alma.
Once we switch from “project implementation” to “support”, the process for reporting will change.
Speed will vary from campus to campus based on utilization rates.
The warm-up tool was for the test-load, not for “warming up” the production systems.
10
Lena
3
Q&A (recurring) - urgent questions
Do you have a question to discuss at the meeting? Add it below with your name.
(Caitlin) Problem Reporting & Tracking subgroup will be making a “report a problem” page draft that will be up on the CDL website for Go Live. May we add the roster info for the ICs as campus contacts to that page?
(Jackie) In the initial report from ExL about Primo slowness sent to us on 4/22, the warm-up tool will be ready and deployed to prod in the July release. Was there a change from that report?
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.
Any other activities to call out specifically (or generally) in the sheet?
PMs to share with ICs that campuses should have a backup plan/checklist or response plan in the event they do not go live on 7/27 (removing website search boxes, links, etc.)
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?
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
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.