wish for a permission on Hard Due Dates Changes
Bug #1289651 reported by
Tina Ji
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
The permission should control access to Admin > Server Admin > Hard Due Date Changes, so individual libraries may maintain their own hard due dates.
Tina Ji
Sitka
Changed in evergreen: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
tags: | added: permissions |
To post a comment you must log in.
The permissions currently required to administer hard due dates are:
CREATE_ CIRC_DURATION CIRC_DURATION CIRC_DURATION
UPDATE_
DELETE_
These permissions are required at the Consortium level and control administering circulation duration rules.
In a consortium environment, we can't grant these permissions to users at the level required to allow them to simply change the hard due date value for their own institution because those permissions would also allow them to control duration rules for the entire consortium.
Creating some new permissions:
CREATE_ HARD_DUE_ DATE_VALUES HARD_DUE_ DATE_VALUES HARD_DUE_ DATE_VALUES
UPDATE_
DELETE_
on the config. hard_due_ date_values table would allow staff members at individual libraries to regularly update their own hard date values.
Initial setup of hard due dates could be left to consortium administrators, but stop dates could be maintained by staff at the library.