-
Notifications
You must be signed in to change notification settings - Fork 1
List subjects without GND ID in subject array #23
Comments
Very similar to #17 which deals with persons without GND ID [edit: and also https://github.com/hbz/lobid/issues/302 which deals with corporate bodies]. Adjusted the title and description to cover subjects. |
We must use the same generic property for the label as we do for the other subject, currently this is {
"@context":"http://lobid.org/download/contextTmp.json",
"@id":"http://lobid.org/resources/TT002234459#!",
"subject":[
{
"@id":"http://d-nb.info/gnd/4114067-9",
"preferredName":"Jakobsweg",
"preferredNameForThePlaceOrGeographicName":"Jakobsweg"
},
{
"@id":"http://d-nb.info/gnd/4049787-2",
"preferredName":"Rhein-Lahn-Kreis",
"preferredNameForThePlaceOrGeographicName":"Rhein-Lahn-Kreis"
},
{
"@id":"http://dewey.info/class/914/"
},
{
"preferredName":"Karte"
}
],
"subjectOrder":[
"http://d-nb.info/gnd/4049787-2, http://d-nb.info/gnd/4114067-9, Karte"
]
} |
It might make sense to add the type |
@dr0i When you start working on API 2.0 issues, remember that I created some example files, see hbz/lobid-resources#79 (comment). |
What shall I do with these - seems to be a whole other issue, no? |
Deployed small test set to staging, see e.g. http://staging.lobid.org/resources/TT002234459. |
+1 looks good, e.g. http://staging.lobid.org/resources/BT000128754. The example you link to (http://staging.lobid.org/resources/TT002234459) reminds me that we should consider removing those subject strings from the subject array that we use for type/medium information (i.e. the "Formschlagwörter" like "Karte" and "Aufsatzsammlung"). See also hbz/lobid#54. |
Don't know why this was opened again. Closing. |
As far as I can see, subjects without GND ID are currently not listed as object without
@id
(i..e. blank node) in thesubject
array. This probably would make sense for querying etc.(Just sitting in the DINI AG KIM Titeldaten meeting where this is discussed.)
The text was updated successfully, but these errors were encountered: