Open acka47 opened 4 years ago
That's a good idea too, but what we discussed was about abbreviatedNameForThe*
.
That's a good idea too, but what we discussed was about
abbreviatedNameForThe*
.
Yes, but we can already implement this as a generic property exists. For abbreviatedNameForThe*
I will first open an issue at DNB to add the generic property in the first place.
After looking at this, I now think https://github.com/hbz/lobid-gnd/issues/229, like this here, is actually about using the generic property (abbreviatedName there, temporaryName here), and filling it with values that in the DNB data are stored in the specific fields. Given that we have some unification with the DNB data on the horizon, and this has not been driven by a concrete user request, I think we should not invest the time to implement this right now.
Ok. Then we can close this issue for now?
Shouldn't we include temporaryName
, temporaryNameOfTheConferenceOrEvent
, temporaryNameOfTheCorporateBody
, temporaryNameOfThePlaceOrGeographicName
for reconciliation queries then? Or is this already the case. Doesn't seem so when looking at #228.
Yes, good catch! We only had temporaryName
(which isn't used in the data). Added the specific ones in https://github.com/hbz/lobid-gnd/commit/bd52135562e0c5a6a02fba259986fb7957e0eb60.
As discussed offline, we aim at the consistent approach for all name properties, i.e. using *Name
only and getting rid of specific versions like *NameOfTheCorporateBody
but will not implement this right now.
As with
preferredName
, we should only usetemporaryName
in lobid-gnd data for all these properties:temporaryName
,temporaryNameOfTheConferenceOrEvent
,temporaryNameOfTheCorporateBody
,temporaryNameOfThePlaceOrGeographicName
.