We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In some cases VIAF doesn't return a GND-IDN, but a PICA-PPN instead. (This is often the case, if the GND-IDN contains a dash.)
E.g. looking for "Schlesinger'sche Buchhandlung" returns 991407407, which cannot be found. If you check the full VIAF dataset '(http://www.viaf.org/viaf/138248454/viaf.json) it returns the full GND URI (http://d-nb.info/gnd/10364445-3).
991407407
And in this particular case this is redirected to a dataset with the latest IDN: 1073054446.
1073054446
Can't think of an easy solution for this …
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
In some cases VIAF doesn't return a GND-IDN, but a PICA-PPN instead. (This is often the case, if the GND-IDN contains a dash.)
E.g. looking for "Schlesinger'sche Buchhandlung" returns
991407407
, which cannot be found.If you check the full VIAF dataset '(http://www.viaf.org/viaf/138248454/viaf.json) it returns the full GND URI (http://d-nb.info/gnd/10364445-3).
And in this particular case this is redirected to a dataset with the latest IDN:
1073054446
.Can't think of an easy solution for this …
The text was updated successfully, but these errors were encountered: