Difference between revisions of "Faces Content Models"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{ESciDoc Solutions}} | {{ESciDoc Solutions}} | ||
<accesscontrol>MPDL,,Faces,,FIZ,,</accesscontrol> | <accesscontrol>MPDL,,Faces,,FIZ,,</accesscontrol> | ||
==Content model for FACES collection== | ==Content model for FACES collection== | ||
Revision as of 12:28, 12 June 2008
|
This is a protected page.
Content model for FACES collection[edit]
- Note: this content model is applicable for R2 of Faces solution and there may be changes in future depending on R3 requirements
Context[edit]
- Context: FaceContext
- Admin descriptor: No rules for now
- Workflow: No rules for now
- Validation rules: No rules for now
- Responsible org units: MPIB
Proposal[edit]
- 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
See Discussion page on user management
Containers[edit]
Face collections[edit]
- ContainerCModel: FaceCollection
- Metadata: Publication metadata set
- Members: All face items
Proposal[edit]
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.
User albums[edit]
- ContainerCModel: FaceAlbum
- Metadata: Publication metadata set
- Members: selected face items by the user
Items[edit]
- ItemCModel: FaceItem
- Metadata: Publication metadata set
- Conditions:
- Component has public or private visibility