2021-04-09 ULMS Steering Committee Meeting Agenda

1:00-1:05

Welcome

@John Wenzler

1:05-1:30

COLD Report

@John Wenzler

• Structure of the Steering Committee - Starting with the 21/22 term, Brandon will serve as the Chair of the ULMS Steering Committee; Adriana Popescu will serve as COLD liaison

• CSU/UC Reciprocal Borrowing Proposal - no input from COLD yet; John to follow up

• SUNY/CSU Consortial Borrowing Pilot - survey sent to COLD deans; early interest from a few libraries has been expressed and Chris Lee presented the proposal to I-SPIE; the pilot will move forward, but need to finalize the number of participating libraries

• Ex Libris Rapido Offer - survey sent to resource sharing staff to gather data around how adoption would affect workload; we will know more next week, but it is likely that the workload will not be an issue, as much as the need to change workflows.

1:30-1:45

CSU Libraries Data Warehouse or Data Lake

@Laura Krier

For reference see:

Open

John will discuss next steps with Carlos, as it is not clear what information/data COLD wants or needs. Depending on what is needed, developing this data warehouse may go beyond the scope of the ULMS Steering Committee.

1:45-2:00

CSU+ Due Dates

Fall Prep questions for ULMS

@Natalya Magazino (Unlicensed)

Resource Sharing and Fulfilment groups have been tasked to bring forward recommendations to COLD and the CSU libraries with regards to quarantine periods and if or not to extend CSU+ due dates. Broader recommendations on any other planning aspect for reopening libraries in the fall would be helpful to COLD and to all libraries.

2:00-2:30

Reports

All

Chancellor’s Office

• Conversations with ExL on contract renewal to start soon

Resource Sharing

• Working on finalizing issue descriptions for meeting with ExLibris

• Met with UC courier team and found out the team has regularly scheduled meetings with Unity to talk service issues. Chris has requested monthly meetings with Unity that would include RS Manager, RSFC chair and vice-chair, and RSFC member designated to manage Unity problem reporting form submissions.

• Continuing to look into feasibility of using the resource sharing request API to accommodate Cal State Walk-in users.

• Looking at resource sharing related enhancements. Will recommend 2-3 to our community of practice by end of week.

• We have begun testing CSU+ requesting in Primo. Will continue to test and Chris will report issues to ExLibris.

Resource Management

• VE Configuration

  • Members of the RM group who are part of the Norm Rules Joint Task Force are monitoring or involved in building/testing Drools for configuring Primo VE

• ELUNA Enhancements Vote

  • Resource Management folk have discussed ELUNA Enhancements in the current ballot and will point out (via a Technical Services message) ballot items of interest, some which the committee endorses for the CSU’s vote and for the Libraries that are individual ELUNA members.

• ExL Customer Satisfaction Survey

  • Discussion and preparation of use-case information for the issues mentioned in Resource Management.

Fulfillment

• Continued to work on documenting our Alma issues for ExLibris.

• Hosted the Spring Fulfillment Open Forum with presentations on Digitization and Walk-in Users. The recording and notes are posted to the Fulfillment confluence site: 2021-03-25 Fulfillment Open Forum

• Reviewed the Alma enhancements. Our vote recommendation will be emailed to the Access Listserv.

ERM

· Source record for CDI records indicates which collection is responsible for why that record is showing up, but it may not be the actual source of the metadata.

· The CDI source collection name may not map perfectly to the alma collection name because it is a Summon 360 collection name (CDI is the combination of Alma and Summon central indexes, but the source can only pull from one source, and that is Summon 360).

o You can check the collection title crosswalk from the CDI Collection List, which can be found here: https://knowledge.exlibrisgroup.com/Primo/Content_Corner/Central_Discovery_Index/Documentation_and_Training/Documentation_and_Training_(English)/Alma_-_CDI_Single_Activation/CDI_Collection_Lists_for_Alma_Customers#CDI_Collection_List

1. Gale Linking update

From Jessica on Slack:
“Ex Libris Development team has completed an initial assessment of this issue. After taking into account a number of factors including impact, scope, technical complexity, functional prerequisites, and existing priorities, Development team has set a preliminary target date for resolving this issue no later than May 2021.
Please note that this is a tentative estimate only, and is subject to change due to ongoing review and assessment of Operations priorities. We will notify you if there are any further changes to the target date.”

1. ERM Top 3 Issues submitted to Ex Libris as SalesForce #'s: 00941104, 00941106, 00941107

Additionally, CDI records originating from an inactive CDI collection diminish user experience. Libraries would like the option to have those records removed.

a. We want a way to resolve metadata errors more easily than submitting a Salesforce case, ideally by ourselves.
We want to even out resolution times between vendors (for example, resolving Ebsco metadata errors takes far longer than other vendors).

b. We need tools for identifying the source of the metadata (rather than just the source collection in CDI, which we have been told by Ex Libris may not be the source of the metadata). These tools should be easy to use and have documentation.

c. We need training to read the CTO record to understand it and to be able to identify what the metadata errors may be.

a. We want CDI updates and indexing to be faster, ideally closer to 48 hours than even 72.

Other examples: In Academic Core Plus, Ex Libris updated every portfolio with the wrong linking so we had to correct the linking for all of our subscribed portfolios. CSU Fullerton reported that 450 records were removed by Ex Libris from their Alexander Street Press American History in Video collection during a recent CZ update. Another CZ update broke the Safari e-book parser, which took two weeks for Ex Libris Support to address and meant a loss of access to one of our largest e-book packages for a significant amount of time. There have recently been higher than normal reports of broken links in the OA e-collections, necessitating manual intervention and individual reporting to Ex Libris Support.

