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

• CDI meeting with ExL: UCD is already using CDI and hasn’t received any customer support questions from patrons which is good news. Alison noted the CDL SFX fix was made a while back by ExL and should be working for Primo VE campuses who want to test CDI.

Progress on integrations work

Report on progress on 3rd party integrations plans.

Do you have any questions or concerns to discuss at the meeting?

0

Update status in advance

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 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: Nothing

• ILSDC:

• PPC:

• Coordinators:

• SILS Chairs: Agenda is to review the Cutover plan and ask what questions chairs have.

98

Go-Live coordination

July 27 at time TBD

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

1. Understand the considerations in deciding your publicized go-live time (Carlo leads)

2. Decide whether we want to agree on one time for all or each campus decides and publicizes on their own.

From 5/13: Campuses will check with their teams on whether a noon go-live time works and report back on May 20.

See 5/19 SILS Chairs notes for discussion on go-live time (agenda item 5)

30

Carlo, Tom

• What are the considerations?

  • Assumption is AFN would not be available for any campus that hasn’t gone live. Some campuses will not be immediately doing ILL so won’t be enabling AFN on day one.

  • Next step is to get clarity on AFN: would any fulfillment requests wither on the vine if a campus is not yet “live” or does the request move to the next campus for fulfillment? Will AFN be turned on and working even if the campus is not yet live (i.e., before a campus has asked ExL to run the go-live job)? Carlo will ask on BC.

  • A go live time is for the messaging; to set patron expectations.

  • New-to-Almas must provide fulfillment data which takes some time.

• UCLA would prefer an earlier time than noon.

• UCI would prefer an earlier time than noon. Would like to wait for the ExL meeting (June 2 with existing Almas) before deciding.

Revisit this decision next week after we get answers from ExL about AFN. Carlo will post on BC.

•  Carlo Medina (Unlicensed) will post on BC: would any fulfillment requests wither on the vine if a campus is not yet “live” or does the request move to the next campus for fulfillment? Will AFN be turned on and working even if the campus is not yet live (i.e., before a campus has asked ExL to run the go-live job)?

Timeline review / PM update

• Cutover to do list

• 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

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.

Any questions on the timeline?

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?

  • UCB is asking each FG to assess how much testing they need to do, so they can plan to be done by Monday for signoff.

  • Talk to your group and see what you think is reasonable.

  • Does signing off on data acceptance clear ExL of responsibility? What does it mean to signoff? (Lena will ask)

  • Also involves lining up DNS changes, etc.

  • What is the mechanism to immediately report issues? SalesForce cutover case. If it’s something you think might affect others, slack the ICs.

  • What time works? noon and aim for 10am.

• Coordinate this as part of our testing? No consensus on this. 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?

  • Comments from ICs

    • ExL noted Primo will get faster as its used.

    • Carlo has noted he gets very diverse results on the same searches.

  • Ask ExL what they advise for testing. (Lynne will ask)

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

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

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

• From Marci: The Go Live Readiness checklist is a version of what we sometimes refer to as generally as the Health Checklist. We’ll actually use the form formally two times during the full implementation portion of the project: once as you a readying for Go Live (so around the start of Cutover) and then a second time prior to the official Switch to Support. I have suggested to past projects for them to also use the form earlier on in the project themselves to track progress on what they have learned and completed implementing, and what areas may still need additional review. This helps both sides tremendously as we can work on focusing on earlier determined problematic areas. It’s also easier for your project team when it’s time to formally complete the checklist as it’s been already been “in progress” and could be kept up to date.  Questions about Go Live Readiness Checklist and Certifications.

30

Carlo, Tom

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

• 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

•  Gem Stone-Logan to ask on basecamp if NZ has to go live first? Are there other dependencies such as the AFN?
•  ICs to invite your EUOS member to your local imp team meeting to keep them informed.
•  Campuses will check with their teams on whether a noon go-live time works.
•  Lynne E. Grigsby to ask ExL what they advise for go-live testing for performance, particularly Primo. (Lynne)
•  Lena Zentall (Unlicensed) to post on Basecamp: Does signing off on data acceptance clear ExL of responsibility? What does it mean to signoff?

Questions from slack

Other / Homework

0

Tom

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

• Question: Any objections to using the Alma account allocation for API purposes? Do Alma campuses have a good way to monitor it? There’s a report. Use the Alma account allocation to keep things simple.

• Question: Do we need best practices/guidelines for APIs? Is this something that can wait until post-go-live? Wait. No one is hitting their limit now.

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

• 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. Check on Tuesday to make sure things look good.

• UCD Escalation (3/17) is resolved. Working through some issues.

• Update on Alma/Primo slowness issue: Ex Libris has agreed to lead a meeting about how they plan to solve the slowness issues in Alma/Primo VE. They want to introduce what they're calling a "warmup tool." The meeting will be led by ExL senior staff from Israel (thus the early start time): Ahuva Mazuz, VP of Development and Omri Gerson, Corp VP Platform & Tech. There will be time for Q&A. Attendance is optional.

  • Tuesday June 8 at 8am

  • THE MEETING WILL BE RECORDED.

  • A few WG members will also attend.

Q&A (recurring)

Do you have a question to discuss at the meeting? Add it below with your name.

1. (Greg) what does a Technical Freeze REALLY mean for some Circulation activities?  For reference: https://3.basecamp.com/3765443/buckets/15553579/messages/3791614832#__recording_3792051687

2. (Lynne) Suppressing items – how do Alma campuses do this level of suppression?

3. (Lynne/Lena) Consortium response to Primo response time & named user questions

4. (Susan/Lisa S): for electronic resources which make use of outbound linking we will need the base URL and possibly an image file (in some cases the URL for the image location rather than the image file itself). AEFG has an MVP item for the CDL resources needing updating as this requires extensive coordination between CDL and campuses and can vary across content providers. AEFG is following up with the Discovery FG for the “get it at UC” logo (which replaces UC-eLinks) to ensure that the image files that are created will meet most content providers' image file type and size requirements. Please have a look at (Initial Post-Go-Live) Outbound Linking from Vendor Platforms (AEFG MVP 006).

5. (Gillian) from my Resource Sharing rep: it sounds like there are quite a few cases that will need to be opened for the whole consortia. Apparently there is an account where someone (at CDL I assume) can do that - do you know if we can see those cases?

6. (Alison): FYI - emailed everyone the ‘sfx freeze’ info, please spread to your team as appropriate/needed.

TBD

Team

• Concern over the number of serious defects in digitization workflows (no ability to see comments, etc.). Not feeling confident about this critical functionality.

• Jeremy shared a code repository for APIs that CSU is using to share: https://github.com/CSU-ULMS This is an excellent model of sharing APIs and custom coding across a consortium. Thank you, again, CSUs!

CDL should manage the Get it at UC button and make it publicly available for vendors. Vendors prefer a link to an image file, not the image file itself.

For systemwide cases, Alison/Gem will open SF cases with a cc to the ICs SILS-IC-L@ucop.edu so ICs have visibility into these cases.

•  Alison Ray (CDL)Caitlin Nelson and Gem Stone-Logan will find a home for the new “Get it at UC” button (image file). (CDL should manage the “Get it at UC” button and make it publicly available for vendors. Vendors prefer a link to an image file, not the image file itself. )

Parking lot

0

TOTAL

90/90

Review decisions and actions.