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

Import APIs don't work with DataCite test DOIs #8028

Closed
qqmyers opened this issue Jul 27, 2021 · 0 comments · Fixed by #8033
Closed

Import APIs don't work with DataCite test DOIs #8028

qqmyers opened this issue Jul 27, 2021 · 0 comments · Fixed by #8033
Assignees

Comments

@qqmyers
Copy link
Member

qqmyers commented Jul 27, 2021

Discovered during @kcondon's testing of #7504: The test in ImportDataCommand, which is intended to see if a DataCite DOI exists, always fails for test DataCite DOIs now (since their change from using the open 10.5072 test authority and requiring test accounts. As of that change, test DOIs are not indexed even when findable and thus URLs of the form https://doi.org/10.33564/FK27U7YBV always return 404.)
This affects the new migrate API in #7504 and should also affect the existing Dataverse APIs /api/dataverses/<id>/datasets/:import and /api/dataverses/<id>/datasets/:importddi APIs.

Since the intent of the test is just to verify that the DOI exists at DataCite, calling DOIDataCiteServiceBean.alreadyExists() for the DOI instead should work.

Note that this is a testing-only issue.

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

Successfully merging a pull request may close this issue.

2 participants