-
Notifications
You must be signed in to change notification settings - Fork 500
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
Feature Request/Idea: Allow the Deletion of Auxiliary Files via API #8235
Comments
FYI: I've implemented this in the QDR fork and it should mostly be a matter of making a PR. |
pdurbin
added a commit
to QualitativeDataRepository/dataverse
that referenced
this issue
Nov 16, 2021
Conflicts (from PR IQSS#8192 it seems): src/main/java/edu/harvard/iq/dataverse/api/Access.java
pdurbin
added a commit
to QualitativeDataRepository/dataverse
that referenced
this issue
Nov 16, 2021
pdurbin
pushed a commit
to QualitativeDataRepository/dataverse
that referenced
this issue
Nov 16, 2021
pdurbin
added a commit
to QualitativeDataRepository/dataverse
that referenced
this issue
Nov 16, 2021
pdurbin
added a commit
to QualitativeDataRepository/dataverse
that referenced
this issue
Nov 16, 2021
pdurbin
added a commit
to QualitativeDataRepository/dataverse
that referenced
this issue
Nov 22, 2021
pdurbin
added a commit
to QualitativeDataRepository/dataverse
that referenced
this issue
Nov 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview of the Feature Request
Currently the Dataverse API includes endpoints to add or download Auxiliary Files as described in the documentation: https://guides.dataverse.org/en/latest/developers/aux-file-support.html
However, there is no way to delete an auxiliary file that is accidentally or incorrectly added. Please add an API endpoint to remove an existing auxiliary file.
What kind of user is the feature intended for?
An API User who has permissions to add auxiliary files
What inspired the request?
Testing with a Dataverse-integrated application prompted the request after duplicate auxiliary files were added as well as an incorrectly formatted auxiliary files. As these are auxiliary files we did not consider them falling under the same category as regular data files--which would need to be formally de-accessioned.
The text was updated successfully, but these errors were encountered: