Determine any followup questions and requests for Ex Libris.
Determine any followup actions for UC.
Followup on how the cloud team addresses performance issues in real-time. Yes!
Ask for reports - what exactly do we need? when do we want it?
Consider doing automated load/response time testing internally now. UC time/bandwidth are likely an issue. A: UCB’s tool wouldn’t show the detail we need. Jeremy mentioned Selenium but not sure how it works with angularJS. No response from other ICs.
SLA (see meeting notes for relevant sections - link below)
Next steps for PMs to wrangle: Draft a formal followup to ExL with our questions and requests. It will be shared with ExL senior management.
SUNY was promised monthly reports and in 2 years only got 2 reports. We will likely need to be persistent in asking for reports.
Sarah reported the tool that sends context info to ExL that was mentioned during the call does not work well (if you refresh your screen, it doesn’t work)
Concern that academic research searching may be more esoteric and not repeat the same search terms. Thus, response time would not speed up over time for many searches.
No consensus on when we should get reports. We want a report that covers a period of longer than 5 days. Consult with ExL.
Set the expectation that we want regular reports.
2
Q&A (recurring) - urgent questions
Do you have a question to discuss at the meeting? Add it below with your name.
(Sarah) Update about the suppress from Discovery Network project
(Jackie) Is anyone adding the 899$a prior to bib extraction? Or do you plan to wait til after go-live?
(Lena on behalf of EUOS + Discovery) It would be helpful for campuses to list all their configurations on one page so that we all know what our different instances look like based on their configurations. This especially helps EUOS understand how campuses are alike and differ as they are figuring out the ways to message to users about what UC Library Search can do (e.g., support page, news releases). [I suggested they identify a key set of configs since there are MANY!)
GK: AFN related question: What is being used as the ID to look a patron up from another institution?
30
All
On #1: UCSD and UCB are aiming for noon; UCR and UCSB are not saying a time to staff or public. Disclaimer: Not publishing a time doesn’t mean you don’t have an internal project timeline for go-live – that’s critical.
On #2: Don’t add 899 yet! Testing is still happening. It might be ready for go-live or shortly after.
On #4: Not seeing the value considering the amount of work that might be involved. Often many configurations are involved in rendering things - that is, it needs context. Asking your local IC makes more sense. Not understanding the use case for needing to know what other campuses do. Patrons care about their campus Primo.
On #5: Jackie and Laksmi will get an answer to Gillian.
[from 6/3] Preference for allowing each campus to publicize a time individually
The ICs confirmed their preference to let each campus decide how/if to communicate an expected go-live time (or general range such as “morning” or “afternoon” or “by noon”). We have not found any dependencies that require coordination around a single time.
Important reminder to share out your timeline locally at your campus. Have you shared this information about when staff will no longer have access, etc. Have you shared the cutover plan with your library staff and department heads? Have you informed staff what will be happening during this process? We don’t want surprises.
[From 6/3] Decide which IZ(s) to use for the analytics workshop (in addition to the NZ).
Does anything gets “edited” during the analytics workshops?
No. It’s not possible to edit Alma data via Analytics.
How many IZs would you like to volunteer?
It’s completely up to UC to decide. One suggestion from the trainer is to use a different IZ each day.
Would you like your IZ demo’ed in the analytics workshop? (Poll on slack)
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
FYI. 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.
Q: 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.
Put decision about which IZs to use for the Analytics workshop in September in the parking lot until post-go-live.
@Lena Zentall (Unlicensed) to ask Marci Q: 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?
5
Parking lot
0
6
TOTAL
90/90
Review decisions and actions.
20
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu