Difference between revisions of "Data Assessment, Harmonisation, and Certification Facilities"
From Gcube Wiki
m (Created page with '... == Overview == ... == Key Features == ;feature 1 :description == Subsystems ==') |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
== Overview == | == Overview == | ||
| − | ... | + | The iMarine EA Community of Practice works on a wide range of data types with different sources and targets; our main objective is to let the user consume this data in an uniform and useful way. Data retrieved using different format and protocol is harmonizated and assessed using the service offered by this area and by the one already present in the system. |
| + | |||
| + | In order to meet the requirements a number of components have been designed. | ||
| + | |||
| + | This document outlines the design rationale and high-level architecture of such components. | ||
== Key Features == | == Key Features == | ||
| − | ; | + | The components part of the subsystem provide the following main key features: |
| − | : | + | |
| + | ;Pluglable data consumption service | ||
| + | :the data consumption service follow a plugin architecture where the plugin provide access to a type of datasource | ||
| + | ;Component reuse | ||
| + | :Components are design to be reused in different services | ||
| + | ; | ||
| + | |||
| + | == Main Components == | ||
| − | + | ;the [[Tabular Data Flow Manager]] | |
| + | :this family of components provide a tabular data flow mechanism. | ||
| + | ;the [[Occurrence Data Reconciliation]] | ||
| + | :TODO. | ||
| + | ;the [[Taxon Names Reconciliation Service]] | ||
| + | :TODO | ||
Revision as of 14:30, 11 May 2012
Overview
The iMarine EA Community of Practice works on a wide range of data types with different sources and targets; our main objective is to let the user consume this data in an uniform and useful way. Data retrieved using different format and protocol is harmonizated and assessed using the service offered by this area and by the one already present in the system.
In order to meet the requirements a number of components have been designed.
This document outlines the design rationale and high-level architecture of such components.
Key Features
The components part of the subsystem provide the following main key features:
- Pluglable data consumption service
- the data consumption service follow a plugin architecture where the plugin provide access to a type of datasource
- Component reuse
- Components are design to be reused in different services
Main Components
- the Tabular Data Flow Manager
- this family of components provide a tabular data flow mechanism.
- the Occurrence Data Reconciliation
- TODO.
- the Taxon Names Reconciliation Service
- TODO
