Difference between revisions of "Imeji User Management"
m |
m (→User Roles) |
||
Line 96: | Line 96: | ||
* define metadata profile editors | * define metadata profile editors | ||
* '''inherits all rights from the MD Profile Editor''' | * '''inherits all rights from the MD Profile Editor''' | ||
| (context: only one specific | | (context: only one specific MD profile)<br> | ||
Each '''account user''' per default will be MD profile administrator for his own metadata profiles! | Each '''account user''' per default will be MD profile administrator for his own metadata profiles! | ||
| | | | ||
Line 105: | Line 105: | ||
* edit metadata profile | * edit metadata profile | ||
* release/withdraw metadata profile | * release/withdraw metadata profile | ||
| (context: only one specific | | (context: only one specific MD profile) | ||
| '''implemented: 1.0''' | | '''implemented: 1.0''' <br> | ||
based on collection basis as one collection currently has exactly one MD profile (1:1) | |||
|- | |- | ||
| '''System Administrator''' | | '''System Administrator''' |
Revision as of 10:25, 6 December 2011
|
Scenarios[edit]
Implemented (1.0)[edit]
- User account creation: Only System Administrators have the right to create new user accounts.
- Every registered user is an account user that has the right to create own collections.
- One user can have as many priviledges as he gets.
Not implemented[edit]
- User account creation: It should be possible that every user can create his own account.
- For special purposes (e.g. for students), accounts are needed that have special rights for the context of one or several collections, but do not have the right to create own collections.
- User Groups: Further to the user roles, it would make sense to implement the creation of user groups, which than can have special user rights assigned similar to individual users.
User Roles[edit]
Label | Description | eSciDoc Role | Status |
Account User |
|
(context: whole imeji) | implemented: 1.0 |
Collection Administrator |
Is allowed to work on one specified collection (context)
|
(context: only one specific collection) Each account user per default will be collection administrator for his own collections! |
|
Collection Editor |
Is allowed to work on one specified collection (context)
|
(context: only one specific collection) | implemented: 1.0 |
Image Editor |
Is allowed to work on pictures of one specified collection (context)
|
(context: only one specific collection) | implemented: 1.0 |
(Collection) Viewer | Is allowed to view pictures of a pending collection (context) | (context: only one specific collection) | implemented: 1.0 |
Album Administrator |
Is allowed to work on one specified album (context)
|
(context: only one specific album) Each account user per default will be album editor for his own collections! |
|
Album Editor |
Is allowed to work on the content of one specified album (context)
|
(context: only one specific album) | |
MD Profile Administrator |
Is allowed to work on one specific metadata profile (context)
|
(context: only one specific MD profile) Each account user per default will be MD profile administrator for his own metadata profiles! |
|
MD Profile Editor |
Is allowed to work on one specified metadata profile (context)
|
(context: only one specific MD profile) | implemented: 1.0 based on collection basis as one collection currently has exactly one MD profile (1:1) |
System Administrator |
Is allowed to work on the whole system
|
Use Cases[edit]
User Management[edit]
- UC_LA_UM_01 Create account user
- UC_LA_UM_02 Edit account user
- UC_LA_UM_03 Assign privileges to account user
- UC_LA_UM_04 Deactivate account user
- UC_LA_UM_06 Create user group
- UC_LA_UM_07 Edit user group
- UC_LA_UM_08 Confirm account user