Difference between revisions of "Talk:Faces User Management"

From MPDLMediaWiki
Jump to navigation Jump to search
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=User Roles=
== UC_FAC_UM_01 Log on to the system ==
: 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)


=== Discussion ===
== UC_FAC_UM_02 Log off from the system ==
*A more generic remark: defined component visibility is tricky, as it is required by a certain context (ie. FACES context allows "public" component visibility only for the 6 persons, the rest have to be "private" or "restrcited visibility to the account users.) therefore, definition of component visibility due to certain usage in a certain context might make "re-usage" and "re-purposing" of data tricky. For FACES collection, we still might go this way, as the usage rights for the images will not change, neither in other contextes...--[[User:Uat|Ulla]] 08:55, 12 June 2008 (UTC)
 
*not certain if all Face albums by users should be created in "Faces" context in fact
== UC_FAC_UM_03 View account users list ==
:: What other context is possible? --[[User:Kristina|Kristina]] 09:15, 27 June 2008 (UTC)
 
*My assumption (Natasa):
== UC_FAC_UM_04 Create 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_05 Edit account user ==
:FIZ should be informed immediately on this new role. Pls. contact Willy --[[User:Natasab|Natasa]] 00:12, 11 July 2008 (UTC)
 
== UC_FAC_UM_06 Deactivate account user ==
 
== 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).