DataCite reRegsiter: fix handling when DOI doesn't exist at DataCite#12171
Open
qqmyers wants to merge 1 commit intoIQSS:developfrom
Open
Conversation
scolapasta
approved these changes
Feb 19, 2026
github-project-automation
bot
moved this from Ready for Triage
to Ready for QA ⏩
in IQSS Dataverse Project
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it: As recently seen at Harvard, the reRegisterMethod, which checks with DataCite to see if a DOI's metadata/url need to be updated and only making the update calls if needed, isn't handling the case when the DOI doesn't exist/hasn't been registered. This PR adds the appropriate try/catch logic to handle the case when a non 200 response is received, which allows the reRegister call to just register the DOI in this case.
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: