Difference between revisions of "Content Manager"
From Gcube Wiki
| Line 1: | Line 1: | ||
| − | 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. | + | The Content Manager service provides its clients with 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 | + | The Content Manager is designed as an [[OCMA:_The_Open_Content_Management_Architecture|OCMA]] service. In OCMA terms, it classifies as a [[OCMA:_The_Open_Content_Management_Architecture#Service_Classes|''multi-type'', ''1-N adapter'']] service: |
| + | |||
| + | * it is a multi-type service because it supports two front types for, respectively, reading and writing content modelled as labelled trees. Collectively, the front types and the tree content model form the ''<code>gDoc</code>'' access type of the service. | ||
| + | * it is an adapter service because it adapts the <code>gDoc</code> type to multiple back types. For this, the service employes an open architecture of type-specific plugins to which it delegates the creation and operation of its [[OCMA:_The_Open_Content_Management_Architecture#Collection_Managers|collection managers]]. | ||
Revision as of 09:23, 31 August 2010
The Content Manager service provides its clients with 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 subsystem that deals with organisation of content and related data.
Service Design
The Content Manager is designed as an OCMA service. In OCMA terms, it classifies as a multi-type, 1-N adapter service:
- it is a multi-type service because it supports two front types for, respectively, reading and writing content modelled as labelled trees. Collectively, the front types and the tree content model form the
gDocaccess type of the service. - it is an adapter service because it adapts the
gDoctype to multiple back types. For this, the service employes an open architecture of type-specific plugins to which it delegates the creation and operation of its collection managers.
