AWOB Task 006

MPDL,GAVO

General Information
Grouping: Short description:

Discussion
We think it is useful to add a label to project members reflecting the role the project member play in the scientific project. This is un prescribed, could be Co-I, PI, etc. Not to be mistaken with the AWOB project role, which deals with privileges a user has in the project.


 * NBU: not certain if i understood well from the VIDConf, i understood that we would not like to use Co-I, PI labels - as these are different in different contexts. Therefore the first draft provided here with non-specific AWOB labels


 * JK: What we meant in our last meeting is that there should be two different types of roles, AWOB project role and science project role. AWOB project role defines the AWOB project access privilege/authorization. Until now we defined them using Actors(PI, Co-I, ProjectMember, see http://colab.mpdl.mpg.de/mediawiki/Talk:AWOB_Concepts_Actor).
 * The science project roles are used commonly in the science community such as PI, Co-I, external collaborator etc.  In many projects,  they need to identify who are the PI(s), Co-Is or etc in their projects. However, there is no fixed set of these science roles in the community and it is better to leave to the scientists which naming convention to use. There is a close relationship b/w these two types of roles.
 * The problem with current AWOB project role names are too similar to the science project roles which makes scientists confused. Therefore, we proposed to change the AWOB project roles such as project lead, project manager, project member, guest, etc.

New roles proposal

 * Project observer - only view privileges on the complete project (no writing at all)
 * Project reviewer - same as Project observer, additionally right to comment on any AWOB Content and AWOB Resources (Files, Wiki, Message boards)

Additional notes on current implementation

 * User role is assigned to each user who creates an AWOB account at present
 * User role is extended, so each registered user has a right to create a project
 * this can be changed depending on the workflow we define in following manner:
 * Administrator verifies the user and gives a Project Owner role, or
 * All Users are automatically assigned with a Project Owner role

Task Visibility

 * 'r', 'w', '-' denote 'read', 'write', 'not available', respectively.
 * 'PM', 'TM', 'TMa' denote 'Project Member', 'Task member', 'Task Manager' respectively