wish for a permission on Hard Due Dates Changes

Bug #1289651 reported by tji@sitka.bclibraries.ca
20
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

Tags: permissions
Kathy Lussier (klussier)
Changed in evergreen:
status: New → Triaged
importance: Undecided → Wishlist
tags: added: permissions
Revision history for this message
Michele Morgan (mmorgan) wrote :

The permissions currently required to administer hard due dates are:

CREATE_CIRC_DURATION
UPDATE_CIRC_DURATION
DELETE_CIRC_DURATION

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
UPDATE_HARD_DUE_DATE_VALUES
DELETE_HARD_DUE_DATE_VALUES

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.

Changed in evergreen:
status: Triaged → Confirmed
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

still an issue in 3.11.1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.