Hiltje de Vries
My feedback
3 results found
-
48 votes
Dear community,
Thanks for raising this idea.
I would like to better understand the requirement:
Do you want to limit users to be able to install/use only cloud apps that they have the proper roles for operating? Meaning - users will not be able to install/use a cloud app they do not have the required roles to operate it.
or
Do you want to allow the use of cloud apps only for users that you specifically choose (by giving them a dedicated role for that)? Meaning - users will be able to install/use cloud apps only if they were given a dedicated role for that (for example, a new role "CLOUD_APP_OPERATOR")?
or
Both?
or
Other?
I would be happy to hear your thoughts and clarifications.
Thanks,
Uri Beladev
Platform Product Management team
Hiltje de Vries shared this idea · -
66 votes
An error occurred while saving the comment Hiltje de Vries supported this idea · -
35 votesHiltje de Vries supported this idea ·
An error occurred while saving the comment Hiltje de Vries commentedKeeping 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.
Hi Lisa, Leiden University Library (The Netherlands) has the same problem. Especially our patrons who are doing research for which they need several items with the same title of our Special Collections are complaining. Strange thing is, that ALMA is not completely strict in this policy; requests done by Primo give an error but requests done by staff users using the ALMA item request option are not giving problems.