(Jackie) How is UCLA/SRLF handling depositing library requests on restricted items? Are you guys managing this with CAIA?
Analytics are baked into other roles. Design analytics role – how do others understand this role? any concerns?
15
All
Are we voting individually or as a consortium?
From chat: I found this doc . . . https://docs.google.com/document/d/1025shKzczXIsDFr99xepaSAPNFHVfpH2GaZqo0EV5sk/edit (Not sure if that's open for all.) "Institution vs Consortium membership: Voting: ELUNA members can vote for product enhancements for products they license. Consortial members get 1 vote per consortium. Institutional members get 1 vote per institution. If you have both a consortial membership and an institution membership, you get “2” votes: one through the consortium, which is collaborative and one just for your institution, which would include any products you license which the consortium does not (e.g. Leganto, Esploro, etc.)"
No objections, but unclear if the testing will work.
Carlo is out. Jackie will reach out directly.
Design analytics:
UCSC emails reports in many cases. They have also given many people this role and they don’t see it heavily used. They asked staff to add their initials to reports they design. It’s not easy to use design analytics.
UCSB has power users with the role and they have best practices; they also email reports when possible. Reports folder that no one is allowed to touch.
Same at UCR.
Same at UCI as well. We have separate folders for each department in shared folders; follow best practices too
UCD: One of our Collection Strategies analysts created a dashboard for librarians
Lena Zentall (Unlicensed) Gem, Alison, Lena, Caitlin will discuss NERS voting on Monday (determine if our consortia account is active now for Alma/Primo, before we go live.)
AFN: Next week the MoU for API keys will be drafted for campuses to use with CDL. It will be a lightweight approach (email) format
Is there a speed at which we would not go live? Since we were told that Primo VE will be slow until it “warms up” do we need to add checking Primo speed to local test plans?
Understand if a campus is done with data verification, can they move onto functionality testing? Is there anything else that would change data that would affect others? What is the list of things to avoid? Confirm with ExL. ASK ON BASECAMP FOR 7/15 MEETING. Greg asked and the answer was “yes, fine to move on to functionality testing once fulfillment data is accepted.
Do you need a confirmation from ExL before you start doing any configuring? Or, does that happen implicitly once you sign off on data acceptance and fulfillment data (for non-almas) NO.
If instances are delivered earlier, we would like fulfillment processed earlier. At least one campus is aiming to provide their fulfillment data on Friday. They would like it run Friday night. How much advance notice does ExL need to be able to run fulfillment data earlier? e.g., run it Friday night rather than Sunday night. (Tom)
Still some confusion about go live steps and dependencies. Run through the timeline with what happens at each step of go live so each step and dependencies are clear. (Lena)
How soon would we get a report with what data failed in fulfillment data load? (Tom)
How long does it take to create premium sandbox? (Lynne)
When do we have access to analytics data? Takes one day to update per Gem.
What is data acceptance? All of the written acceptances during Cutover are a way to inform EXL that you have reviewed your data/environment - and you are ready to move on to the next phase of Cutover. If a problem is found during your initial review, you must report your problems to EXL ASAP and EXL will work with you to find a resolution. You would however still have the ability to conditionally accept the data along with documenting the issues found and be able to move forward with the Cutover process. If a problem is found *after* Go Live, you would also notify EXL so we can work with you to find a resolution.
Awareness Go Live Decision Plan is going to WG this Friday for approval. Any questions?
5
All
RMFG will suggest a freeze on updating NZ records until campuses verify their data and sign off on data acceptance. Bib-level data. Gem will discuss with ILSDC also.
FYI. Salesforce includes contacts for some people who don’t have access to Salesforce, e.g., procurement, managers, etc. Cleanup reminder: this should be done before cutover to support (end of October)
Note – Immediately after go-live, campus accounts will be shifted to go under the UCS umbrella. .
FYI. New group investigating reporting & tracking systemwide issues: Caitlin and Claudia Horning volunteered for the group at the 6/30 SILS chairs meeting. Nothing to report yet.
FYI. Notes in comments field will follow in resource sharing request coming in July release!
Good to know…Existing Almas on NA02/NA04 will be locked and blocked by ExL once the migration analyst begins the export. Some exports may begin as early as 5:15pm on July 9 (right after your technical and fulfillment services freeze) but not all will be started that early. The actual start of the export is dependent on the availability of migration resources. So not all existing Almas will be automatically locked right after 5pm PT on 7/9 but the expectation is that they will be locked sometime between July 9 5pm PT and July 14 EOD.
No NA07 environments are locked by ExL.
Special meetings
July 15 Cutover Preparation Delivery Review special meeting
Please forward the invite to anyone who should be there or may have questions.
Add any questions on this meeting on Basecampdue EOD on Tues July 13; Laurie will follow up on leftover questions after the meeting
ILSDC 7/15: Update on ExL suppressing records - will ExL continue to do this post-go-live.
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.