This will be a major change because metadata.tsv functions as a corpus control file. This means that it plays a central role in the ms3 code base, but also in dimcat or the documentation pages at https://dcmlab.github.io/standards/

It is clear that after this change, ms3 still needs to be able to handle (and update) corpora with a metadata.tsv. The advantages that this change brings:

• metadata files have distinctive file names and can be attributed to their corpus (rather than all having the same file name)
• they come with a JSON descriptor just like all other TSV files