Difference between revisions of "TimeSeries"
Lucio.lelii (Talk | contribs) (→Architecture) |
Lucio.lelii (Talk | contribs) (→Architecture) |
||
| Line 19: | Line 19: | ||
=== Architecture === | === Architecture === | ||
| + | |||
| + | The subsystem comprises the following components: | ||
| + | |||
| + | * '''TimeSeries service''': the service core; | ||
| + | |||
| + | * '''TimeSeries client library''': a library to connect to the service. | ||
| + | |||
| + | A diagram of the relationships between these components is reported in the following figure: | ||
[[Image:timeseriesservicearch.png|frame|center|TimeSeries service Architecture]] | [[Image:timeseriesservicearch.png|frame|center|TimeSeries service Architecture]] | ||
Revision as of 17:07, 11 May 2012
A service for performing assessment and harmonization on time series. The aim is to provide users with an interface and methods for assessing if values are not correct, for linking with codelists (for a better managing) or for performing some processing and aggregation on such data. This document outlines the design rationale, key features, and high-level architecture, as well as the options deployment.
Overview
The goal of this service is to offer a single entry for processing, assessing and harmonizing time series.
The service is able to import data using different protocols.
Design
Philosophy
This represents an endpoint for users who want to process time series in order to extract informations.
Architecture
The subsystem comprises the following components:
- TimeSeries service: the service core;
- TimeSeries client library: a library to connect to the service.
A diagram of the relationships between these components is reported in the following figure:
