Difference between revisions of "Content Manager"
| Line 1: | Line 1: | ||
| − | The Content Manager | + | The Content Manager service provides uniform access to content hosted or served by a variety of back-ends, both inside and outside the system. It is the central component of the gCube [[GCube_Information_Organisation_Services_(NEW)|subsystem] that deals with organisation of content and related data. |
= Service Design = | = Service Design = | ||
| + | The Content Manager is designed as an [[OCMA:_The_Open_Content_Management_Architecture|OCMA] service. In OCMA terms, it classifies as a ''multi-type'', ''1-N adapter'' service. It supports two front types for, respectively, reading and writing content modelled as labelled trees. Collectively, the front types and the content model define the ''<code>gDoc</code>'' access type of the service. The service adapts then adapts the <code>gDoc</code> type to multiple back types. For this, it employes an open architecture of type-specific plugins to which it delegates the creation and operation of its collection managers. | ||
Revision as of 22:12, 30 August 2010
The Content Manager service provides uniform access to content hosted or served by a variety of back-ends, both inside and outside the system. It is the central component of the gCube [[GCube_Information_Organisation_Services_(NEW)|subsystem] that deals with organisation of content and related data.
Service Design
The Content Manager is designed as an [[OCMA:_The_Open_Content_Management_Architecture|OCMA] service. In OCMA terms, it classifies as a multi-type, 1-N adapter service. It supports two front types for, respectively, reading and writing content modelled as labelled trees. Collectively, the front types and the content model define the gDoc access type of the service. The service adapts then adapts the gDoc type to multiple back types. For this, it employes an open architecture of type-specific plugins to which it delegates the creation and operation of its collection managers.
