Difference between revisions of "Talk:Faces User Management"

From MPDLMediaWiki
Jump to navigation Jump to search
 
(21 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=Faces roles=
== UC_FAC_UM_01 Log on to the system ==
===Unregistered user===
: As long as the standard mechanism provided by the coreservices is used this use-case is fine. --[[User:Natasab|Natasa]] 14:27, 25 August 2008 (UTC)
*As described in article page i.e. FACES VIEWER
*Has privileges to see all item metadata (images accordingly to the component visibility)


===Account user===
== UC_FAC_UM_02 Log off from the system ==
*ALBUM CREATOR
*Has privileges to create albums (containers) in "Faces" context
*Has privileges to add items into albums
*Has privileges to publish I.e. release own albums (containers) in "Faces" context
*Has privileges to see all item metadata and components (independent on component visibility) in "Faces" context


== UC_FAC_UM_03 View account users list ==


===Discussion===
== UC_FAC_UM_04 Create account user ==
*not certain if all Face albums by users should be created in "Faces" context in fact
 
*check with institute if the information on created Face albums should be actually also publicly available or only to registered users (metadata, not images)
== UC_FAC_UM_05 Edit account user ==
*check with institute if there will be users who are allowed to create albums from public images only i.e. students (self-registration) --> Not needed --[[User:Kristina|Kristina]] 06:32, 12 June 2008 (UTC)
 
*My assumption:
== UC_FAC_UM_06 Deactivate account user ==
**We need 1 separate context i.e. "Albums context" where users can create albums
 
**We need in "Faces" context thus role "Privileged Viewer" for users who are able to view all items independent on component visibility
== UC_FAC_UM_07 Confirm account user ==
 
== User States ==
 
== User Roles ==
 
== Account User Metadata Set ==
[[User:Kristina|Kristina]] 10:31, 23 December 2008 (UTC):
:* The Admin Solution does not support the saving of more personal data as currently possible (name, organization, e.mail). But it is planned to set up an Identity Provider (IDP), which will displace the Admin Solution.
:* To save the metadata about an account user in the IDP, [[eduPerson]] can be used. Therefore we need "Person resource" (describes a person; means to have a person item). But if "Person resource" will be provided depends also on the FIZ and will be decided in a later step (when the IDP is set up and working).

Latest revision as of 10:31, 23 December 2008

UC_FAC_UM_01 Log on to the system[edit]

As long as the standard mechanism provided by the coreservices is used this use-case is fine. --Natasa 14:27, 25 August 2008 (UTC)

UC_FAC_UM_02 Log off from the system[edit]

UC_FAC_UM_03 View account users list[edit]

UC_FAC_UM_04 Create account user[edit]

UC_FAC_UM_05 Edit account user[edit]

UC_FAC_UM_06 Deactivate account user[edit]

UC_FAC_UM_07 Confirm account user[edit]

User States[edit]

User Roles[edit]

Account User Metadata Set[edit]

Kristina 10:31, 23 December 2008 (UTC):

  • The Admin Solution does not support the saving of more personal data as currently possible (name, organization, e.mail). But it is planned to set up an Identity Provider (IDP), which will displace the Admin Solution.
  • To save the metadata about an account user in the IDP, eduPerson can be used. Therefore we need "Person resource" (describes a person; means to have a person item). But if "Person resource" will be provided depends also on the FIZ and will be decided in a later step (when the IDP is set up and working).

Use Case

Coordinated Universal Time

Intrusion Detection & Prevention

Fachinformationszentrum Karlsruhe

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Talk:Faces_User_Management&oldid=26019"