TBradley27/FilTar

Encode metadata in TSV format rather than YAML

TBradley27 opened this issue · 1 comments

Encoding metadata in a serialisation language such as YAML has quite a few drawbacks - either you have to heavily normalise the data (making data association more difficult), or you have to encode the data in highly nested structures which is also quite difficult to manipulate or reason with.

It would be better to encode all metadata in tsv format. This would necessitate rescripting of downstream workflow management processes. It is also possible that this rescripting will make workflow management simpler, more interpretable and easier to manage.

It is also a good idea to separate configuration data and metadata into different files which is not currently the case.

This is fixed with aaf8198