Additionally, frequently ebook records loaded from the CZ lack basic access points such as subject headings or anything other than a title and author. To make the records usable for patrons, campuses would have to manually improve the records, or choose not to use the CZ records and import the data from somewhere else, which is more work than using a CZ collection. If there is going to be a collection in the CZ, the metadata should conform to a basic record standard that includes enough information for patrons to actually discover the item, otherwise, there is no point in having the record in our system.

a. We want CZ updates to be accurate. When a CZ collection update has errors, Ex Libris should take the responsibility to fix the collection in such a way that their entire user base isn't tasked with manually updating collections to address the error, or deleting their collection (often with local information), reimporting the entire CZ Collection, and manually adjusting portfolios to reflect local changes (again).

b. We want ebook CZ collections to have a title, author, original publication date, and subject headings at the bare minimum, as these are needed for basic discovery. We would prefer to have records comply with the full-level OCLC encoding standard. https://www.oclc.org/bibformats/en/onlinecataloging.html#levels

· How PrimoVE merges multiple catalog records

PCI to CDI - A comparison of FRBR grouping and Match and Merge
https://knowledge.exlibrisgroup.com/Primo/Community_Knowledge/PCI_to_CDI_-_A_comparison_of_FRBR_grouping_and_Match_and_Merge

· Troubleshooting CDI issues

Central Discovery Index (CDI) - Troubleshooting Tips and Tricks
https://knowledge.exlibrisgroup.com/Primo/Community_Knowledge/Central_Discovery_Index_(CDI)_-_Troubleshooting_Tips_and_Tricks

o How to view the CTO record:
only works in PrimoVE
append a record URL with “&displayCTO=true” sans quotation marks at the end of the URL

o Link in record example (display CTO link shows under the title)
Memory and Identity - Rivka Galchen and David Linden
https://csu-sdsu.primo.exlibrisgroup.com/discovery/fulldisplay?docid=alma991071953449202901&context=L&vid=01CALS_SDL:01CALS_SDL&lang=en&search_scope=MyInst_and_CI&adaptor=Local Search Engine&tab=Everything&query=any,contains,Memory and Identity - Rivka Galchen and David Linden&offset=0&displayCTO=true

o Link Resolver example:
Extraterrestrials in the Stacks
https://csu-sdsu.primo.exlibrisgroup.com/discovery/fulldisplay?docid=cdi_gale_infotracacademiconefile_A653528641&context=PC&vid=01CALS_SDL:01CALS_SDL&lang=en&search_scope=MyInst_and_CI&adaptor=Primo Central&tab=Everything&query=any,contains,alien abduction&offset=0&displayCTO=true

Discovery

April is the designated month for data collection during the Primo VE evaluation. All campuses should aim to have all data submitted by Friday April 30th for it to be considered. The final decision as to whether the CSU system moves to VE or stays with Primo Back Office will be made by the DFC in late May. If the decision is to Go VE, a tentative go-live date for VE to be in production is Monday June 21st. As a reminder, the timeline for the evaluation can be seen at Primo VE Evaluation Schedule

Detailed discussion on the testing plan can be found in the recorded 5th Go VE Forum: https://csulb.zoom.us/rec/share/3AXC7p6TW8_vz9U9N-kDja85c9YuebGPWsh4JJUlSNR5EpeCGsXdvO7vvPnBMcv6.nzBFWsD9eWAJRmbl. Links to the testing forms have been provided to the campus Primo/Primo VE admins at each library. Most testing and evaluation data relies on their expertise and input. However, there are two testing areas where multiple responses per library are welcomed, you may find them immediately below:

PRIMO VE Front End Usability Survey (keep in mind that your library may not have VE fully configured, check with your campus Primo admin if you have any questions)

https://docs.google.com/forms/d/e/1FAIpQLSe1GWGix_1IR7aMuY0JMI5zTcs8ImGhZ7PTJIvbFMBzrYrlUQ/viewform?usp=sf_link

Primo vs Primo VE Results and Relevancy (keep in mind that your library may not have VE fully configured, check with your campus Primo admin if you have any questions)

https://docs.google.com/forms/d/e/1FAIpQLSf0IbbFQnrstv5Has5Iq1iGUWWLV-TTAqTdKfrNW9McJX-RsA/viewform?usp=sf_link

Unrelated to VE, Ex Libris has suppressed the display of certain racial slurs. See their ‘Policy Regarding Subject Headings in CDI’ for details: https://knowledge.exlibrisgroup.com/Primo/Content_Corner/Central_Discovery_Index/Documentation_and_Training/Documentation_and_Training_(English)/CDI_-_The_Central_Discovery_Index/Ex_Libris_DEI_(Diversity%2C_Equity%2C_and_Inclusion)_Policy_Regarding_Subject_Headings_in_CDI_(Central_Discovery_Index)

The title of the policy is a misnomer because as best we can tell the suppressed terms were introduced via author-supplied keywords; they are not valid LCSH data. How and why such keywords get added to the records displayed to end users as “Subject Headings” is beyond the scope of this message but Chair Gardner recommends reading Masked by trust : bias in library discovery http://www.worldcat.org/oclc/1200667767 if anyone is interested in the details.

This information is of particular importance for librarians working with the sociology, history, and linguistics fields because cursory examination of results including the now-suppressed terms comes predominantly from those three fields.

Assessment & Analytics

We are working on putting together a report from the recent SUSHI/Usage Data survey and coming up with a plan for training and documentation for libraries on using SUSHI and Usage Data in Analytics.

Acquisitions

Discussing alternative communication methods with committee to foster ongoing discussions within acquisitions community