Changes between Version 51 and Version 52 of ProjectDocumentation

Timestamp:

Jun 16, 2018, 6:20:29 PM (6 years ago)

Author:

sommeria

Comment:

--

ProjectDocumentation

@@ -60 +60 @@
 = 4 - Methods of calibration and data processing =
 = 5 - Organisation of data files =
-All data related to a project are stored in a given folder, accessible to all team members. For the Coriolis platform,it is named  "/.fsnet/project/coriolis/year/project key name". Data must be properly stored and documented, taking into account the future constraints of data processing and publication beyond the research team, see section [#Datamanagement]. Although the details of data organisation should be adapted to different projects, some general rules must be followed:
+All data related to a project are stored in a given folder, accessible to all team members. For the Coriolis platform,it is named  "/.fsnet/project/coriolis/year/project key name". Data must be properly stored and documented, taking into account the future constraints of data processing and publication beyond the research team, see section [#Datamanagement #Datamanagement]. Although the details of data organisation should be adapted to different projects, some general rules must be followed:
 
  * A key request is to properly define a set of experiments, to be described in the table of section 6. The data from each instrument should properly refer to its experiment name.
@@ -111 +111 @@
 = 9 - Data management = #Datamanagement
 We can distinguish three steps:
- * Raw data: as given by the different instruments. They are generally stored in local disks, instrument units (volts, pixels for images...). The available formats are often limited and proprietary to the company selling the instrument. For long data sets, avoid text formats which are longer to read and occupy more disk space than binary formats. 
+
+ * Raw data: as given by the different instruments. They are generally stored in local disks, instrument units (volts, pixels for images...). The available formats are often limited and proprietary to the company selling the instrument. For long data sets, avoid text formats which are longer to read and occupy more disk space than binary formats.
  * Processed data: they are stored in storage bays with backup system, as local instrument disks are quickly full and less safe. Physical units and standard formats are needed for communication to researchers who did not participate in the project.
  * Published data: they contain a selection of the most "interesting" data, and involve various analysis of the processed data, like statistics, plots, which are very dependent on the project. We consider two levels of published data.
-
- 
- 
+   * Publication on the OpenDAP server of LEGI: this allows for flexible modification and online consultation, see [https://servforge.legi.grenoble-inp.fr/projects/soft-trokata/wiki/SoftWare/ProjectMeta] for details. 
+   * Publication as a Zenodo archive: its advantage is the perennity of the storage and its support by European authorities. However, the data of a project are limited in size (50 Go), and can be only downloaded as a .zip archive, without online consultation. It is appropriate as a final step after the OpenDAP. [[BR]]