expand context org for SET_CIRC_LOST permission
Bug #1259636 reported by
Jason Etheridge
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Consider this scenario:
In a stock-like org hierarchy, staff in a consortium have the SET_CIRC_LOST permission granted at a depth of Branch.
Patron A checkouts out Item A (belonging to Library A) at Library A.
Sometime later, the circulation gets renewed at Library B.
Sometime later, Patron A loses Item A.
Library A does not have permission to mark the circulation as Lost, even though it is their item, based on the transaction library being Library B.
We could have the permission check consider multiple libraries against the depth:
the item circ lib, the item owning lib, and the circ transaction lib
Currently we're just using the latter. We may want to use all three.
To post a comment you must log in.
Adding a link to related bug 1632797.