Permissions Ignoring Working Org Unit

[Joan Kranich]

Evergreen Release 3.0.7

Permissions set at a library level are now based on the Home Library in the staff patron record (login record) and not based on the Working Org Unit of that patron record.

For example, CW MARS sets the permission UPDATE_COPY at the library level.
Only the owning library can edit their items.
The owning library in past releases was based on the Working OU in the Permission Editor for the specific login and not based on Home Library.

Some time around release 2.12 this changed and used both the Home Library and the Working OU.
In 3.0.7 the permission uses only the Home Library and ignores the Working OU.

If I log in with a staff record with a Home Library of Gaylord and a Working OU Northborough, I can edit items owned by Gaylord. I cannot edit items owned by Northborough.

[Michele Morgan (mmorgan)]

I can confirm the home library is being used as context for copy editing permission on a 3.0.7 system. But I am seeing that the working location is being used as context as well.

In both the web client and xul client, I logged in at a Danvers workstation as a user with Lynnfield home library and Wakefield working location. I was able to edit copies belonging to both Lynnfield and Wakefield.

Marking Confirmed.

[Meg Stroup (mstroup)]

Adding that we have experienced this issue on a 3.1.10 system.

What we are seeing matches the behavior Joan describes above.