LP#1811442 - Assign copy alert permissions.
authorChris Sharp <csharp@georgialibraries.org>
Mon, 20 May 2019 19:44:08 +0000 (15:44 -0400)
committerGalen Charlton <gmc@equinoxinitiative.org>
Tue, 1 Oct 2019 20:39:34 +0000 (16:39 -0400)
VIEW_COPY_ALERTS and ADMIN_COPY_ALERT permissions were added
recently, but not assigned in the default seed data.  This branch
assigns VIEW_COPY_ALERTS to Staff profiles at the Consortium depth
and adds ADMIN_COPY_ALERT to the Cataloging Administrator profile.

Since permissions are set so specifically per-site, this branch does
not contain an upgrade script, but does provide an update to release
notes reminding site admins to manually add them to the appropriate

Signed-off-by: Chris Sharp <csharp@georgialibraries.org>
Signed-off-by: Kyle Huckins <khuckins@catalyte.io>
Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
docs/RELEASE_NOTES_NEXT/Administration/copy-alert-perms-assigned-in-seed-data.adoc [new file with mode: 0644]

index daf37c3..e0567d2 100644 (file)
@@ -2090,6 +2090,7 @@ INSERT INTO permission.grp_perm_map (grp, perm, depth, grantable)
+                       'VIEW_COPY_ALERT',
@@ -2299,6 +2300,7 @@ INSERT INTO permission.grp_perm_map (grp, perm, depth, grantable)
                pgt.name = 'Cataloging Administrator' AND
                aout.name = 'System' AND
                perm.code IN (
+                       'ADMIN_COPY_ALERT',
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/copy-alert-perms-assigned-in-seed-data.adoc b/docs/RELEASE_NOTES_NEXT/Administration/copy-alert-perms-assigned-in-seed-data.adoc
new file mode 100644 (file)
index 0000000..13395bf
--- /dev/null
@@ -0,0 +1,15 @@
+Copy Alert Permissions Added to Seed Data
+Copy alerts were improved in recent releases of Evergreen,
+but the permissions were not assigned to any of the stock
+permission profiles in the "seed data" supplied to first time
+The VIEW_COPY_ALERT permission is now assigned to all profiles
+under the "Staff" parent profile, and ADMIN_COPY_ALERT is now
+assigned to Cataloging Administrator and should be available to
+all Administrator profiles.
+This change does NOT include an upgrade script, so site server
+administrators are responsible for updating the permissions
+profiles for their individual systems.