Page Comparison

Check-in / Logistics / Any issues with testing?

1. Report any major changes in availability / circumstances

2. Anything to report on the test load?

15

Tom

Progress on integrations work

1. Round-robin to see how everyone is doing on integrations work.

   1. For non-alma campuses, where are you at in the patron update (SIS loader) process?

   2. Progress or changes to your 3rd party integrations plans? (refer to your forms on Basecamp)

20

Tom

Integrations:

• UCB

• UCLA

• UCM

• UCSD

• UCSF

• CDL

Authentication:

• UCLA:

• Merced:

• Berkeley LBL:

SIS loader:

• UCB

• UCLA

• UCM

• UCSD

• UCSF

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 TBD.

• Patron Data (Greg)

• PPC: Review final decisions (as needed)

• SILS Chairs/Coordinators meeting update & actions

5

Tom

• Patron Data:

• ILSDC:

• PPC: decision on CDI - EasyActive

• Coordinators:

Timeline review / PM update

• Basecamp To-Dos

• Working copy timeline

• SILS Implementation Timeline

• Timeline Feedback Plan for the process of approving the timeline with ICs

• Basecamp Project Meetings

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?

• Update on Alma slowness issue:

• What is the official date that Cutover begins? EXL considers the start of Cutover to be the day when the Migration Team begins their work. For the UCS, it will start Monday June 28th.

  1. Migration will begin to export SFX data, copy the NZ to a migration environment, and build the NZ starting then.

  2. Most deliverables (and pre-cutover activities) are due on dates prior to Migration's start work.

  3. The existing Alma campuses are doing their technical services freeze at EOD on July 9th - due to the fact the Migration team will begin copying their environment at that time.

  4. So the answer is -- Cutover officially starts on Monday June 28th (although for HQ, this is our Sunday night, the 27th).

Go-Live Discussions

Cutover planning on basecamp

Timeline on confluence

Getting prepared for go-live

• Let your website manager know that discovery links will need to reflect the change on July 27 (exact time TBD).

• Decide as a team what time we want to go live on July 27th. How can we coordinate this to ensure we are all "open for business" at the agreed upon time? This could require weekend work. Are we willing/able to do that?

• If a campus is not ready to go, do we all agree to go live without that campus?

• Sample searches to test Primo speed once we get our cutover instances:

  • should we all use the same search terms?

  • one search term that brings lots of results

  • one search term with few results

  • how many searches is enough? 5? 10? 100?

  • Share a spreadsheet so we can see results at a glance?

  • Possible next step: Create a draft sheet then consult with Discovery?

• Please invite your EUOS member to your local imp team meeting.

• Do the already-Almas have a checklist/countdown for go-live?

• This informative BC post regarding the use of the Health Checklist and it’s relationship with Go Live was unfortunately archived - so Marci unarchived it today for reference - especially as we will use the form or a similar one as we prepare for your switch to Support: Questions about Go Live Readiness Checklist and Certifications.

30

Carlo

• Do Health checklist by May 17 for discussion at May 20 ExL meeting and upload to the Completed health checklist folder.

• Do we need to accommodate for ExL to run each go-live job consecutively or can they be run simultaneously (10 campuses + NZ)?

  • Marci added this question to the Cutover Planning To Do list under the Notify EXL you are ready for Go Live - EXL will run Go Live jobs [Alma Campuses]

    • Laurie’s answer: A go-live job will be submitted for each campus but the jobs can be run simultaneously. In other words, all jobs are *not* submitted to a queue where one is run after the other; rather they can all be submitted at the same time and can all run at the same time.  

Questions from slack

Other / Homework

0

Tom

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

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

• Answer from ExL: For reporting Alma or Primo slowness: Details are in the SalesForce Cases for Reporting Alma Slowness post from 5/7. It lists what information is to be included in the SF case.

Parking lot

0

• UCD Escalation (3/17)

• [from 5/6] Load and performance testing

• (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 6pm PT to May 30 6pm PT.

TOTAL

90/90

Review decisions and actions.