Prevent User Deletion of Paging Lists
We frequently have the unfortunate situation where staff accidentally delete their paging list from the list of Notices. Ideally, we'd prefer that frontline staff be able to prepare, print, & fulfill their paging lists but not be able to delete them.
Separating authorizations to create/edit/delete these lists from the preparation & printing would save support staff a great deal of time spent recreating these lists & remove some of the potential for frustration & confusion among frontline staff.
Shawn P. Farrell
shared this idea
-
Carrie Zamorano
commented
We need the ability to print our own paging lists instead of relying on our consortium to do this at set times. Separating authorizations would prevent errors from occurring that could negatively impact other libraries.
-
Martha Hansen
commented
Yes! I was just coming to make my own request individual authorization for paging lists. We are part of a large consortium and because of the danger of individual libraries accidentally messing up other libraries paging lists we can't run our own paging lists. The consortium staff runs them twice a day for all the libraries and emails them out. Because the paging lists can't be isolated to a single library we understand that they don't want to share the privilege for fear of messing up the notices. If libraries had the option to have a separate limited authorization to run their paging lists it would save us a lot of wasted time and effort because we often can't pull the items in the timeline allowed between the two system-run paging lists.
-
Alison Pruntel
commented
Yes, we've had some staff accidentally delete a notice job.
-
Elizabeth Wright
commented
Yes, please. Obviously it would be ideal to limit the paging lists that are available to each login, but this would certainly help. We have over 100 paging lists and new staff are very nervous accessing their lists in this table (so some might not perform this circulation workflow because they don't want to make a mistake).