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

Handle entries without preferredName #139

Closed
fsteeg opened this Issue Jul 5, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@fsteeg
Contributor

fsteeg commented Jul 5, 2018

They can't be opened from the result list:

http://lobid.org/gnd/search?q=NOT+_exists_%3ApreferredName

And yield errors when opened directly:

http://lobid.org/gnd/1085995054

@fsteeg fsteeg added bug ready labels Jul 5, 2018

@fsteeg fsteeg self-assigned this Jul 5, 2018

@fsteeg fsteeg added working and removed ready labels Jul 11, 2018

fsteeg added a commit that referenced this issue Jul 11, 2018

@dr0i dr0i added review and removed working labels Jul 11, 2018

@fsteeg

This comment has been minimized.

Contributor

fsteeg commented Jul 11, 2018

Deployed to test:

http://test.lobid.org/gnd/search?q=NOT+_exists_%3ApreferredName
http://test.lobid.org/gnd/1085995054

We should probably also report this as an issue in the GND RDF conversion, e.g. http://d-nb.info/gnd/1085995054 has content in 110 b which should probably end up in preferredName.

@fsteeg fsteeg assigned acka47 and unassigned fsteeg Jul 11, 2018

@acka47

This comment has been minimized.

Contributor

acka47 commented Jul 11, 2018

+1

We should probably also report this as an issue in the GND RDF conversion, e.g. http://d-nb.info/gnd/1085995054 has content in 110 b which should probably end up in preferredName.

As soon as this is deployed I will make an issue regarding all of these. It looks to me as they all have their problems...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment