More granular permissions for deleting items/bibs
In Polaris, a single delete of a bib/item record will result in that record being 'marked for deletion.' It is no longer visible in the PAC, but is still visible in Polaris with a Deleted status. Deleting a record in Deleted status, or what we've termed 'double-delete,' will result in the record being fully purged from the database.
Sometimes, staff will delete a record and go back to it to verify the deletion. They see it's still visible in Polaris (missing the Deleted status) and delete it a second time. This accidental purging results in no longer being able to 'undelete' the record or pull circ statistics if needed. As a consortium with a shared database, this is problematic.
Currently, there is only one permission responsible for the ability to delete and purge records. We would like separate permissions for deleting records and purging records to help curb accidental purging.
Nicole Murphy
shared this idea
-
Celia Mulder
commented
We would also find this useful. We have our page staff delete weeded item records and they will accidentally double delete a record set of items, which causes issues for our weeding tracking and stats.
-
It would be helpful to have these permissions separated. We currently discourage library staff from deleting at all except where a record was created in error. Instead, we update items to deleted if they have been withdrawn/lost/missing for a certain amount of time.
