2022-03-04 Meeting notes

Sharing and Updates

Share any Discovery related information from other SILS groups

5

All

Review Past Actions

5

Did everyone share their campus issue tracking pages (if available)? Local Issue Tracking Pages Repository

Did everyone share their local repositories (if available)? Primo Package Code Repositories

Issue Tracking:

We need a way to aggregate and track important issues that may be system-wide or even just affecting multiple campuses.

Primo Configuration:
We (UC system) may want to harmonize our Primo packages, or create a central repository of packages/configurations that can be shared among campuses. First, we need to understand what everyone is currently doing to decide if we even want to do this.

• Gem Stone-Logan will ask Operations/Steering about how subteams should track issues. “Should everyone be doing it the same way? If so, what are our options. If not, can we use GitHub, and is there a .org account or do we make a new one?”

Update: CDI links for CDL managed Naxos collections not appearing.

Gem

02/24/2022 At a minimum, this is affecting UCSD, UCM, and UCLA, maybe more. UCI appears to have local versions (?) and it's working fine for them. Greg, at UCSD, heard these links were working until recently and we haven't made any changes at CDL. I have a ticket open with Ex Libris but haven't heard back yet.

3/4/2022 update: This appears to be working now, though I never heard back from Ex Libris.

If any aren’t working, let Gem know.

Update: Deduplication Issue

02/24/2022 requested additional info from Ex Libris in terms of what configurations changes could be made to circumvent the problem until they have a patch but haven't heard back.

• All: Do local testing using Josh’s examples (Slack), and others, to provide more data for the ExL tickets.

Josh’s example from Slack:
The local DFG at UCLA has been discussing three problems with Primo. Two of these may be related to the deduplication issue, so I'm not sure if I should just put these in the parking lot or add them to the agenda, which looks pretty full already. Some context: we have deduplication turned on and we have it configured to prefer the electronic records. At the moment, the deduplication problems appear to be inconsistent.

Problem 1: Primo is not always showing the print holdings for deduped records.Example: https://search.library.ucla.edu/permalink/01UCS_LAL/trta7g/alma9992307073606533
Primo shows you that the print version is available at 2 locations. However, it won't display the actual holdings for the print location.

Problem 2: Primo is favoring a simple microfiche record over a fuller print record.Example: https://search.library.ucla.edu/permalink/01UCS_LAL/17p22dp/alma991010687959704701
Primo is showing you the bib info for the microfiche record at UC Irvine's Law Library. The UCLA Law Library has a much fuller record for the print version. Is Primo displaying this because it considers microfiche to be electronic (which we configured Primo to prefer in deduplication)? If not, is there a hierarchy of preferences in Primo deduplication (i.e. if electronic not available, then prefer print next, not microfiche or other formats)?Problem 3: Holdings for Davis Law Library are not displaying

Example 1:  https://search.library.ucla.edu/permalink/01UCS_LAL/ja2kno/alma9956983303606533

Example 2: 
https://search.library.ucla.edu/permalink/01UCS_LAL/ja2kno/alma996711603606533

Click on "Other UC Libraries" and click on Davis. The system will display the loading animation (aka diamond parade) and never get the data. 

Exclude eBooks from CDI

Gem, Sean

Note: This is the first item in the Phase 4 Handoff.

02/24/2022 We have several tickets open with Ex Libris about bad CDI links for ebooks when our Alma records are fine. That said, I'm very nervous about how this might interact with the dedup problem. I'd like to be involved in the testing we do around this.

02/25/2022 Our campus is very interested in the Exclude eBooks from CDI feature. This was brought up locally when the feature was initially released and we wanted to follow up on this as it looked like something that would ease confusion in discovery

 Example from UCI

-Also, and this just gets confusing, those particular records will never match and merge because they're coming from institutional repositories

-Ex Libris via SalesForce case for this title said that policy is not to match and merge from IRs because IRs are supposed to have unique stuff in them

Review Work Handoff

The phase 4 handoff sheet for Discovery has been added to our shared google drive. The Operations Team recommends we review these tasks and add them to the Confluence workplan as appropriate.https://docs.google.com/spreadsheets/d/1hIO3dlD5sq26CvpAE4CZAnyzBNNHrMy0MyrKFM2urUw/edit#gid=0

Standing Item: Review Issues Spreadsheet and Parking Lot.

5

Spreadsheet is still pending.

Wrap up

Review actions and decisions

5

Parking Lot

Capture important topics for future discussion:

Discussion Parking Lot / Future Topics

Total

45