Use lv properties instead of dc elements for lists of alternate labels

[acka47]

Requested by @jschnasse . Listing several labels of one contributor/creator or subject under dc:contributor/dc:creator/dc:subject seems wrong as it leaves the impressions of having more contributors/creators than there actually are. We should rather use properties from our local lobid vocab namespace. As this is only intended to be an interims solution, we could just use properties without defining them in the vocab as we already do with contributingCorporateBodyLabel.

[acka47]

To do:

• [x] Adjust morph
• [x] Adjust context file
• [ ] OPTIONAL Add properties to lobid vocab

[acka47]

The morph has to be updated like this:

• [x] Replace all occurences of http://purl.org/dc/elements/1.1/contributor by http://purl.org/lobid/lv#contributorLabel
• [x] Replace http://purl.org/dc/elements/1.1/subject by http://purl.org/lobid/lv#subjectLabel

[acka47]

After running the morph, the JSON-LD context has to be updated like this:

• [x] Replace "contributorLabel": "http://purl.org/dc/elements/1.1/contributor" by "contributorLabel": "http://purl.org/lobid/lv#contributorLabel"
• [x] Replace "subjectLabel": "http://purl.org/dc/elements/1.1/subject" by "subjectLabel": "http://purl.org/lobid/lv#subjectLabel"

[acka47]

@dr0i, what do you think: Should I update the morph myself according to https://github.com/hbz/lobid/issues/169#issuecomment-113487704?

[dr0i]

Just give it a try. Put in in an branch of its own, as normal. I will review it.

[dr0i]

Deployed to testing.

[dr0i]

Deployed to production, closing.

[jschnasse]

thx! Looks nice so far.

[dr0i]

We forgot to update the API as well, thus leading to hbz/nwbib#117.

[dr0i]

Reclosing due to resolving hbz/nwbib#117.