Allow Community Zone updates to push silently behind Local Overrides/Exceptions
When we discover that a portfolio or collection has a linking or coverage date problem, we report it to Ex Libris ASAP so updates can be made to the collective. While waiting for them to fix an issue at the CKB level, we put in place a local linking override so our users can access the content for which we pay. We would like to be able to retain access to resources with as few gaps in services as possible.
To go back to the CZ linking or coverage once a fix has been declared, we currently have to remove our local exceptions before the change happens. This means making the change a day or more before to ensure I don’t miss the window of opportunity – if we miss it, the Ex Libris changes are not allowed to pass to our record behind the local override until the next content update, around a week later.
Customers and Ex Libris would likely find it more manageable if CZ data could be pushed in content updates whether or not overrides were in place. The override would still be in effect, of course, but if the customer elected to delete the override parameter, end users would immediately see the current version of its CZ parameters in the discovery interface rather than an older version.
This idea relates to Support Case #00847117.
Electronic resources have global fields that are maintained by Ex libris and local overides fields that are maintained by the customer.
Any changes Ex libris makes to the electronic resources are made to the global fields and are pushed automaticly and reported in the CZ update task list, the overides still take effect until they are deleted.
if you have any local overides the CZ update task list will prompt you to remove them so the global fields will take effect.
you can read more about it https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/060Working_with_the_Community_Zone_Updates_Task_List
-
Ben Hockenberry commented
Thank you, though-- I've noted this in the case.
-
Ben Hockenberry commented
Please see my case in question -- the technician said this was not already supported.