-
Notifications
You must be signed in to change notification settings - Fork 1
Add @type to GND entities #25
Comments
We shouldn't use the URIs but alias them in the |
@dr0i asked offline how to identify in the MAB source that a GND entry is of type "Family". Let's have a look at some example files with GND families: <datafield tag="902" ind1="-" ind2="1">
<subfield code="p">Dorhoff</subfield>
<subfield code="c">Familie</subfield>
<subfield code="9">(DE-588)102851445X</subfield>
</datafield> <datafield tag="902" ind1="-" ind2="1">
<subfield code="p">Heinsberg, von</subfield>
<subfield code="c">Familie</subfield>
<subfield code="9">(DE-588)189407115</subfield>
</datafield> <datafield tag="902" ind1="-" ind2="1">
<subfield code="p">Wittgenstein</subfield>
<subfield code="c">Familie</subfield>
<subfield code="d">ca. 19./20. Jh.</subfield>
<subfield code="9">(DE-588)118769618</subfield>
</datafield> I had a look at several more examples. It looks like the GND references of type "Family" are identified by the string "Familie" in subfield c. |
- add ConferenceOrEvent as rdf:type See hbz/lobid-rdf-to-json#25.
- add nameOfCreatingCorporateBodyG - add gnd#Person See hbz/lobid-rdf-to-json#25.
If an ID is |
@acka47 odd - couldn't find a |
@dr0i for example http://lobid.org/resources/HT014376582 or http://lobid.org/resources/HT019035373 (with hbz as subject). |
- add nameOfCreatingCorporateBodyG - add gnd#Person See hbz/lobid-rdf-to-json#25.
- add "sameEntity" option to metamorph rule "choose" See hbz/lobid-rdf-to-json#25.
Deployed test set, see e.g. http://staging.lobid.org/resources/HT018612706#!. |
Something strange happened to the "subject":[
{
},
{
"dateOfBirth":"1921",
"dateOfDeath":"1995",
"id":"http://d-nb.info/gnd/11855087X",
"preferredName":"Highsmith, Patricia",
"preferredNameForThePerson":"Highsmith, Patricia",
"type":[
"http://d-nb.info/standards/elementset/gnd#Person"
]
}
] Seems to be a problem in many resources, e.g. 8 occurences of |
+1 |
In API 1.0 we had some reason not to include the type of a linked GND resource. With API 2.0 we can do this. Example:
When we have the type, we could probably leave out the specific
preferredNameForThe...
properties. (As soon as we add variant names we should do so anyways to not inflate the documents to much.) I will make another issue for this.The text was updated successfully, but these errors were encountered: