-
Notifications
You must be signed in to change notification settings - Fork 493
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
Implement ability to reserve DOIs through DataCite #5093
Comments
This could be a better approach than using multiple providers as we had planned first in #4833 and #5082. Private drafts seem to be a proper fit for our use case, even so they won't be resolvable until "registered". (Scientist could share a Dataverse installation URL instead for collaboration...) Do you guys think this is a good topic for a community contribution? |
(That was a quick and comprehensive answer, @pdurbin 😉 ) |
@poikilotherm heh. Thanks for chatting at http://irclog.iq.harvard.edu/dataverse/2018-10-10 As I mentioned there @sekmiller and I talked about it and we don't think the refactoring he's working on for #5060 will conflict. We are, of course, available to answer any questions. Thanks for linking to https://support.datacite.org/docs/doi-states which explains the new feature, listing three states:
We're pretty sure that we'd want DOIs to go straight from "draft" to "findable" so that they're indexed in DataCite Search. |
To be more complete, I should mention that these states are not usable via the XML based MDS API, but via the REST API and EZID API. This could be a big blocker, because that means changing the whole code of As it seems that @sekmiller wrote huge parts of the class: any ideas how to tackle this? |
@poikilotherm as promised, I mentioned this issue at standup. Thanks for linking to https://support.datacite.org/docs/doi-states#section-doi-states-outside-of-fabrica which gives details on your assertion that we can't use the old DataCite API for this: The vibe I got from @scolapasta and @sekmiller is that we certainly wouldn't mind if you poke around with the new DataCite API and report back any interesting findings! |
@poikilotherm hi! Are you actively working on this? Do you still want to be assigned to it? |
No I am currently concentrating on "getting things testable". |
Status update: we still will need this down the road, but concentrate on getting things moving to production currently. |
|
The fix required removing the throwing of RuntimeException in DataCiteRESTfullClient. This is considered a system exception and rolls back the entire "create dataset" command and transaction. This commit also remove the temporary fix I had put in to allow datasets to be created when DataCite is down: 9cbd5d3 Basically, it's a better fix. We need the create time to be null if DataCite is down so that we can query for unreserved DOIs and then reserve them.
Conflicts: src/main/java/propertyFiles/Bundle.properties
ability to reserve DOIs through DataCite #5093
Datacite has added the ability to reserve DOIs pre publish (as EZID did). This ticket will track adding the ability to reserve those DOIs when we create datasets, as well as a one time ability to reserve DOIs for existing drafts that have only reserved their DOIs on the dataverse side.
The text was updated successfully, but these errors were encountered: