...
Time | Item | Presenter | Notes | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1:00-1:05 | Welcome | ||||||||||||||
1:05-1:30 | COLD Report |
| |||||||||||||
1:30-1:45 | CSU Libraries Data Warehouse or Data Lake | For reference see:
| |||||||||||||
1:45-2:00 | CSU+ Due Dates Fall Prep questions for ULMS | ||||||||||||||
2:00-2:30 | Reports | All | Chancellor’s OfficeResource Sharing
Resource Management
Fulfillment
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
From Jessica on Slack:
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. 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 · Troubleshooting CDI issues Central Discovery Index (CDI) - Troubleshooting Tips and Tricks o How to view the CTO record: o Link in record example (display CTO link shows under the title) o Link Resolver example: DiscoveryAssessment & AnalyticsWe 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 |
Action items
...