Skip to content

v2.0: Re-extracts all files using ms3 v2.2.1
Compare
Choose a tag to compare
@johentsch johentsch released this 08 Sep 16:42
· 5 commits to main since this release
v2.0
587781b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changes to the TSV facets

Updated filenames

The TSV files have been renamed and now come with a suffix specifying the data facet that they represent. The three facets are

  • measures
  • notes
  • harmonies

so, for example, the file measures/op08n01.tsv has been renamed to measures/op08n01.measures.tsv.

Added resource descriptors

Each TSV file is now accompanied with a JSON resource descriptor following the frictionless specification for Tabular Data Resources. They can and have be used to validate the tabular data.

These files have the same names as the TSV files they describe but replacing the .tsv extension with .resource.json. For example, the file measures/op08n01.tsv has the corresponding descriptor measures/op08n01.resource.json.

These metadata files replace the previous csv-metadata.json files (which followed the CSVW standard) that had described the data inadequately.

Added column quarterbeats_all_endings

The quarterbeats column (also known as qstamp) that had already been available does not provide values for first or third endings, expressing the dimensions of a singular playthrough without taking into account any repeats. The newly added column quarterbeats_all_endings does not have any empty values, providing continuous positions as if each measure followed the previous one.

Renamed index column

The first column of metadata.tsv was renamed from fname to piece.

Changes to the reviewed folder

The _reviewed.mscx files compare the current set of annotation labels against those from the previous version (v2.1). They are identical, so no differences are displayed.

Wherever the MuseScore parser throws one or several warnings (e.g. because an
annotation label does not match the score very well), these warnings appear in a .warnings file. For example, the
warnings for op08n01 can be seen
in reviewed/op08n01.warnings.
One goal for future versions of this dataset would be to reduce the number of warnings to the point
of addressing all of them.

Frictionless datapackage

This release is the first one that has a frictionless datapackage attached (below). It consists of

  • medtner_tales.zip, a ZIP file containing one TSV file per facet, that corresponds to a concatenation of the TSV files in the respective folder, that is
    • medtner_tales.expanded.tsv
    • medtner_tales.measures.tsv
    • medtner_tales.metadata.tsv (concatenation of a single file)
    • medtner_tales.notes.tsv
  • medtner_tales.datapackage.json, the package descriptor.

If one has the frictionless framework installed, one can use the descriptor to validate the package using the command

frictionless validate medtner_tales.datapackage.json
Assets 4
Loading