So, rather than reusing ADMIN_BOOKING_RESOURCE_TYPE as a retrieve perm, working branch user/jeffdavis/lp1873048-booking-resource-view-perms adds a new VIEW_BOOKING_RESOURCE_TYPE perm, which can be scoped to the system level or whatever, as needed. A new VIEW_BOOKING_RESOURCE perm is also added for consistency.
Turns out we need a separate retrieve perm for resource types. There will be cases where resource types are owned at the system level (thus system-level view perm is required) but circ staff only have branch-level perms for managing reservations. See https:/ /bugs.launchpad .net/evergreen/ +bug/1835127/ comments/ 2 and https:/ /bugs.launchpad .net/evergreen/ +bug/1816475/ comments/ 19. Thanks to Jane Sandberg for pointing this out.
So, rather than reusing ADMIN_BOOKING_ RESOURCE_ TYPE as a retrieve perm, working branch user/jeffdavis/ lp1873048- booking- resource- view-perms adds a new VIEW_BOOKING_ RESOURCE_ TYPE perm, which can be scoped to the system level or whatever, as needed. A new VIEW_BOOKING_ RESOURCE perm is also added for consistency.
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ jeffdavis/ lp1873048- booking- resource- view-perms