...
| CZ Weekly Update Delays explained: |
|---|
The CZ is updated and those changes are then filtered down to the IZ and NZ. From Ex Libris: "Alma handles 50,000 changes at a time. If more than 50,000 changes are to be performed in the Community Zone, Alma launches an additional job to handle the rest of the changes." If there are a large number of changes, the job that “synchronizes changes from the CZ” will be broken up and run over the course of several nights. You can check on the progress of this job in the Monitor Jobs > Running tab. If you see a job, Synchronize Changes from CZ = Pending, the update has not finished. You can see the changes in the CZ but they may not have been applied locally yet. If your library has been expecting changes from a specific weekly update, wait until the update is complete to check on the changes. |
ExL Removes E-collections and portfolios, how to keep them in your instance IZ: |
|---|
When Ex Libris announces they are going to remove an e-collection, many times, they remove the e-collection from the CZ, making the e-collection and local collection in the IZ. Then they will eventually remove the e-collection from the IZ. If your library does not want this e-collection to be deleted, change the Auto-Update setting in the e-collection service from yes to no. This will keep the collection local into the IZ until the library is ready to remove it.Message from Ex Libris: “The behavior for what happens in the IZ when collections and portfolios are removed from the CZ is described in the documentation here: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/060Working_with_the_Community_Zone_Updates_Task_List When electronic collections are deleted in the CZ, the collection is deactivated and localized, but not deleted from the IZ. When portfolios are deleted in the CZ, what happens in the IZ depends upon whether the collection is set to auto-activation or non auto-activation. If a collection is set to auto-activation, then the portfolios are deleted automatically. If the collection is set to non auto-activation, then the portfolios are localized and deactivated, but not deleted. You mentioned that at this point institutions have had portfolios deleted with the updates in the CZ. Depending on how many perpetual access titles institutions had, it may be possible to restore the deleted portfolios using the Manage Deleted Repository tool. If that is not realistic due to the quantity of portfolios affected, I can look into whether it is possible to restore these portfolios in another way.” |
...