Talk:Faces User Management

Faces roles

Unregistered user

• As described in article page i.e. FACES VIEWER
• Has privileges to see all item metadata (images accordingly to the component visibility)

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)

Account user

• ALBUM CREATOR
• Has privileges to create albums (containers) in "Faces" context
• Has privileges to add items into his own private albums
• Has privileges to share his own private albums with other account user which means that these other account users can edit the private albums, too.
• Has privileges to publish (release) his own albums (containers) in the "Faces" context
• Has privileges to see all item metadata and components (independent on component visibility) in the "Faces" context

Discussion

• 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)
• 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 --Kristina 06:32, 12 June 2008 (UTC)
• My assumption:
  • 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

Coordinated Universal Time