CMS Notes 001

CMS, or Content Management System, is essentially a dashboard that controls data acquisition, storage, and distribution.

Based on pre-determined user-access-rights (vertical and horizontal dimensions) The dashboard facilitates uploading, browsing, and annotation of documents.

For administrative purposes CMS may have a hierarchical structure:

• Acounts : E.g. Philips, Aberdare Etc.
• Users : Eg. Alex(FP), Belinda(FP), JohnDo(Philips)
• Users are assigned roles defining their capabilities
• Content Categories: Documents e.g. Logos, Advertisements, etc
• Documents may consist of single Masters, which contain:
• various file_type versions, e.g. (CMYK)PDF, (RGB)JPG,
• each of which has one or more size instances e.g. (350dpi)Print[_Offline], (150dpi)Proof
• Where it gets interesting is in the organisation of the content, its taxonomy. Taxonomy does dot necessarily mean hierarchical. Hierarchical is just one model of taxonomy. The Object Orientation Model is also a taxonomy, though a taxonomy that starts to lend itself to holarchical perspective. Folksonomy, enough being said about that. I’m curious to look into how relationships can be established via Meta-data, perhaps something like the Dubblin Core Metadata Initiative’s DCMI Abstract Model can be used to create manageable relational protocols flexible enough to allow for the radical demands of disparate situations and contextual complexity.

DCMES={ Title,Creator,Subject, Description, Publisher, Contributor, Date, Type, Format, Identifier, Source, Language, Relation, Coverage, Rights,�}