-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use generic temporaryName property instead of specific ones #227
Comments
That's a good idea too, but what we discussed was about |
Yes, but we can already implement this as a generic property exists. For |
After looking at this, I now think #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 |
Yes, good catch! We only had |
As discussed offline, we aim at the consistent approach for all name properties, i.e. using |
As with
preferredName
, we should only usetemporaryName
in lobid-gnd data for all these properties:temporaryName
,temporaryNameOfTheConferenceOrEvent
,temporaryNameOfTheCorporateBody
,temporaryNameOfThePlaceOrGeographicName
.The text was updated successfully, but these errors were encountered: