Talk:AWOB Concepts Actor

MPDL,GAVO

= Overview = A person or an organization(org) exists without any relationship with an awob. If a person or an org interacts with an awob instance, they could become a certain type of a user of an awob, and could play a certain role in a project or in some other contexts. Therefore, we identify different users and roles, grouped depending on conext:


 * Generic Actors: actor types which exist independent of awob.
 * System/Account: user account type that an individual has in an AWOB installation (from now on simply AWOB)
 * Project: roles that users have with an AWOB project
 * Session/Runtime: session level roles of users

= Generic Actors =
 * Actors which exist independent of awob.

Individual

 * is a person who has a valid e-mail address and has necessary qualifications to become an AWOB user.

System Administrator(sys admin)

 * an Individual
 * installs AWOB.

Possibly Organization (TBD)
= Actors by AWOB Account type =
 * Categorized by user account that inidividuals have an AWOB installation (henceforth called awob).

Registered User

 * an Individual that has a user account within an AWOB instance
 * can login to an AWOB instance with its own username and password.
 * has a 'RU dashboard'.
 * can edit its own 'user profile' in the system.
 * can see other 'visible RUs' (see discussion)
 * can request an additional 'awob system role(awob sys role)'.

Project Creator(PC)

 * an RU
 * can create a project in the system.
 * can take on any role in projects created by itself.

Moderator(AM)

 * A PC
 * Can assign 'project creator' role to a RU upon request.
 * ANY MORE? Eg: can decide whether an Individual can become an RU?

AWOB Administrator (AA)

 * a moderator
 * can assign any AWOB system role to any RU.
 * Can configure system
 * e.g. to allow all users from certain email domain to become project creators

= Actors within an AWOB session =

User

 * Generic role representing any usage of AWOB by whatever means.
 * Need not be an Individual who is actively interacting through a web browser. Could be code, say Google-like web crawlers. Possibly applications interacting with AWOB through an API. Can be authenticated or not.

Anonymous User(AnonU)

 * a User not known to the system (not authenticated)
 * can only access public parts of AWOB. ToBeDefined ...

Authenticated/Logged-in User (AuthU)

 * A registered user who has opened a login session with AWOB.
 * Privileges derived from the actual RU's account information, roles, projects etc
 * e.g. Can view/edit RU's dashboard
 * etc

= Actors within an AWOB project (awob project role)= Actors defined by the possible roles that an individual can play within a project. This part needs more discussion to be completed beyond the scope of the demonstrator. In particular need to decide how to control access privileges on project resources, based on either by awob project role or by assigning roles like create/read/modify/delete on individual resources to individual project members.

Project Member(PM)

 * Any individual related to a project

Project Editor(PE) (other name?)

 * is a Project Member
 * Required before a member can make changes to the project.
 * Does not imply the member can make any type of changes. Likely includes:
 * create new project content, e.g. wiki pages/upload files to the project.

Email User(EU)

 * isa Project Member
 * participates in a project only via email, in a sense is an "email list user".
 * can receive and send emails from/to a project mailing list.
 * can send resources as attachments that will be added to project resources.

Project Admin (TBD do we need this)

 * Thought of as someone who does the "dirty work" for a PI or Co-I.
 * But does not have authority to make a decision.
 * Needs discussion

Project Co-Investigator(Co-I)

 * a Project Admin
 * In terms of project site management Co-I and PI have almost the same actions/privileges except final saying in close project, release data, submit the paper(Ask scientists)
 * can do the following in a project to which it belongs.
 * invite an user to the project.
 * assign an awob project role other than 'PI' (and 'Co-I'? TOD) to an accepted 'invitee of a project'.
 * edit 'most project content', though this depends on how we allow

Project Principal Investigator(PI)

 * a Co-I
 * can do the following in a project to which it belongs.
 * assign Co-Is to its own project.
 * assign any awob project role to an accepted 'invitee of a project'.
 * set/alter project status
 * close the project.

= Other possible roles in a project =
 * External Collaborator
 * an individual
 * participate in the project providing comments or performing specific tasks.
 * needs more inputs from scientists.

Project Browser

 * minimum awob sys role required, RU
 * one can only browse through contents of a private project.

Referee

 * a project browser. Must therefore have a (temporary) account, possibly created by PI???

Project Invitee
A person who is invited to join a project.
 * Must be an individual.
 * See "Invite Collaborators" user stories.

= Disscussion =
 * what's on user profile?
 * make oneself visible/searchable by other RUs?
 * For searchable options: by email, by name, etc