Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In File version 1: When saving, units has moved to the second column, directly after "Field" for ease of finding it. In order to do this, the metadata fields can now be read in any order and it depends on the metadata headings to map the metadata to the correct field. See attached example.res.csv.

When exporting

Populates as many metadata fields as possible, including name.

...

The metadata will be loaded into the domain object, but will for the most part be hidden from the UI. The We have chosen not to strip any of the metadata in attempt to be able to round trip as close to the original file and the UI will determine how the data is displayed.

...

When the res.csv doesn't contain all the required metadata (such as, importing a csv than exporting as a res.csv) it will appear to flatten the data.

Reading into Data Sources

...

The name chosen for display will be "Site > Structure" if the metadata exists, otherwise the "Name" Field will be used. However, as names need to be unique, we will append the Field metadata to this name for any non unique columns

...