File naming convention

GHS39_<EXPERIMENT>_<PROJECT>_<VARIABLE COLLECTION CODE>_<DATE or DATERANGE>_<DATA PROCESSING>_[VERSION].extension

The individual elements that make up the naming convention are described in detail below. First of all however it is important that you consider the following points

1. All terms in the filename should be upper case apart from the file ending which should be lower case
2. An underscore is used to separate the different ‘elements’ of the filename. An underscore should therefore not be used elsewhere within the filename
3. Do not use illegal characters within a filename, e.g. / ? < > : * | ” as well as a ‘space’.
4. The file naming convention has been constructed to balance the amount of useful detail in the name, the need to ensure file uniqueness, as well as to keep the filename as short as possible.

• GHS39: Official HIE facility code to represent data sourced from the S39 Glasshouse facility (all data from the S39 Glasshouse facility should be prefixed by use of the code ‘GHS39’).

• EXPERIMENT: The experiment the file is associated with. The experiment code is generally a broad category encompassing multiple nested projects, e.g. GREAT, GLAHD, etc

• PROJECT: Which project this data file is associated with. The project short name code should be used in the filename. In the event that the data was from an automated sensor, ‘AUTO’ is used for the project code

• VARIABLE COLLECTION CODE: A collection code that represents a particular grouping of variables contained within a file. A list of variables contained within different variable collection codes can be found in the ‘Collection Codes’ section below.

• DATE or DATERANGE: The date range which a dataset covers (for automated timeseries data for example) or the single date on which a sample, for example, was taken. Note that dates are in the YYYYMMDD format (with a hyphen used to split the start and end date of a date range).

• DATA PROCESSING: The level of post-processing operated on the data. The definitions of the different levels of post-processing can be found below.

• VERSION: An optional version number of the form _Vx. This can be utilised when a new version of a file already existing within HIEv has been updated/corrected (maintaining the same data processing level).

• extension: The format of the data file, e.g. .csv, .dat (for toa5 data) etc.

Examples

• GHS39_GREAT_MAIN_HEIGHTDIAMETER_20160108-20160229_L1.csv
  • A dataset from the main experiment containing tree diameters and heights, measured between 2016-01-08 and 2016‑02-29. Data have not been thoroughly quality checked, but some checking has been done after data entry. (Being version 1 the optional version number is omitted here).

• GHS39_GREAT_MAIN_GX-AQ_20160225-20160226_L2.csv
  • A dataset from the main experiment containing photosynthesis-light response curves (AQ), measured between 2016‑02-25 and 2016‑02-26. Data has been quality checked.
• GHS39_GLAHD_HEATWAVE_BIOMASS_20150211_L1_V2.csv
  • A dataset from the heatwave experiment containing biomass measurements from 2015‑02-11. Data has been checked but not thoroughly processed. This file is an updated version of a previously uploaded file, with some changes have been made to the dataset. Thus this file has been marked as version 2.

Data Processing Codes

The meanings of the different data processing codes used in WTC filenames are as follows:

• R (Raw Data): Data that has been directly extracted from an instrument and that has not been subjected to any data cleaning or postprocessing
• L1 (Level One Data): Data that has been cleaned and processed, but in a cursory manner. Some erroneous data may be included.
• L2 (Level Two Data): Data that has been rigorously cleaned, processed, and checked for quality control.
• L3 (Level Three Data): Archive of published datasets.

Collection Codes

Please edit the table as you see fit! This is a quick draft.