PubMan Collaboration Scenario
The Collaborator is a user role that privileges special users to access and/or modify items independently of the item status.
An example scenario of the MPI PL is: secretary enters all items and wants to provide all authors with the possibility to access/modify the item in any state
Where are the collaborative rights defined?
- collaborative privileges can be assigned on item level (including all components) and/or on context level (all items within one collection)
What has to be done on admin interface?
- the admin is responsible for creating collaborative usergroups
- the user, who wants to collaborate with selected persons, informs the admin about the desired members of the collaborative group and the chosen name of the collaboration group
- the admin creates the respective collaboration group -> gives collaborative rights to every group member -> informs the enrollee
- afterwards the user is able to choose single/multiple items for collaboration in PubMan
- on context level the admin has to set collaborative rights for the respectivte collaborative usergroups on admin interface
- collaborator privileges for an item can be additionally granted to a particular user, not only to a user group.--Natasa 07:39, 3 August 2010 (UTC)
PubMan workflow for defining Collaborators/collaborative groups
- there are two Collaborator role options:
- a) Collaborator who is privileged to view items in all states
- b) Collaborator who is privileged to view and modify items in all states (except withdrawn)
- on PubMan Item List (My Items) the user chooses single or multiple items for collaboration
- for whole contexts the admin has to set collaborative rights for respective usergroups
- on collaboration tab the user can choose the respective usergroup (or also multiple usergroups) for collaboration
- for every usergroup he/she chooses to collaborate with the user has to define the type of collaboration:
- a) Collaboration-View only or
- b) Collaboration-View & Modify
- all users of the selected usergroups have Collaborator rights and are now able to view and/or modify their collaborative items
- on PubMan Item List it is also possible to deselect items for collaboration / to end collaboration
Who is able to assign collaborative rights?
- on admin interface:
- person, who is responsible for PubMan user management (according the new roles: via admin interface collaborative rights can be assigned to a user or to a user-group only for a context. Thus this can only be done by a user who has the role of Context Administrator - for the contexts she administers) --Natasa 07:42, 3 August 2010 (UTC).
- on PubMan:
- Depositor (if owner of the item)
- Moderator (or any QARole) (see remark above. If the user who is Moderator of the context also has Context administrator right, then this would be possible --Natasa 07:42, 3 August 2010 (UTC))
PubMan Item View
- collaborative item status can be seen and modified by the Depositor (if owner of the item) and Moderator (or any QARole)
- collaborative item status can be seen by the user who has collaborative right for this item as well. --Natasa 07:43, 3 August 2010 (UTC)
PubMan Advanced Search
- query for collaborative items is possible
- but no possibility to search for special collaborative usergroups (might be solved by working with single contexts)
- Collaborative items query is not possible in a simple manner. Maybe this extension shall not be calculated as part of the initial implementation. What is possible, is that we retrieve a list of objects on which a user has collaborative grants. This list of objects could contain any number of context-ids or item-ids or container-ids. In this case, restriction can be additionally applied to the initial advanced search results. --Natasa 07:47, 3 August 2010 (UTC)
My Item Workspace
- separated into two different lists:
- a)"View my items"
- b)"View my collaborative items"
- see the remark on how to retrieve list of collaborative objects in the part of the advanced search. In the same manner, collaborative items could be restricted from the Workspace (by applying an additional filter based on context-ids or item-ids). --Natasa 07:51, 3 August 2010 (UTC)
- UC create collaborative usergroup
- the above UC is already implemented via eSciDoc Admin. In general, it is about creating a user-group and assigning collaborator privilege for a Context. If a collaborator privilege is to be assigned for an Item, then the new UC choose collaborative groups (implemented in PubMan will have to be implemented). --Natasa 07:56, 3 August 2010 (UTC)
- UC choose item for collaboration
- UC select type of collaboration
- UC choose collaborative groups (later: choose single persons for collaboration)
- Requirement coming from NIMS: "deposit on behalf on" via SWORD. As the core-infrastructure does not allow create-on-behalf-on, the workaround would be to create an item and grant a collaborative privilege to a particular user (provided via SWORD Deposit interface). --Natasa 07:54, 3 August 2010 (UTC)
- UC Pubman My Item: show my collaborative items
- UC Collaboration Tab for information on collaboratives in view item version
- In fact, this UC covers UC Choose item for collaboration, UC select type of collaboration and UC choose collaborative groups.
Renaming this UC to "Assign Collaborative rights for item" and describing all steps - would be simpler to understand the implementation. --Natasa 08:01, 3 August 2010 (UTC)
Definition of mentioned user roles
|Depositor||Role that when granted allows to create items in the repository and manage items (including components and their content) he/she created in accordance with the overall workflow rules.|
Is responsible for the quality assurance of the data.
|Collaborator||Two different types of collaborators: collaborator-viewer & collaborator-modifier.
Role that when granted allows access and/or modify the containers, the items, their components and the internally managed content independently of item state.
|Privileged Viewer||Role that when granted allows to access all components and their content of a released item in one context/collection independently of visibility.|