Base document model for Bungeni

Motivation

Currently adding new content types to bungeni requires adding source code to 
the system e.g. : adding tables to the schema/model, writing descriptors and so 
on .  Plugging in workflow, versioning, aaudting etc. also requires adding more 
source code to the system. 

Proposal

A configurable "base document" document model is required for Bungeni. With 
this configurable document model -- the following will be possible :

 -- Add new content types to Bungeni via configuration
  * Configured to have versioning, workflow and auditing
  * Content type can be configured to have attached files and events
  * Content type can be assigned to a group

 -- It will be possible to associate a custom workflow to a new content type

 -- it will be possible to associate the content type to workspaces

 -- Existing content types (questions , motions etc. ) must be handled by this model

 -- Existing visibility rules prescribed in ui.xml must be handled by this model. 

The outcome from all of this is intended to be a bungeni framework with a 
generic document type - which can  be extended to add new document types and 
assoicated behaviors to the system without modifiying existing or writing new 
source code.

Limitations

The following are the proposed limitations 

  -- The available fields will be fixed (and the same ) for all content types

  -- Since additional text, numeric or date fields may be necessary for an unknown content type. These fields may be part of the "base document" model - and can be usable via the ui.xml visibility rules.

Original issue reported on code.google.com by ashok.ha...@gmail.com on 24 Jul 2011 at 10:33

BenoitTalbot / bungeni-portal

Base document model for Bungeni #721