Table data (excel, csv) parser
Base on changes in #736 (closed), it should not be too hard to provide a parser for excel or csv files.
The challenge here is to find the right schema mapping for the given columns. This could be achieved in different ways:
- an additional user-provided mapping file
- additional mapping data in the existing user-provided nomad.yaml files
- mapping information in the excel file itself
- e.g. full qualified metainfo quantity names as column names
This is also more meaningful, with custom "on-the-fly" schema definitions (#705 (closed)) and schema versioning (#549 (closed))