The holdings editor now works better for Sitka libraries but there is a problem with depth of editing permissions/access.
Library staff can now change the owning library of holdings they do not own. They should not be able to do so and should receive an override advising them of such. We think this is a bug.
Testing confirms they can only change the owning library to their own library (or libraries) , which is expected and correct, and once changed and saved they cannot change it back to the original owning library , i.e. they are correctly restricted to their own org units as expected.
We think the grant depth of UPDATE_VOLUMN is ignored. There should be an override blocking access to non-owned holdings.
Co-op Support reverts the record for the site when this is reported to us.
We have this fix on production in 3.9.0 .
The holdings editor now works better for Sitka libraries but there is a problem with depth of editing permissions/access.
Library staff can now change the owning library of holdings they do not own. They should not be able to do so and should receive an override advising them of such. We think this is a bug.
Testing confirms they can only change the owning library to their own library (or libraries) , which is expected and correct, and once changed and saved they cannot change it back to the original owning library , i.e. they are correctly restricted to their own org units as expected.
We think the grant depth of UPDATE_VOLUMN is ignored. There should be an override blocking access to non-owned holdings.
Co-op Support reverts the record for the site when this is reported to us.