2021-10-14 Meeting notes

IC meetings - thru the end of the year

Discuss IC needs and possibly how to scale back on meetings through the end of the year

15

Tom, Carlo

• Meet every other week?

• PPC style: discuss via slack if a meeting is needed and decide on an ad-hoc basis whether to meet?

  • Good to have the time held if we need it.

  • Slackbot reminder on Tuesday to prompt whether a meeting is needed and Steering confirms yes or no.

Keep the IC meeting invite in the calendar as a placeholder.

ICs to do a Slackbot reminder on Tuesday to prompt whether a meeting is needed; ICs weigh in with any issues that need a meeting; Steering confirms yes or no to the meeting.

Q&A (recurring) - urgent questions

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

1. Gem - Browzine

2. Gem - Duplicate identifiers

3. Lakshmi - Primo Search Results - problematic augmented data

4. Lakshmi: Issues with link-in-record records

https://uci.primo.exlibrisgroup.com/discovery/fulldisplay?context=PC&vid=01CDL_IRV_INST:UCI&search_scope=DN_and_CI&tab=Everything&docid=cdi_chinalaw_primary_1090525010

TBD

1. Standardize on option 2 (Third Iron’s recommendation) or do not standardize UC-wide?

   1. Davis was set up on option 1 so not sure how difficult a switch would be.

   2. UCSF is getting recommended to do option 1.

   3. Pros: Easier to track if everyone is doing the same thing.

   4. Cons: Possibly harder to troubleshoot problems.

2. Duplicate identifiers: most campuses had 10 to 100’s and a few campuses had 1000’s. Gem will send the duplicates for the campuses to review.

3. Problematic augmented data: don’t want to see items at a higher level than a specific search term. Don’t want to see “dancing” if the search is “hip hop”. ExL is augmenting records with subject headings in the 650 field. Lakshmi will do a summary for Caitlin to take to PPC.

4. Issues with link-in-record records: Was previously working at UCI, but no longer working. Is anyone else seeing this problem? ExL has asked UCI to wait for 3 days. UCM - seems familiar and Tom recalls ExL did something for them to fix it. Advise from PM: wait to see if this fixes it and respond on the case. Keep PMs posted if you don’t get a response.

5. Ramon reported that Access services between UCR and UCLA are getting bounceback notices with AFN users. UCLA is blocking ExL notices through their firewall. Bounces back to UCR and says “cannot be delivered”. Tom reported UCM had this issue immediately after go live. They had to whitelist to avoid things being considered spam. Tom specified at the host level. UCM was getting them internally from their own IZ. Caitlin reported that Vince mentioned this at the ILLOps meeting today too. Spam (or false spam in this case!) seems to be a perennial issue with ILL.

   1. This could be happening more broadly across campuses. Any value in having a list of the EXL host names to be whitelisted by all campuses? Tom said the IP addresses (or domain) would be helpful to have. Send Policy Framework record (SPF) is what Tom had to modify. No interest in pursuing this further beyond UCR and UCLA at this point.

   2. This issue was discussed in ILL Ops today so campuses are aware of the issue.

6. Alison reported a mismatch in an integration profile; Need to ensure the NZ is matching IZ for Z39.50 name and password. Fulfillment FG reps are working on this. FYI to ICs.

Gem will draft a Browzine decision page. Do not standardize at this time.

Timeline review / PM update

• Project Meetings (on basecamp and confluence)

Support during Implementation:

• Document Alma/Primo slowness in Salesforce, see instructions

• Alma/Primo known issues page on Confluence

• For escalations:

  • Essential to include case numbers - make sure that ICs provide those to PMs when asking for escalations. PMs need to ensure IC has pinged the consultant asking for a status update before escalating.

  • Escalations can go into 2 categories: it’s urgent, or there’s a lack of communication.

• SalesForce case OR Basecamp post? Please share this with your local implementation teams:

  • If it’s a general question, post on BC

  • If it’s problem, open a SF case

    • Also no need to double dip - if you have a SF case first, that’s all ExL needs (no need to additionally post on BC)

0

Lena

Ex Libris meetings:

• Next Monday, 10/18 Marci Deignan, Ex Libris project manager will lead a summary of the third and final version of the Switch to Support Readiness forms coordinated by the Implementation Coordinators. We will not have office hours on Thursday 10/21 as the Ex Libris Implementation consultants will be preparing for the switch to support. 

• Our final meeting on Monday 10/25 will be the Switch to Support meeting led by Callie Mendoza, Ex Libris North American Support Manager. Agenda:

  • Contacting Ex Libris Support

  • Knowledge Resources

  • Submitting Cases

  • Sharing Feedback with Support

  • New Customer Tips

  • PowerPoint available on the EXL KnowledgeCenter

Monthly call with ExL:

• Overview of the monthly call process scheduled for 10/20 with Alon Botvinik, ExL Dir of Support: SSM, PMs, IC co-chairs, DOC steering member.

• Nov/Dec: SSM and IC co-chair(s) as available will join the monthly call with ExL Support.

• Jan 2022 and beyond: SILS Operations Team will decide who attends in addition to SSM.

Key deadlines:

• Switch to Support Readiness form

  Objective: identify issues that need to be resolved and identify trends in problematic areas.

  • Marci will review results in the Monday October 18th weekly meeting

• Now: Register for the Ex Libris Knowledge Accelerator Program (KAP) series (Nov 3-Dec 15)

  • The EXL Training team does not anticipate anyone else joining the cycle (based on Switch to Support schedules and time zones). Do note though that your KAP cycle will include the same sessions and content EXL delivers to all KAP attendees.

  • Details regarding the Knowledge Accelerator Program (KAP): Knowledge Acceleration Program  

  • Registration page: Sign in  

Parking lot

TOTAL

50/50

Review decisions and actions.