Faces Content Models

Content model for FACES collection

 * Note: this content model is applicable for R2 of Faces solution and there may be changes in future depending on R3 requirements

Context

 * Context: FaceContext
 * Admin descriptor: No rules for now
 * Workflow: No rules for now
 * Validation rules: No rules for now
 * Responsible org units: MPIB

Proposal
See Discussion page on user management
 * Have extra context for Album creators simply to distinguish them and not to mix - Thus album creators would be able to give further privileges for their albums to other people, check also discussion on

Face collections

 * ContainerCModel: FaceCollection
 * Metadata: Faces Application Profile Collection
 * Members: All face items, released

Proposal
Instead above create 2 objects with FaceCollection CModel.
 * 1. object: Faces collection
 * Members: all face items
 * 2. object: Faces public collection
 * Members: face items with public component level visibility

Both containers would be top level containers in Faces Context.
 * Proposal: to postpone the creation of two separate containers for now until R3 and further requirements. probably we should come back to it later.--Natasa 00:03, 11 July 2008 (UTC)

User albums

 * ContainerCModel: FaceAlbum
 * Metadata: Faces Application Profile Album
 * Members: selected face items by the user
 * Conditions: user who create albums has "Privileged Viewer" role on FacesContext, to be able to see images with private component visibility.--Natasa 14:56, 3 September 2008 (UTC)

Items

 * ItemCModel: FaceItem
 * Metadata: Faces Application Profile FacesItem
 * Conditions:
 * Component has public or private visibility