Prevent deletion in Community Zone based on field or value in specific field.
Blocking deletion in Community Zone based on field or value in specific field. Possibility to be definded as a parameter for each CZ vocabulary.
Bruce Sciboz
shared this idea
As you all know, the Community Zone content is shared among all Alma customers, each with different requirements. Therefore, I’m not sure this request would be acceptable to the wider Alma community. That said, if there were a consensus on a closed list of fields that CZ bibliographic records should be restricted from deleting per MARC profile, this capability already exists and is managed by the Ex Libris Content Operations team. Unfortunately, this is not available for authorities. Do you think such a consensus could be reached?
-
Esther Ernst
commented
Blocking the "Delete record" functionality for GND-records would save precious time and work that we spend for troubleshooting, so we would really appreciate this possibility.
-
Sebastian Aigner
commented
In the GND context, it causes problems when colleagues use the "Delete Record" functionality via "Record Actions", because it changes the LDR in a way that is not compatible with how records are deleted in the GND master file. It therefore sends these records into limbo, since they are neither available in the Alma-GND-mirror, nor are they actually deleted in the master file.