2021-05-27 Meeting notes

TENTATIVE: ILSDC monthly checkin

TJ Kao, Catherine Busselen

Go-Live coordination

July 27 at time TBD

https://docs.google.com/spreadsheets/d/1olDkcAsvX3pp1W-GY4MJvpu0C2I5Krkts_0wIN96fGI/edit#gid=1252460463

Decide as a team what time we want to publicize for go-live on July 27th?

• Campuses will check with their teams on whether a noon go-live time works and report back on May 20.)

How can we coordinate to ensure we are all "open for business" at the agreed upon time? What’s our next step?

30

Carlo, Tom

Followup from Q’s last week:

What is the impact on the timeline if a campus does not meet the 6/18 deadline for sending NZ bibs?

• QUESTION: If someone is late providing their data (especially the bibs for the NZ build) can the NZ build still progress with the other campuses? 

  • RESPONSE: Yes

• QUESTION Can the late campus’ data be added to the NZ after Go Live?

  • RESPONSE: Yes, but they will need to use the tools in the Alma UI to load the data (rather than go through EXL Migration).

• Additionally - the NZ Load order should remain the same for Cutover as it was for Test Load

Laurie’s answer about if NZ has to delay go-live:

• QUESTION: What happens if we were to find a major problem with the NZ data and it couldn't be fixed in time. Could the IZs go live without the NZ?

  RESPONSE: The NZ is built first so if there are any issues, they will be addressed right away.  If there is a major issue, it will be addressed with the highest priority. 

  The IZs could go live even if the NZ isn’t available but they would of course not have access to full NZ functionality such as the AFN (automated fulfillment network).  Also, the discovery network scope in Primo would not be available.  

  • QUESTION: Related, what if there is a problem with one IZ's data.  Could the NZ and the other IZs go live without them?

    RESPONSE: Yes

• QUESTION: Does signing off on data acceptance clear ExL of responsibility? What does it mean to signoff?

  • RESPONSE: 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.

Progress on integrations work

Do you have anything to discuss at the meeting?

Report on progress on 3rd party integrations plans.

TBD

Tom

Update your status before the meeting

SIS loader: due April 30

• UCB:

• UCLA:

• UCM:

• UCSD:

• UCSF:

Other day 1 integrations: due May 31

• UCB:

• UCLA:

• UCM:

• UCSD:

• UCSF:

• CDL:

ILS Data cleanup / Patron Data / PPC

Do you have anything to discuss at the meeting?

• ILS Data Cleanup (Tom): co-chairs visit on 3rd Thursdays. TJ Kao and/or Catherine Busselen will join on June 17.

• Patron Data (Greg)

• PPC: Review final decisions (as needed)

• SILS Chairs/Coordinators meeting update & actions

TBD

Tom

Update your status before the meeting

98

Timeline review / PM update

• Basecamp To-Dos

• Cutover to do list

• Cutover preview Q&A

• Working copy timeline

• SILS Implementation Timeline

• Project Meetings (on basecamp and confluence)

• Document Alma/Primo slowness in SalesForce, see instructions.

Stay up to date on timeline / deadlines

5

Lena

Any questions on the timeline?

• Reminder: Email your technical freeze date(s) to the PMs at sils-exl-ucs-pm-l@listserv.ucop.edu by May 31

• Reminder: If you make changes in your existing production system after the freeze, besides needing to true up the data later, it also means the 2 systems no longer match when doing data validation. Make notes for testing.

• Update on Alma slowness issue:

Questions from slack

ICs to add any issues from slack that require further discussion.

Check-in / Logistics / Any issues with testing?

Do you have anything to discuss at the meeting?

1. Report any major changes in availability / circumstances

2. Anything to report on the test load?

TBD

(Carlo)

Update your status in advance

Q&A (recurring)

Do you have a question to discuss at the meeting?

• 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

Other / Homework

0

Tom

Assigned 5/13:

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

• Ask ExL what they advise for go-live testing for performance, particularly Primo. (Lynne)

• ICs to invite your EUOS member to your local imp team meeting to keep them informed.

Questions for Ex Libris PM (recurring)

Post questions in Basecamp as they come up. It’s open 24/7!

Reminder: Post cutover questions on Basecamp in the UCS Cutover Planning To Do list.

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

Parking lot

0

• UCD Escalation (3/17)

• (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.