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

Problem: It does not appear to be possible to delete an AIP via the API #1696

Open
5 tasks
helrond opened this issue Jun 4, 2024 · 6 comments
Open
5 tasks
Labels
API Issues relating to the Archivematica APIs, bugs/new endpoints, etc. triage-release-1.18 Type: feature New functionality.

Comments

@helrond
Copy link

helrond commented Jun 4, 2024

Please describe the problem you'd like to be solved
I could definitely be missing something here, but it does not appear to be possible to fully delete an AIP via the Storage Service API. I am able to create a request for deletion but it looks like a Storage Service admin still has to approve those requests using the Storage Service GUI. I am finding myself having to delete a large number of AIPs, and this process is both tedious and error-prone, as the possibility of clicking the wrong button seems high.

Describe the solution you'd like to see implemented
If it doesn't already exist, I'd love to have an API endpoint which replicates the functionality of the Package Delete Requests page and allows Storage Service administrators to approve or reject delete requests programatically.

Describe alternatives you've considered
Another alternative could be adding the ability to perform bulk actions in the Package Delete Requests page.

Additional context


For Artefactual use:

Before you close this issue, you must check off the following:

  • All pull requests related to this issue are properly linked
  • All pull requests related to this issue have been merged
  • A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
  • Documentation regarding this issue has been written and merged
  • Details about this issue have been added to the release notes
@replaceafill
Copy link
Member

You're not missing it. It doesn't exist. See #1662

@helrond
Copy link
Author

helrond commented Jun 5, 2024

Ah, should have spent a bit more time searching this repo first. Looks like this is well-documented elsewhere so does it make sense to just close this issue?

@sromkey
Copy link
Contributor

sromkey commented Jun 5, 2024

@helrond The initial issue was more of a question so we closed it, let's keep this one open.

@sromkey sromkey added Type: feature New functionality. API Issues relating to the Archivematica APIs, bugs/new endpoints, etc. labels Jun 5, 2024
@replaceafill
Copy link
Member

Related #1153

@replaceafill replaceafill added this to the 1.17.0 milestone Jun 5, 2024
@sromkey sromkey removed this from the 1.17.0 milestone Sep 25, 2024
@sromkey
Copy link
Contributor

sromkey commented Sep 25, 2024

We're close to a 1.17 release but hoping we can get to this in 1.18 instead!

@scollazo
Copy link

scollazo commented Feb 3, 2025

There is a storage service command that helps with this by using the command line in artefactual/archivematica-storage-service@b0f9ae3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Issues relating to the Archivematica APIs, bugs/new endpoints, etc. triage-release-1.18 Type: feature New functionality.
Projects
None yet
Development

No branches or pull requests

4 participants