[Hold for after 6/25] 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
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.