Add more subfields to musical work information

[acka47]

As written in #516 (comment):

people will also want the information from 303, subfields m, n and r.

lobid/lodmill#784 (comment) has the cataloging help for 303. Here is the list of the subfields to add and which RDA properties to use:

• m: http://rdaregistry.info/Elements/w/P10220
• n: http://rdaregistry.info/Elements/w/P10079
• p: We might use http://rdaregistry.info/Elements/w/P10065 with this and the name string as content without creating a separate person object.
• r: http://rdaregistry.info/Elements/w/P10221
• u: Should be attached to the title with separator ,

I think this should suffice for now.

[ChristophEwertowski]

If it's still relevant it should be tackled after lobid/lodmill#784 is solved.

[ChristophEwertowski]

Deployed to test. See hasMediumOfPerformance in exampleOfWork in HT018853619 (test, json) or in containsExampleOfWork in HT018857620 (test, json). For hasMusicalKey or hasNumericDesignationOfMusicalWork also see HT018857620 (test, json).
Subfields u und p are already covered.

[acka47]

This looks good but I think we should use other labels in the JSON than the ones from RDA. For one, we only have very few properties where we use the "hasX" structure and also the keyes are quite long. Here are my suggestions:

• hasNumericDesignationOfMusicalWork -> workNumbering
• hasMusicalKey -> musicalKey
• hasMediumOfPerformance -> I suggest using instrumentation here, see e.g. https://www.dict.cc/deutsch-englisch/Besetzung+%5BMusikgruppe%5D.html or https://en.wikipedia.org/wiki/Instrumentation_(music)

[ChristophEwertowski]

Deployed to test, see http://test.lobid.org/resources/HT018857620.json.

[acka47]

+1