...
Note: Units has moved to directly after "Field" for ease of finding it.
When exporting
Populates as many metadata fields as possible, including name.
When exporting from Data Sources, we no longer append the input set name (Corresponding with the Data Source Group) to the Name metadata.
Above the data
...
(See image below), each
...
header will be a "key". The key is aiming to uniquely identify each column but also retain some information of the column metadata to make it more user friendly. The key is made up of two parts, the "Field" metadata (unique within the res.csv file) and a descriptive part (not necessarily unique within the res.csv file). The metadata should be referenced via the field when distinguishing the differences between each column. The key will always start with the "Field" metadata to make it unique, but to descriptive part depends on where it is exported from:
From Results Manager or any place in which has
...
the "Site" and "Structure" metadata it will be: Field > Site > Structure
From Data Sources or any place
...
that DOESN'T
...
have all the metadata it will be: Field > Name
...
When exporting
Populates as many metadata fields as possible, including name.
...
When importing
The metadata will be loaded into the domain object, but will for the most part be hidden from the UI. The UI will determine how the data is displayed.
...