search

ecotaxa / ecopart

A web application dedicated to particle data from UVP and LISST.
Other
0 stars 1 forks source link

Separate EcoPart and EcoTaxa #23

Open picheral opened 4 years ago

picheral commented 4 years ago

On ne devrait à terme n'avoir qu'une seule instance serveur d'EcoPart centralisant toutes les données (en plus des instances mobiles).

grololo06 commented 4 years ago

Techniquement: EcoPart utiliserait l'API pour communiquer avec EcoTaxa.

jiho commented 4 years ago

The metadata could be:

  1. in EcoTaxa and the EcoPart instance is linked with a single EcoTaxa instance and shares its db;
  2. either in both EcoPart and multiple EcoTaxa instances and kept always perfectly in sync;
  3. in EcoTaxa instances only and dynamically fetched/modified by EcoPart through the API.
picheral commented 4 years ago

My opinion is that the import of particle AND images from UVP instruments and later for all interfaced instrument in Jerico3 should be done at a single place. Today, the UVP data (including images) should be doable directly from the Particle Project Management of EcoPart.

picheral commented 4 years ago

It will be the case for Zooplankton data issued from the floats as only plankton DATA will be transfered by satellite.

picheral commented 4 years ago

The metadata of UVP instruments are much better managed on the EcoPART side which should remain the root source. All metadata of associated samples on Ecotaxa must be updated from EcoPart.

grololo06 commented 4 years ago

Assigned to the people involved in the specification/clear-up.

grololo06 commented 4 years ago

Take advantage from this move for ensuring the new EcoPart has the code quality for ensuring future evolution:

As this will need proper re-testing anyway, a (manual) test plan document will help for the future as well.