| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | Check-in / Logistics / Any issues with testing? | Report any major changes in availability / circumstances Anything to report on the test load? Progress on authentication integration for new-to-Alma campuses? UCLA, UCM | 10 | Carlo | | | |
| 2 | Exclude from discovery network - possible decision to harmonize | | 10 | Sarah | Sarah reported having trouble excluding some items from the discovery network (not the same as the NZ). Sarah opened a BC ticket. It is possible to exclude physical items from the DN. Other consortia don’t seem to have figured this out (CSU, SUNY have equipment displaying for example). Suppression is another way to deal with it. NRLF special collections look requestable (another example of things that could be excluded). Sarah is still processing what’s possible but it looks promising. She invited ICs to review the ticket also. One solution would be to submit all the physical locations to ExL to exclude. Only ExL can manage this configuration. Can be excluded by Location, resource type or MARC field. Can we all agree on one MARC field to all use? Each IZ can decide for themselves. However, ensure one campus doesn’t define a criteria that would affect another campus accidentally.
| - ICs to check if they have physical equipment showing in Primo.
- Sarah Lindsey to share the “Exclude from discovery network” decision to PPC for assignment. Here’s her BC ticket.
| |
| 3 | ILS Data cleanup / Patron Data groups / PPC | ILS Data Cleanup (Tom): co-chairs visit on 3rd Thursdays. TJ Kao and/or Catherine Busselen will join on 5/20. Patron Data (Greg) PPC: Review final decisions (as needed) SILS Chairs/Coordinators meeting update & actions
| 5 | Carlo, Tom | | | |
| 4 | Implementation buddy (contact list and email list) | Direct access: Campus contacts list for everyone doing configuration and sys admin/IT backend work. Broad discussion or not sure who to contact: Will the UC Alma email list (google group) suffice? Do we need a special email list just for implementation with staff who are doing configuration and sys admin/IT backend work? What info. would be helpful to include on the contact list? pre-migration ILS, pre-migration discovery system, law school, major integrations, etc. (See Criteria for Matching table from Buddy system)
| 15 | Carlo, Tom | Inspired by Gillian taking 30 minutes to help walk Carlo through a configuration - super helpful! Working together will be more helpful than relying on ExL. Sarah/Gillian confirmed UC Alma list is quiet and it’s fine to post implementation questions on this list. This means, we would need to get staff who are making configurations and doing IT backend work need to subscribe to the UC Alma list.
| | - ICs to fill out the Campus contacts list for their campus (optional, no pressure)
- Lena Zentall (Unlicensed) will add the criteria for matching - add a sheet to the contacts doc.
- ICs to encourage staff who are making configurations and doing backend IT work to subscribe to the UC Alma list.
|
| 5 | Timeline review / PM update | Stay up to date on timeline / deadlines Any topics that are not currently scheduled that need to be covered? See Basecamp Project Meetings. Feel free to request special meeting topics. | 5 | Lena | Any questions on the timeline? For “Request a consultant” meetings, please submit your questions at the time you request the meeting.
Current Cutover Plan Status: Steps 2&3: - Basecamp CO To Do List work in process Step 4: Thurs April 22 (estimated) – Marci will send PMs/ICs CO plan for review UPDATE - Marci/Laurie will submit Cutover plan to PMs on Monday April 26th (posted on PM planning BaseCamp) PMs will share public BC link with ICs and PPC PMs to ask ICs and PPC that questions be submitted before the 4/29 meeting. Feed questions to ExL as they come in on this google doc. Related - Thurs April 22 – Fiscal Close meeting – will provide TS freeze days (even if delayed for PM/IC full CO plan release) Step 4.5: Thurs April 29 – Marci/Laurie review CO plan during UCS PM/ICS meeting
Step 5: Thurs May 6 – Marci/Laurie review CO plan during all UCS staff office hours
| Invite PPC to the IC meeting. | |
| 6 | Primo VE workshop (week of May 17): which environment to use for training? | Determine how we will decide. Does anyone want to opt out? Davis ? but prefers UCSD  Irvine Riverside Los Angeles - not a hard “no” but we have been used a lot and would value seeing another institution’s instance Merced - We are okay with being used, but Primo VE is not fully tested / configured. San Diego Berkeley - opt out San Francisco - opt out Santa Barbara - opt out Santa Cruz - opt out
Marci suggests we decide by 2 weeks prior to the Workshop start (by April 30) How will we decide?
| 5 | Lena | | Riverside is our winner! | |
| 7 | Questions from slack | (Gillian, 4/19): how long will we have access to our NA04 environments after go-live on NA07? Answer Current v. SILS products (scroll to the bottom) Current Alma and Primo/Primo VE environments will be decommissioned at Go Live. In essence, campuses are transferring their existing Alma and Primo (UCD, UCSB) or Primo VE (UCI, UCR, UCSC) subscriptions over to the new environment at Go Live.
There is, however, a 3-month continuation post-Go Live for these Ex Libris solutions (and the related campus/es): Voyager (UCLA only) Intota (UCLA only) SFX and SFX KnowledgeBase (CDL and all campuses) Summon (UCLA and UCSF only) 360 Resource Manager (CDL)
(Jackie): Are there plans for members outside of CDL to attend the NZ training? (Jeremy) VDX/NCIP https://3.basecamp.com/3765443/buckets/15553579/messages/3686436265 (Lakshmi) Premium Sandbox question: Add the answer to this Confluence page that has Decommissioning details at the bottom. For the current Alma campuses, they will lose access to their current sandboxes at Go Live. Premium sandbox will be populated (data copied) when UC is ready (e.g., cleanup may be desired first, etc.) and makes the request to ExL. (Not sure how long it takes)
(Gem) On the IC channel a while back there was a question about how to access the ELUNA Document repository. It turns out there's one username/password for everyone so access information has been added to the Membership in ELUNA document: https://docs.google.com/document/d/1025shKzczXIsDFr99xepaSAPNFHVfpH2GaZqo0EV5sk/edit May 29-30 downtime - what happens to jobs that are scheduled to run?
| TBD | | Gillian’s question: Are other already-Alma campuses concerned? Yes, UCI is also concerned. Will the old production environment be accessible on a limited basis to check if anything is missing? The premium sandbox wouldn’t be the helpful since it won’t be refreshed and they are not keeping the configs up to date. This is a best practice. Lakshmi will draft an email. (Jackie): Are there plans for members outside of CDL to attend the NZ training? No. It’s intended for CDL staff who are working in the NZ. Working with RMFG co-chairs closely on use cases for access to the NZ and work that needs to be done at the NZ level. Will these be recorded? Jeremy on VDX/NCIP: Alison will paste Joe’s question into the exL food bowl for the 4/29 meeting.
| | |
| 8 | Other / Homework | | 5 | Tom | | | |
| 9 | Q&A (recurring) | Q&A during the IC meeting as a first stop before asking a question on Basecamp. If it’s time-sensitive, post to slack (IC channel, SILS Chairs are good options) Any issues that we want to seek broader input from other consortia? | TBD | Carlo | | | |
| 10 | Questions for Ex Libris PM (recurring) Post questions in Basecamp as they come up. It’s open 24/7! | Note: We lose in efficiency and we may lose in translation when questions go through the PMs. When topics come up that should logically go to Basecamp to the Ex Libris consultants, invite an IC (or appropriate person) to take point on that issue. | 0 | Lena | | | |
| 11 | Parking lot | | 0 | | UCD Escalation (3/17): Requested a meeting with ExL. (If needed) Best practices/guidelines for APIs. Awareness that NA04-NA07 servers are being physically moved to a new location over Memorial Day weekend and there will be a scheduled downtime from May 29 8pm PT to May 30 8pm PT.
| | |
| 12 | | TOTAL | 90/90 | | Review decisions and actions. | | |