add ability to impose blocks on deleting and merging bibs

[Galen Charlton]

There are certain workflows in a shared database where it may be useful to be able to mark specific bibliographic records as ineligible for deletion or merging.

A particular use case: when adding a library to a consortium, where bibs may be loaded first, then items and hold requests that reference those bibs. However, if a consortium has an delete-empty-bibs-on-sight policy, deleting those bibs would cause problems with the migration.

If it were possible to mark individual bibs as being ineligible for deletion (and by extension, being the source of a merge), that outcome could be avoided.

There is perhaps a bigger per-record permissions project here.

Evergreen main

[Rogan Hamby (rogan-hamby)]

I have a patch for this at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=f099e171181bd96df0a850cc61228c7f148a4d00

copy of my commit message:

This adds a new True/False column to the bibliographic record table intended for data projects, therefore there is no UI included for it. The value is called 'protected'. By default this is false. If set to true and a staff member attempts to delete a record it will fail and return a message that the record is protected. The function to merge records will also not allow the record to be the source of a bibliographic merger though it can still be the target of one.

[Llewellyn Marshall (lbmarshallv)]

Would it make sense to put this into the "Other Actions" or "Mark For" drop downs on the edit record page?

[Beth Willis (willis-a)]

+1 for the "Mark for" menu.

[Rogan Hamby (rogan-hamby)]

Displaying it is good but I'm not a proponent of making it possible for catalogers to edit the value as the purpose is to make it for catalogers to not be able to alter it as back ground data projects are being done.