Imeji User Management

From MPDLMediaWiki
Revision as of 09:34, 10 April 2012 by Kleinfercher (talk | contribs) (added category)
Jump to navigation Jump to search

Template:Imeji

Scenarios[edit]

Implemented (Beta Release)[edit]

  • User account creation: Only system administrators have the right to create new user accounts.
  • User can edit his own information and change his password.
  • Every registered user is an account user that has the right to create own collections.
  • One user can have as many privileges as he gets.
  • Account information is sent per email

Not implemented[edit]

  • User account creation: It should be possible that every user can create his own account -- discarded?
  • 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
  • create collections
  • create albums
  • create metadata profiles
  • inherits all rights from the MD Profile Administrator, the Collection Administrator, and the Album Administrator
(context: whole imeji) implemented: Beta Release
Collection Administrator

Is allowed to work on one specified collection (context)

  • define following roles for the selected collection:
  • collection administrators
  • collection editors
  • image editors
  • collection viewers
  • change privileges (add a new one, delete an old one)
  • inherits all rights from the Collection Editor
(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)

  • edit collection
  • release/withdraw/delete collection
  • inherits all rights from the Image Editor
(context: only one specific collection) implemented: Beta Release
Image Editor

Is allowed to work on pictures of one specified collection (context)

  • upload pictures
  • delete/withdraw pictures
  • assign metadata values
  • inherits all rights from the Collection Viewer
(context: only one specific collection) implemented: Beta Release
(Collection) Viewer Is allowed to view pictures of a pending collection (context) (context: only one specific collection) implemented: Beta Release
Album Administrator

Is allowed to work on one specified album (context)

  • define following roles for the selected album:
  • album administrators
  • album editors
  • change privileges (add a new one, delete an old one)
  • edit album
  • release/withdraw/delete album
  • inherits all rights from the Album Editor
(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)

  • add pictures
  • remove pictures
(context: only one specific album)
MD Profile Administrator

Is allowed to work on one specific metadata profile (context)

  • define metadata profile editors
  • inherits all rights from the MD Profile Editor
(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)

  • edit metadata profile
  • release/withdraw metadata profile
(context: only one specific MD profile) implemented: Beta Release

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

  • view all images, collections, metadata profiles, and albums
  • view all account users
  • create/delete account users
  • delete images, collections, metadata profiles, and albums

Use Cases[edit]

User Management[edit]

Administrative Search[edit]