Clarification on Alma/Primo known issues page on Confluence: We have a suggestion to use it for product issues (Alma/Primo) that are controlled by Ex Libris; not for known issues as a result of CDL’s data clean-up and campus-level e-resources management (or non-migration related access issues that also may surface/be tracked).
Does everyone agree with this approach? Yes.
Do we need another list for internal known issues? Who manages it? Set it up decision page style so each group has one and it feeds into a consolidated view? (may be too much overhead?) - Return to this Q
Followup Qs re: Salesforce:
Will we see all of our ExL SF cases in one place, including for products that are not Alma/Primo, e.g., RefWorks, ProQuest, etc.?
Is it possible to choose whether to see all products or only Alma/Primo or is it one option for all?
FYI. Risk assessment for Go-Live
ICs to do local risk assessment and share select risks before Jul 1
Go Live Risks sheet (feel free to make a copy for your local imp team risk assessment)
Brainstorm mitigations together with ICs at Jul 1 or Jul 8 (Jeremy reported in chat that fiscal close makes Jul 1 a busy time.) Preference?
No special meetings are scheduled after this week. If you have a topic for Ex Libris to cover, Request a Special Meeting.
4
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
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.