Comment 1 for bug 1289651

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.