-
-
Save JeroenDeDauw/0e63b15a1522dab12fc1498020c1d11b to your computer and use it in GitHub Desktop.
{ | |
"fields": { | |
"P58": { | |
"label": "Person – preferred name", | |
"description": "GND data field for the preferred name of a person or a family", | |
"aliases": [ | |
"PICA+ 028A", | |
"PICA3 100", | |
"MARC 21 100" | |
], | |
"viewLink": "https://doku.wikibase.wiki/wiki/datafield?property=P58", | |
"editLink": "https://doku.wikibase.wiki/wiki/Property:P58", | |
"subfields": { | |
"P41": { | |
"label": "Personal name", | |
"occurrence": false, | |
"description": "Hinweis zur Erfassung von Personen, die nur unter einem Nachnamen bekannt sind" | |
}, | |
"P21": { | |
"label": "Surname", | |
"occurrence": false | |
} | |
}, | |
"codings": { | |
"PICA+": { | |
"fieldName": "028A" | |
}, | |
"PICA3": { | |
"fieldName": "100" | |
}, | |
"MARC 21": { | |
"fieldName": "100" | |
} | |
}, | |
"rulesOfUse": { | |
}, | |
"examples": { | |
"Q626": { | |
"label": "Sarah Hartmann" | |
} | |
} | |
}, | |
"P150": { | |
"label": "Identification number" | |
} | |
} | |
} |
tbauer2811
commented
Sep 29, 2021
- instead of "fields" I would suggest "gndfields"
- instead of "subfields" I would suggest "gndsubfields"
we can work on the JSON draft from here, can you give me write access here?
I cannot give write access on a gist. So instead I copied what was here into a file in the "GND repo", which holds the MediaWiki extension we developed for you. Here is the file: https://github.com/ProfessionalWiki/GND/blob/master/gnd-doku.json. You should have an invitation to get access to the repo.
* instead of "fields" I would suggest "gndfields" * instead of "subfields" I would suggest "gndsubfields"
That is your call, but I'd not do this, since the whole JSON already is GND specific and is returned by a GND specific API. In other words, there will never be non-GND stuff in there so that the subfields are GND subfields should be clear from the context.
* instead of "fields" I would suggest "gndfields" * instead of "subfields" I would suggest "gndsubfields"
That is your call, but I'd not do this, since the whole JSON already is GND specific and is returned by a GND specific API. In other words, there will never be non-GND stuff in there so that the subfields are GND subfields should be clear from the context.
Okay makes sense, I agree with you.