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

Add the second admissible range of the ORCID identifiers #146

Closed
jdvorak001 opened this issue May 26, 2023 · 0 comments · Fixed by #147
Closed

Add the second admissible range of the ORCID identifiers #146

jdvorak001 opened this issue May 26, 2023 · 0 comments · Fixed by #147
Labels

Comments

@jdvorak001
Copy link
Collaborator

jdvorak001 commented May 26, 2023

Quoting from the ORCID FAQ What is the relationship between ISNI and ORCID? (published 2023-02-22):

[...] ISNI reserved an initial block of identifiers for use by ORCID when we launched the ORCID registry in 2013. The first range of identifiers was defined between 0000-0001-5000-0007 and 0000-0003-5000-0001.

Fast forward to 2023. The ORCID registry has grown, now with over 16 million records, which means we required a new block of identifiers. This new range reserved for ORCID by ISNI is defined between 0009-0000-0000-0000 and 0009-0010-0000-0000.

We need to adapt the regular expressions that enforce these ranges.

ACz-UniBi added a commit that referenced this issue Jun 9, 2023
Add a second ORCID iD range, which is mentioned in #146 , Thank you @jdvorak001
jdvorak001 added a commit to jdvorak001/guidelines-cris-managers that referenced this issue Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant