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
Describe the bug We've encountered an issue where users can submit incorrectly formatted ORCID. Specifically, the system currently accepts ORCIDs with more than 16 digits (e.g. “https://orcid.org/0000-0000-0001-9244-1708” rather than “https://orcid.org/0000-0001-9244-1708”)
To Reproduce Steps to reproduce the behavior:
Expected behavior The system should reject the ORCID with additional characters and display an error message indicating the correct format.
Additional context Malformed ORCIDs are not accepted by OSTI and cause issues for the publication and reservation of DOIs
The text was updated successfully, but these errors were encountered:
Validate orcids entered in the Editor
594caa4
- Add a new orcid validation method & associated tests Fixes issue #2553
@FiannaOBrien I have a fix for this in PR #2576. If you are able to test it out, please let me know if this solves your issue! Thanks :)
Sorry, something went wrong.
robyngit
Successfully merging a pull request may close this issue.
Describe the bug
We've encountered an issue where users can submit incorrectly formatted ORCID. Specifically, the system currently accepts ORCIDs with more than 16 digits (e.g. “https://orcid.org/0000-0000-0001-9244-1708” rather than “https://orcid.org/0000-0001-9244-1708”)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The system should reject the ORCID with additional characters and display an error message indicating the correct format.
Additional context
Malformed ORCIDs are not accepted by OSTI and cause issues for the publication and reservation of DOIs
The text was updated successfully, but these errors were encountered: