Skip to content
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

dojson: handle obsolete ORCIDs #11

Open
jacquerie opened this issue Jun 28, 2017 · 3 comments
Open

dojson: handle obsolete ORCIDs #11

jacquerie opened this issue Jun 28, 2017 · 3 comments
Assignees

Comments

@jacquerie
Copy link
Contributor

From @annetteholtkamp on March 24, 2017 9:15

In rare cases an author may have 2 Orcid's. Although we'll try to get these cases solved on the Orccid side we should be prepared to deal with them. Currently they are put into 035__z. In the new schema Orcid's should be unique. A second Orcid should be automatically hidden.

Copied from original issue: inspirehep/inspire-next#2129

@jacquerie
Copy link
Contributor Author

Two interesting cases: https://inspirehep.net/record/1518989/export/xme and https://inspirehep.net/record/1005548/export/xme (both orderings appear in the data)

@jacquerie
Copy link
Contributor Author

Another interesting case: https://inspirehep.net/record/1357501/export/xme (they also appear in the same field).

@jacquerie jacquerie self-assigned this Aug 6, 2017
@jacquerie jacquerie changed the title dojson: obsolete Orcid's dojson: handle obsolete ORCIDs Oct 7, 2017
@michamos
Copy link
Contributor

michamos commented Nov 6, 2017

This probably requires something similar to #33.

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

No branches or pull requests

2 participants