Add links to work entities for RDA records #784
Comments
acka47
changed the title
I mean an update of the file you provided in hbz/lobid#161 (comment). |
|
Created an updated list (see hbz/lobid#161 (comment)). |
|
As far as I can see, the data for work is manifested is in field 303. Most of the work titles don't seem to have a link to GND, e.g. HT018848722: <datafield tag="303" ind1="-" ind2="1">
<subfield code="p">Frank, Dietmar</subfield>
<subfield code="t">Traumland Nepal <eng></subfield>
</datafield>HT018847832 is an example for a work title with GND URI. Source (snippet): <datafield tag="303" ind1="-" ind2="1">
<subfield code="p">Dharmasenagaṅi Mahattara</subfield>
<subfield code="d">ca. 7. Jh.</subfield>
<subfield code="t">Vasudevahiṃdī-majjhima-khaṃda</subfield>
<subfield code="9">(DE-588)4792592-9</subfield>
</datafield> |
|
Further examples:
<datafield tag="303" ind1="-" ind2="1">
<subfield code="t"><<The>> killers</subfield>
<subfield code="h">Film</subfield>
<subfield code="f">1946</subfield>
</datafield> |
|
HT018853619 is also interesting, using subfields <datafield tag="303" ind1="-" ind2="1">
<subfield code="p">Mahler, Gustav</subfield>
<subfield code="d">1860-1911</subfield>
<subfield code="t">Lieder</subfield>
<subfield code="m">Singst.</subfield>
<subfield code="m">Orch</subfield>
<subfield code="f">1905</subfield>
<subfield code="u">Ich bin der Welt abhanden gekommen</subfield>
<subfield code="9">(DE-588)300097921</subfield>
<subfield code="z">Arr.</subfield>
</datafield> |
|
I got the cataloging help for field 303 from our colleague Stephanie: |
acka47
changed the title
|
I transformed most of the examples to ttl (the "Zupforchester" example I omitted because of redundancy to the example before). When possible I used the properties of the context.json. Especially difficult to express was the circumstance that a musical work needs a special "Besetzung" (last example). |
|
Going through the examples, I realize that I obviously haven't been clear on what we are trying to achieve with this issue. The central thing is that both we and the Titeldaten working group want to replace the current approach (adding Einheitssachtitel as dct:alternativeTitle) by another approach that enables putting more information (like URI of the work etc.) on the described work. At https://wiki.dnb.de/display/DINIAGKIM/Modellierung+Werk we collected possible approaches. What we have to do know is think about chosing an approach for lobid that covers the different use cases. I think, what is most important to retain in the RDF are the actual title string and the workd ID if existing. |
|
Here is how the first two examples could look like: {
"@context":{
"id":"@id",
"title":"http://purl.org/dc/terms/title",
"exampleOfWork":"http://schema.org/exampleOfWork"
},
"id":"http://lobid.org/resources/HT018848722#!",
"exampleOfWork":{
"title":"Traumland Nepal <eng>"
}
}{
"@context":{
"id":"@id",
"title":"http://purl.org/dc/terms/title",
"exampleOfWork":"http://schema.org/exampleOfWork"
},
"id":"http://lobid.org/resources/HT018848722#!",
"exampleOfWork":{
"id":"http://d-nb.info/gnd/4792592-9",
"title":"Vasudevahiṃdī-majjhima-khaṃda"
}
} |
|
There are some questions to be considered:
|
|
|
Also I don't know how many works are without an id of some sort.
|
|
For many Partituren the instrument is already named in the title (see search). If not there are multiple subjects which could fit but it's cumbersome to select the fitting. Looked for "Sopran" as a subject keyword in the KVK. It's differently handled dependent on which catalog you choose. At the moment you don't really know where to look for instrumentation. It's in many fields and sometimes only in the Aleph data. Some resources have the MAB field filled out, some not. I would approve taking instrumentation into the resources. But also simply searching by URL would be a great improvement. I will get in touch with some colleagues of mine and ask them if they ever searched for instrumentation or rather what they searched for in the specific course at the university. |
|
When implementing something we will also have to adjust the transformation of field 304 "Einheitssachtitel" which is currently mapped to dct:alternative, see current morph line 546. |
|
Some of this is handled in hbz/lobid-resources#516. |
|
As hbz/lobid-resources#567 is resolved this issue is ready to be worked on. |
|
Work entities with GND-id are covered by hbz/lobid-resources#567. But there are some which don't have an id like: HT018848722 (see MAB 303). |
HT018848722: Resource without MAB 303-1.9 but with MAB 303-1.t See lobid/lodmill#784
HT018848736: Has also living statistics which HT018848722 has not. HT018853619: Has subfield u. See lobid/lodmill#784
Also replace spaces with tabs at "provenance" to make it more readable. See lobid/lodmill#784
Also replace blanks with tabs. See lobid/lodmill#784
|
Changes deployed to test. See HT018848722 (production, json) / HT018848722 (test, json) for the original example (person without living statistics and title of work), HT018848736 (production, json) / HT018848736 (test, json) (person with living statistics) and HT018853619 (production, json) / HT018853619 (test, json) (title with subtitle, occupation and person with living statistics; the same as in GND). |
|
Very good. +1 |
Sub-issue of hbz/lobid#161.
See https://wiki.dnb.de/display/DINIAGKIM/Modellierung+Werk. First, I will have to look for example entries in the hbz01 data. Then we will have to implement this.
@dr0i Can you please create a new file with the RDA entries from hbz01? It isn't urgent, though...
The text was updated successfully, but these errors were encountered: