Page Comparison

Choose a new Vice Chair for 2021/2022

List of continuing issues for the next committee

Review CZ updates Button in Alma

• 

• Alma Collection with portfolios>Click on the three dot menu (…)>Edit Service>upper right hand corner

SDSU ERM troubleshooting guide (in progress)

https://libguides.sdsu.edu/ermtroubleshooting

Update on Top 3 ERM Issues

• 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.When the cdi_consortia_inheritance parameter is set to Y, the member institution will inherit network zone (NZ) activations for the following: 

    1. Full text activations for selective/aggregator collections with portfolios

    Notes:

    • Selective settings (We subscribe to only some titles in this collection) for the active collections behave as defined by the network zone (either on institution level; on group level if a group setting exists for the member institution)

    • Suppress settings (Do not show as full text even if active in Alma) behave as defined in NZ (either on the institution or group setting if a group setting exists for the member institution)

  • Full text activations for 'database' type of collections

    Note: The CDI group settings defined in the network zone are taken into account, and Suppress settings (Do not show as full text even if active in Alma) behave as defined in network zone (either on the institution or group setting)

    1. CDI search activations

    Note: The CDI group settings defined in the network are taken into account. 

    1. When the cdi_consortia_inheritance parameter is set to N, the member institution will inherit network zone (NZ) activations for the following:

    2. Full text activations for selective/aggregator collections with portfolios

    Notes:

    • Selective settings (We subscribe to only some titles in this collection) for the active collections behave as defined by the network zone (either on institution level; on group level if a group setting exists for the member institution)

    • Suppress settings (Do not show as full text even if active in Alma) behave as defined in NZ (either on the institution or group setting if a group setting exists for the member institution)

    • They will not inherit:

    • Full text activations for 'database' type of collecti

  • If you want Network coordination, link to the collection, don't activate it locally.

• #2 Metatdata errors CDI and CZ -want to be able to fix metadata errors ourselves

  • Fixing Alma Community Zone Records
    Single record Alma metadata edits are possible in the CZ Community Zone through the "contribution process" https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Electronic_Resource_Management/030_Working_with_Local_Electronic_Resources/060Community_Zone_Contribution_Guidelines
    no local fields allowed

    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

Feedback for Brandon to take to EL on our meeting about the top 3 issues

• Thanks for meeting with us and responding to our top issues. We appreciate the time and energy

• During our conversation, we discussed the following issues

  • First issue and what we took from our conversation

  • Second issue and what we took from our conversation

  • Third issue and what we took from our conversation

• We understand that you are working on these issues and will be watching your progress.

• We have had a difficult time/journey with CDI to date and want to work with you to help address our (many) areas of dissatisfaction with the product. We have been advised in the past that our issues with CDI might be addressed by training. We have faithfully attended all sessions offered by Ex Libris and put what we have learned into practice. We would like to move on to ways that we can help you to help us by discussing areas of CDI that warrant further development, such as:

  • Hit them with what you’d like CDI to do that it doesn’t, or what it does now but poorly

• We look forward to working with you on these improvements and are ready to discuss best approaches with you whenever you are ready.

 What I need help with is:

• issues and takeaways – probably condensed from Kate’s notes.

• Are we happy with their responses?

• The hit ‘em part. What else needs to be changed in CDI to make us happier with CDI?