MEI files that were not generated from MusicXML do not have the right behaviour

[Crowerade]

The app cannot reproduce the changes made to the file when creating a new layer

[yrammos]

I traced the root cause to a lack of xml:id values for <mdiv> and <score> elements in all MEI Basic files that have been produced by MuseScore. As a result, the aforementioned elements do not have unique IDs when they represent added layers.

We should check for these values upon opening a file, and inject them into the MEI, if they are indeed missing.

[yrammos]

Working vs. nonworking MEI with minimal, two-note example. The working MEI was generated from MusicXML by Verovio
within the web app. The nonworking MEI was produced by MuseScore.

[Crowerade]

This should be fixed, I added a new id to every mdiv and score that did not have one so that they can be corresponded to ( commit fe363b3 ). Further development should be needed to have more robust and safer way to generate ids

[yrammos]

This should be fixed, I added a new id to every mdiv and score that did not have one so that they can be corresponded to ( commit fe363b3 ). Further development should be needed to have more robust and safer way to generate ids

@Crowerade FYI a few ways of generating IDs are demonstrated in the MEI Friend codebase: https://www.reddit.com/r/Switzerland/comments/1lyohh8/how_do_we_tell_this_to_younger_generations/#lightbox

[Crowerade]

This should be fixed, I added a new id to every mdiv and score that did not have one so that they can be corresponded to ( commit fe363b3 ). Further development should be needed to have more robust and safer way to generate ids

@Crowerade FYI a few ways of generating IDs are demonstrated in the MEI Friend codebase: https://github.com/mei-friend/mei-friend/blob/826e08f0ab2d07aa3e49ef6b10d4bdc5b2fa69e2/app/static/lib/utils.js#L372

@yrammos I don't think that is the right link :)

[yrammos]

@Crowerade good catch :) Link corrected.