Issue #1 - Changes to records and CDI are taking too long to show up in OneSearch
Metadata Corrections At the Ex Libris level, CDI re-indexes twice a week. When you submit a trouble ticket for a single record metadata correction, it will take 3-7 days AFTER Ex Libris notifies you that the record has been updated for the change to be reflected in Primo.
CDI rights processing (changes to CDI settings in the NZ or the IZ)
The average time to see changes reflected in OneSearch is 70 hours. If you log into the Ex Libris system status page with your salesforce login, you can subscribe to the status page for CDI and be notified when the process is taking longer than 70 hours. http://status.exlibrisgroup.com Ex Libris is working to bring the average time down to 48 hours by the end of the year.
Linking Syntax issue
Once Ex Libris fixes the collection level linking syntax (link resolver type collections) and updates the linking parser - the parser is maintained at the global level and is a part of the global alma release - so it is updated in the weekly CBK update on Sundays.
CDI Inheritance Activation Workflows
Inheriting from the Network Zone CDI - no one should have inherited from Primo Central.
CDI inheritance is all or nothing - but institutions can deviate by editing the NZ settings (as far as I can tell). *****If you don't inherit CDI settings from the NZ, but you link to the NZ collection, what happens????? Ex Libris is checking on this If you activate a full-text collection in the NZ, it's active for all members unless otherwise noted.
CDI inheritance is only for people who were inheriting from Primo Central.
You can override inheritance settings in the NZ or activate the collection in the IZ to have different settings.
Inheritance is relevant for activation for search, for subscribe to only some titles, and do not show even if active in Alma.
If an institution inherits CDI activation for a collection from the NZ, but then activates the same collection in the IZ, it will override the NZ settings. If you want Network coordination, link to the collection, don't activate it locally.
Issue #2 Metadata errors CDI and CZ -want to be able to fix metadata errors ourselves
Once it is changed in the CZ, it will update in Alma when the CZ pipe next updates (dependant on local scheduling) and in local Primo when it next updates (which should be twice a day?). Expect the update within a day.
CDI Metadata updates
no individual ability to update CDI metadata records
Ex Libris is investigating methods for title checks and linking improvements which may assit in resolving the above - getting member editing rights is more complicated legally due to vendor data licensing agreements.
Issue 3 - Community Zone Updates and records are causing extra work for ERM and Cataloging Staff
It takes 6-10 days to make a correction for e-collections and have it be released in the next weekly update. So in our example, they broke Safari in one weekly release and the fix would be released in 6-10 days. I believe it was a little longer than 10 days for Safari but normally if something breaks, that is how long it takes to fix it.
No traction on the issue that they break things and we have to do extra work to deal with the fallout
Discovery
Assessment & Analytics
Acquisitions
we discussed our upcoming meeting with Ex Libris on our Top Three Issues from the Satisfaction Survey
We also had a round robin discussion about how different libraries handle standing orders in ALMA, and how to manage those encumbrances.
