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

DataCite DOI: Investigate how to handle dataset Destroy. #2994

Closed
kcondon opened this issue Mar 3, 2016 · 4 comments
Closed

DataCite DOI: Investigate how to handle dataset Destroy. #2994

kcondon opened this issue Mar 3, 2016 · 4 comments
Assignees
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure" Type: Bug a defect

Comments

@kcondon
Copy link
Contributor

kcondon commented Mar 3, 2016

@posixeleni @sekmiller
Although destroy is a rarely used option it does happen. How should this be handled via DataCite? We currently do nothing special -the record remains active.

Eleni will check with DataCite to see if they have a recommended approach, Stephen will investigate the DataCite API to see whether there is something he can used to remove the record.

@kcondon kcondon added Priority: Medium Type: Bug a defect Component: Code Infrastructure formerly "Feature: Code Infrastructure" labels Mar 3, 2016
@kcondon kcondon added this to the 4.3 milestone Mar 3, 2016
@sekmiller
Copy link
Contributor

There's no way to delete an identifier via the API. I did add a method to delete the record from the api cache if a draft is deleted before publish.

@sekmiller
Copy link
Contributor

Added Code to delete row from cache in the case of delete prior to publish. Handling of destroy published dataset may be deferred as we have not heard from DataCite on the approach we should take. As noted above - there is no way to delete a published identifier - it can be set to "inactive"

@sekmiller
Copy link
Contributor

Still no response from Martin at DataCite.

@scolapasta scolapasta removed this from the 4.3 milestone Mar 16, 2016
@scolapasta scolapasta assigned posixeleni and unassigned sekmiller Mar 16, 2016
@kcondon
Copy link
Contributor Author

kcondon commented Apr 19, 2016

Closing since there is no real impact to user and will reopen if deemed important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure" Type: Bug a defect
Projects
None yet
Development

No branches or pull requests

5 participants