Talk:Faces User Management

User Roles

• 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...--Ulla 08:55, 12 June 2008 (UTC)
• not certain if all Face albums by users should be created in "Faces" context in fact

What other context is possible? --Kristina 09:15, 27 June 2008 (UTC)

• My assumption (Natasa):
  • 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 (image) visibility.

Background: Currently only the states private (only visible for the creator of the image) and public (visible for all users) are available in the framework. But for Faces we need more. Therefore the role "Privileged Viewer" will be implemented which allows a user to view all private components within a special context (Faces) also when he is not the creator. This role has to be automatically assigned to each Faces account user.

--> Role was delivered by the framework

Use Case

Coordinated Universal Time