Upgrade StorageGroup Functions
Hello,
I have a question around the group function in Zotaro. I'm part of a research team that wants to create a private group where we can upload citations, article pdfs and annotate them as a team. However, one of our concerns is being able to track anything that is deleted. From what I have learned through the different resources available on creating private groups, the moment that a group member is given editing rights they can add, edit and delete references? We are looking for a function that allows group members to upload references and edit but not delete references. Is there a function that allows group members access to uploading and editing but not deleting such that only the owner can delete? OR if not, if a group member does delete a reference is there a way to track what is delete, as in maybe the owner is the only person that can empty the trash can? When we tested this function it appeared that a group member given editing rights could delete references/files from the library as well as empty the trash can. Is there a way for only the owner to empty the trash can such that we can track if anything is deleted? We really just need to ensure nothing gets deleted accidentally without having record of it.
Thank you,
Laura
I have a question around the group function in Zotaro. I'm part of a research team that wants to create a private group where we can upload citations, article pdfs and annotate them as a team. However, one of our concerns is being able to track anything that is deleted. From what I have learned through the different resources available on creating private groups, the moment that a group member is given editing rights they can add, edit and delete references? We are looking for a function that allows group members to upload references and edit but not delete references. Is there a function that allows group members access to uploading and editing but not deleting such that only the owner can delete? OR if not, if a group member does delete a reference is there a way to track what is delete, as in maybe the owner is the only person that can empty the trash can? When we tested this function it appeared that a group member given editing rights could delete references/files from the library as well as empty the trash can. Is there a way for only the owner to empty the trash can such that we can track if anything is deleted? We really just need to ensure nothing gets deleted accidentally without having record of it.
Thank you,
Laura
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
Add: add item to beta group, admins pull it in to primary group
Edit: add item to beta and edit as should be, and admins merge or edit the item in primary group
Delete: add a note in beta group, and admins take action in primary group
After a task is done, the corresponding item is deleted from beta group by original proposing member or Admin. Thus, the beta group is just a scratch pad and will never have more than a few items (that are awaiting processing by Admins).
Yes, it means two groups, but is a clean way to protect the primary group while still allowing members to contribute.
As owner of several groups, and planning to share them with other persons, I asked myself this question of refining the access rights too.
First, about protecting entries from deletion by any group member, a solution could be to create a special access level to the "empty trash" function, so that the group owner could choose to give this right to himself only, to every member having admin status or to all members. Unauthorized members could then move any entry to the trash, but only authorized ones could either empty the trash or restore the entries.
Such a solution would also have the advantage of preventing the trash to be emptied by anyone, deleting permanently entries "trashed" by other members.
Imagine the following: A sends entry 12 to the trash and B does the same with entry 43. Then B empties the trash. Later, A changes his mind and wants to restore entry 12. But, at this time, entry 12 does not exist anymore...
(I personally tested this situation on 2 distinct desktops).
In addition, especially for groups with numerous members, it would be great to add a field storing the id of the member who sent the entry to the trash, so that the admin could contact him/her in order to know the reason and decide together what to do with the entry.
The ultimate solution would be to implement both a complete role management functionality, with the ability of creating profiles, and managing detailed Zotero functionalities (not only add, edit, delete) in order to avoid misuses, and also a complete audit trail of every change to the database.
Let me be clear: using Zotero since only a few days, I find this is a great tool resulting from a great job. As a retired IT worker, be sure I'm perfectly aware of the workload my propositions would engage.
Best regards to the team