Difference between revisions of "The GCube Information Organisation Services"
| Line 3: | Line 3: | ||
The architecture of the subsystem has a hourglass topology. Central to the hourglass is the [[Content Manager (NEW)|Content Manager]] (CM), a service that provides uniform access to content served by a variety of back-ends, both inside and outside the system. The Content Manager models content as edge-labelled trees and it relies on plugins to dynamically adapt to an arbitrary number of back-ends. | The architecture of the subsystem has a hourglass topology. Central to the hourglass is the [[Content Manager (NEW)|Content Manager]] (CM), a service that provides uniform access to content served by a variety of back-ends, both inside and outside the system. The Content Manager models content as edge-labelled trees and it relies on plugins to dynamically adapt to an arbitrary number of back-ends. | ||
| − | Back-ends may include storage services as well as access services to content stored further afield. | + | Back-ends may include storage services as well as access services to content stored further afield. A back-end which is part of the subsystem is the [[Storage Manager (NEW)|Storage Manager]] (SM), a service that stores content and organises it into a web of binary relationships. |
The clients of the Content Manager may also be internal or external to gCube. Clients included in the subsystem are the [[Metadata Manager (NEW)|Metadata Manager]] (MM) and the [[Annotation Manager (NEW)|Annotation Manager]] (AM), two services that describe and annotate content on behalf of other clients. | The clients of the Content Manager may also be internal or external to gCube. Clients included in the subsystem are the [[Metadata Manager (NEW)|Metadata Manager]] (MM) and the [[Annotation Manager (NEW)|Annotation Manager]] (AM), two services that describe and annotate content on behalf of other clients. | ||
Revision as of 23:12, 26 August 2010
The Information Organisation form a subsystem of gCube dedicated to content management, including storage, access, description and annotation.
The architecture of the subsystem has a hourglass topology. Central to the hourglass is the Content Manager (CM), a service that provides uniform access to content served by a variety of back-ends, both inside and outside the system. The Content Manager models content as edge-labelled trees and it relies on plugins to dynamically adapt to an arbitrary number of back-ends.
Back-ends may include storage services as well as access services to content stored further afield. A back-end which is part of the subsystem is the Storage Manager (SM), a service that stores content and organises it into a web of binary relationships.
The clients of the Content Manager may also be internal or external to gCube. Clients included in the subsystem are the Metadata Manager (MM) and the Annotation Manager (AM), two services that describe and annotate content on behalf of other clients.
All the services in the subsystem align with the design patterns of an abstract architecture, the Open Content Management Architecture.
