restricts editing access to analytics to specific subject areas
Any patron with design analytics have access to all subjects areas in analytics. It would good, if we could restrict analytics design access to specific subject arease in analytics.
Hiltje de Vries commented
Keeping the privacy aspect in mind, we would also be so much better equiped if we had this possibility. We can not use the analytics_anonymize_user_details because it does not fit the daily workflow of our circulation staff.
Our staffmembers at the Cataloging/Acquisitions Departments (who need the Design Analytics role) f.e. do not have to be able to make Analytics based on Fulfillment, Requests or Users. May 2018 the Dutch Law on Privacy demands us to demarcate access to privacy information.
Marty Tanner Hughes, UGA Libraries commented
This restriction would be especially useful in the areas affected by the analytics_anonymize_user_details parameter. Not all library staff with design analytics role should be able to see identifying patron data, but the anonymization setting is not granular enough; if we turn it on, staff who need patron data can't see it. Being able to restrict analytics subject areas the way we limit staff who have Fulfillment roles would protect patron privacy.