Add an option to mark record sets as "do not delete."
Polaris has long supported an option in Patron Registration where you can mark a patron record as "Do Not Delete." I'd like to see that same functionality carried over to record sets. For me, it's a fairly common task to recover accidentally deleted record sets for staff members who've somehow managed to delete an important and often used record set, despite every warning they receive.
Specifically, I'd like to see this option added at the permissions level, with separate permissions for:
- Mark a record set as "do not delete"
- Clear a record set for deletion
That way staff members can't mark each and every record set as do not delete, but neither can they clear a record set for deletion unless they have the permissions to do so.
Daniel Messer
shared this idea
-
Wes Osborn
commented
While this would certainly be an improvement and would offer clearer signaling and a better UI for staff, we accomplish something similar by limiting permissions for system level owned record sets so that they can't be deleted.
I think one consideration here is that if you could still go through and remove every record from the record set, what benefits do you get by being able to keep the record set "shell" in place?
In our case, we need the shell because we have some automation around handling bounce backs and some tooling for an automated holds service, but I suspect that other folks wouldn't have such automations in place.
Again, I would like to see this, but if you struggle with this today you might consider doing some permissions finagling to see if you could get yourself part (most) of the way there today.
-
Lynn Reynish
commented
Agreed! And better staff training won't solve this issue. Besides, my philosophy is that mistakes shouldn't cause that much pain.
-
Andrew Teeple
commented
Yes, please! I tried to get this idea implemented in the previous enhancement request knowledge base, but it didn't get past the peer review stage, where someone commented that it was unnecessary and it just required "better staff training."
We have staff members who accidentally delete record sets all the time! Accidentally! It isn't an issue of "better staff training" when it happens accidentally.
We use a significant number of shared record sets between staff members, many of which are set up to populate custom reports. Multiple staff members populate these record sets, so it is frustrating when one of these is accidentally deleted and the custom report no longer functions.
Naturally, not all record sets need to be marked as such but it would certainly be helpful to have this option at the permissions level.