Difference between revisions of "Metadata Management"
Manuele.simi (Talk | contribs) (→Reference Architecture) |
Manuele.simi (Talk | contribs) (→Reference Architecture) |
||
| Line 3: | Line 3: | ||
=== Reference Architecture === | === Reference Architecture === | ||
| − | The | + | The functionalities expected by the Metadata Management subsystem are implemented by two cooperating services: one taking care of the creation and management of Metadata Objects and Metadata Collections ([[Metadata Manager]]) and another taking care of the support to metadata object retrieval ([[XML Indexer]]) as depicted in Figure 1. |
[[Image:Metadata_Management_architecture.png|center|Figure 1. gCube Metadata Management Reference Architecture]] | [[Image:Metadata_Management_architecture.png|center|Figure 1. gCube Metadata Management Reference Architecture]] | ||
| + | In particular: | ||
| − | * '''[[Metadata Manager]]''' – this Service is responsible for | + | * '''[[Metadata Manager]]''' – this Service is responsible for storing, changing, accessing and manipulating metadata. It associates Metadata Object with Information Objects, remove associations, returns metadata for a given object and updates associated metadata accorinding to the gCube Metadata Model (see the image below); |
| − | + | ||
| + | * '''[[XML Indexer]]''' – this Service is a generic XML Indexer service allowing to query the Metadata Objects by resolving arbitrary XQuery and XPath expressions against its managed content. It indexes homogeneous collections of XML data. | ||
| − | The following figure | + | |
| + | The following figure shows the gCube Metadata Model as implemented by the Metadata Management Services: | ||
[[Image:MetadataModel.png|center|Figure 2. gCube Metadata Model]] | [[Image:MetadataModel.png|center|Figure 2. gCube Metadata Model]] | ||
Revision as of 01:02, 23 June 2009
Metadata Management
In gCube, the Metadata Management has been designed to rely on the storage facilities provided by the Storage Management layer and its support to manage primary and secondary relations between Information Objects. The subsystem is called upon to support the management of metadata objects and metadata collections, i.e. supporting their creation, access, storage and removal of objects compliant with one or more metadata format and their efficient search. To implement such functions the internals of the subsystem has been organised according to the following architecture.
Reference Architecture
The functionalities expected by the Metadata Management subsystem are implemented by two cooperating services: one taking care of the creation and management of Metadata Objects and Metadata Collections (Metadata Manager) and another taking care of the support to metadata object retrieval (XML Indexer) as depicted in Figure 1.
In particular:
- Metadata Manager – this Service is responsible for storing, changing, accessing and manipulating metadata. It associates Metadata Object with Information Objects, remove associations, returns metadata for a given object and updates associated metadata accorinding to the gCube Metadata Model (see the image below);
- XML Indexer – this Service is a generic XML Indexer service allowing to query the Metadata Objects by resolving arbitrary XQuery and XPath expressions against its managed content. It indexes homogeneous collections of XML data.
The following figure shows the gCube Metadata Model as implemented by the Metadata Management Services:
