...
From Data Sources or any place that DOESN'T have all the metadata metadata it will be: Field > Name
When exporting
From Results Manager or any place in which has all the adequate metadata it will populate the Populates as many metadata fields such as scenariopossible, run name, input sets, site, structure, etc but NOT the "Name" field
From Data Sources or any place that DOESN'T have all the metadata we will populate the name field, and only some of the other metadata fields will be used like units and input sets (Although input sets will have a different meaning) all unused fields will be empty. This is because these metadata fields will be stripped when reading them in to certain places like Data Sources.
...
including name.
When exporting from Data Sources, we don't add/overwrite the input set name to correspond with the the Data Source Group.
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.
Importing into Results Manager
When Data was exported from a Results Manager a run it should be able to use contain all the metadata to recreate the key in such a way , it will be able to replicate a the tree structure that it had before it was exported.
When Data was exported from a place that didnthe res.csv doesn't insert contain all the required metadata (such as Data Sources, importing a csv than exporting as a res.csv) it will appear to flatten the data.
Reading into Data Sources or Other places
We think it will be best have chosen not to strip most any of the metadata for a few reasons:
The user can rename the Data Source item/column and it would be difficult to maintain that
As the metadata doesn't necessarily represent what it did when it was exported:
Scenario name: if imported into Data Sources in a different scenario you might expect it to now have that new Scenario name for this data when you export it
Run name: the data should no longer be connected with a run
Input set: input sets in Data Sources refers to which input sets this data source is assigned to rather than the input set that was used in the run when the data was created
...
in attempt to be able to round trip as close to the original file
However, as names need to be unique, we will append the Field metadata to the Data Source name to any non unique columns
Backwards Compatibility for the original format
...