Difference between revisions of "Faces Content Models"

From MPDLMediaWiki
Jump to navigation Jump to search
m
Line 13: Line 13:
**'''Workflow:''' No rules for now
**'''Workflow:''' No rules for now
**'''Validation rules:''' No rules for now
**'''Validation rules:''' No rules for now
**'''Responsible org units:'''MPI BF
**'''Responsible org units:''' MPIB


===Proposal===
===Proposal===

Revision as of 06:33, 12 June 2008

eSciDoc Solutions

PubMan:
Overview · Functionalities
Interfaces · Support

Faces:
Overview · Functionalities
Scope · Support

ViRR:
Overview · Functionalities
Scope · Support

imeji
Digitization Lifecycle

edit

This is a protected page.

Restricted Access

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