Copy Alert Matrix: Need New Permissions Specifically for Temporary Alerts

Bug #1806716 reported by John Amundson
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

With the addition of the Copy Alert/Suppression Matrix in 3.1, bug #1676608, there is a way to add temporary and persistent copy alerts, (aka item alerts), to items.

However, there does not appear to be specific permissions for each type.

The current set of permissions I was able to find include
CREATE_COPY_ALERT
UPDATE_COPY_ALERT
DELETE_COPY_ALERT

These permissions allow for the management of both temporary and persistent alerts. One of the draws of the new alerts was for non-owning libraries to add temporary alert messages. Currently there does not seem to be a way to do this without granting permissions consortium wide for all copy alerts, which we do not want to do.

I am filing this as a bug because the tech specs for the project, http://yeti.esilibrary.com/dev/public/techspecs/alert-matrix.html, state that "there will, at a minimum, be distinct permissions for... the ability to add, update, and ack/delete temporary alerts". This was also discussed in this MassLNC node, http://masslnc.org/node/2764, which provides a couple use cases.

Tags: permissions
tags: added: permissions
removed: webstaffclient
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.