Difference between revisions of "Data Assessment, Harmonisation, and Certification Facilities"
From Gcube Wiki
(→Main Components) |
|||
| Line 20: | Line 20: | ||
;the [[Tabular Data Flow Manager]] | ;the [[Tabular Data Flow Manager]] | ||
| − | :this family of components | + | :this family of components provides a tabular data flow mechanism. |
;the [[Occurrence Data Reconciliation]] | ;the [[Occurrence Data Reconciliation]] | ||
| − | : | + | :this family of components provides a service for performing assessment and harmonization on occurrence points of species. |
;the [[Taxon Names Reconciliation Service]] | ;the [[Taxon Names Reconciliation Service]] | ||
:TODO | :TODO | ||
Revision as of 14:31, 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 provides a tabular data flow mechanism.
- the Occurrence Data Reconciliation
- this family of components provides a service for performing assessment and harmonization on occurrence points of species.
- the Taxon Names Reconciliation Service
- TODO
