Transferring holds functions need more granular permissions
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
The UPDATE_HOLD permission controls the ability to edit individual holds. The same permission also allows a staff user to perform the following functions:
- Actions for this Record --> Transfer all title holds
- Actions for Selected Holds --> Transfer to Marked Title
Use case:
Circulation staff frequently assist patrons with holds so they need to be able to edit individual holds on behalf of patrons. Their duties do not require them to transfer holds in batch.
Technical services staff, when entering and deleting items, need to be able to select individual holds and transfer them to different titles whenever appropriate.
Transferring all title level holds to another record, outside of merging two records, is rare. Permission for this fuction, if granted at all, should be reserved only for administrators.
We have had situations where all title level holds have been transferred to a different title in error because the user intended to click the "Actions for selected holds", but instead clicked the "Actions for this record" button by mistake.
Related bug:
https:/
Related IRC discussion:
| Kathy Lussier (klussier) wrote | #1 |
| Kathy Lussier (klussier) wrote | #2 |
| tags: | added: pullrequest |
| Changed in evergreen: | |
| milestone: | none → 2.next |
| importance: | Undecided → Wishlist |
| status: | New → Incomplete |
| status: | Incomplete → Triaged |
| Kathy Lussier (klussier) wrote | #3 |
| Changed in evergreen: | |
| milestone: | 2.next → none |
| tags: | removed: pullrequest |
| Changed in evergreen: | |
| assignee: | nobody → Victoria Lewis (sykeslewis) |
| assignee: | Victoria Lewis (sykeslewis) → nobody |
| tags: | added: permissions |
| tags: | added: holds |
| tags: |
added: circ-holds removed: holds |
I really don't think this option is necessary since there is an alternate way to transfer a batch of holds in the client. I would advocate for removing that option altogether. I've posted a message to the list to see if there is support for removing it.
http://