Releases: DCMLab/romantic_piano_corpus
Full extraction with ms3 v2.4.1, including chords facet; added pre-commit hook (workflow v4.3)
Added chords facet
Not to be confounded with labels or chord annotations, a chord is a notational unit in which all included notes are part of the same notational layer and have the same onset and duration. Every chord has a chord_id and every note is part of a chord. These tables are used to convey score information that is not attached to a particular note, such as lyrics, staff text, dynamics and other markup. More information on the columns can be found in the documentation of the ms3 parser.
Added pre-commit hook
The new iteration of the DCML annotation workflow moves the automatic validation of scores and annotations from GitHub actions to the local user. Whenever you are planning to commit changes to the annotation labels, you may want to install the pre-commit package to then run pre-commit install in your local clone. From this moment on, each time you try to commit changes to one or several MuseScore files, the hook will run ms3 review on them and will reject the commit if warnings are detected. If no warnings are detected, the commit will be enriched with all updates to the repo's TSV files that reflect the changes you've made to the scores.
Frictionless datapackage
This release is the first one that has a frictionless datapackage attached (below). It consists of
romantic_piano_corpus.zip, a ZIP file containing one TSV file per facet, that corresponds to a concatenation of the TSV files in the respective folder, that isromantic_piano_corpus.chords.tsvromantic_piano_corpus.expanded.tsvromantic_piano_corpus.measures.tsvromantic_piano_corpus.metadata.tsv(concatenation of a single file)romantic_piano_corpus.notes.tsv
romantic_piano_corpus.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 romantic_piano_corpus.datapackage.jsonv2.0: Re-extracts all files using ms3 v2.2.1
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 romantic_piano_corpus/measures/op12n01.tsv has been renamed to romantic_piano_corpus/measures/op12n01.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 romantic_piano_corpus/measures/op12n01.tsv has the corresponding descriptor romantic_piano_corpus/measures/op12n01.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 op12n01 can be seen
in romantic_piano_corpus/reviewed/op12n01.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.
An Annotated Corpus of Tonal Piano Music from the Long 19th Century (v1.1.1)
This corpus has been created within the DCML corpus initiative and employs
the DCML harmony annotation standard.
Version 1 has been released for submitting it as part of the data
report Hentschel, J., Rammos, Y., Neuwirth, M., Rohrmeier, M. (forthcoming). An Annotated Corpus of Tonal Piano Music from the Long 19th Century
that accompanies nine corpora grouped under the DOI 10.5281/zenodo.7483349.
Version 1.1.1 comes with a complete set of metadata and score headers. Among more accurate composition dates, the
metadata now include URIs that identify the compositions in terms of
the Virtual International Authority File (VIAF), Wikidata, IMSLP
and MusicBrainz. The data has been re-extracted from the scores
using ms3 1.1.1.
The publication covers the following corpora (the DOI links always point at the latest version respectively):
An Annotated Corpus of Tonal Piano Music from the Long 19th Century (v1.1)
This version was rejected by Zenodo due to an error in the .zenodo.json file.
An Annotated Corpus of Tonal Piano Music from the Long 19th Century (v1.0)
This corpus of annotated music scores has been created within the DCML corpus initiative and employs the DCML harmony annotation standard.
Version 1.0 has been released for publication of the data report Hentschel, J., Rammos, Y., Neuwirth, M., Rohrmeier, M. (forthcoming). An Annotated Corpus of Tonal Piano Music from the Long 19th Century.
The publication covers the following corpora: