Difference between revisions of "Taxon Names Reconciliation Service"

From Gcube Wiki
Jump to: navigation, search
(Architecture)
Line 22: Line 22:
  
 
== Deployment ==
 
== Deployment ==
 
All the components of the service must be deployed together in a single node. This subsystem can be replicated on multiple hosts and scopes, this does not guarantee a performance improvement because this is associated to the requests which are made towards the database.
 
  
 
=== Small deployment ===
 
=== Small deployment ===
Line 32: Line 30:
  
 
=== Well suited Use Cases ===
 
=== Well suited Use Cases ===
 
The Service is particularly suited to support processing on large dataset of timeseries and to collect statistics on such data.
 
 
== Subsystems ==
 

Revision as of 17:52, 11 May 2012

A service for performing assessment and harmonization on taxa. The aim is to provide users with an interface and methods for assessing if values are not correct, anomalous or for performing processing and aggregation operations 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 classification of species coming from multiples repositories.

Data can come from the Species Discovery Service or they could be uploaded from a user by means of a web interface. The service is able to interface to other infrastructural services in order to expand the number of functionalities and applications to the data under analysis.

Design

Philosophy

This represents an endpoint for users who want to process taxa in order to explore their coherence and to extract some hidden properties from collected data coming from difference sources.

Architecture

Deployment

Small deployment

The deployment follows the schema of the Architecture

Use Cases

Well suited Use Cases