Open sallain opened 1 week ago
As a first iteration of this feature, the team agreed that we would implement the following:
Pending
) for AIPs where a deletion request has been madeDeleted
) for AIPs that have been successfully deletedThe first iteration does not need to include:
@scollazo has confirmed the following:
Is your feature request related to a problem? Please describe.
Once an AIP has been created, there is no way to delete it through Enduro. It is possible to delete the AIP in Archivematica or the Storage Service, but this means that 1) users have to leave Enduro, and 2) the deletion is not reflected in Enduro.
Describe the solution you'd like
While viewing a single AIP in Enduro, a user with sufficient permission should be given the option to delete the AIP through a UI button.
Similar to Archivematica, deletion should be a two-step process:
Once the deletion request is approved, a API call should be sent to the Storage Service to delete the AIP. The Storage Service should be set to auto-approve deletion requests, so that the user doesn't need to repeat the deletion approval there. Enduro should then receive a confirmation that the package has been deleted (NOTE: based on the current SS API, this may require Enduro to poll the Storage Service for the package's status).
Throughout this workflow, all actions - deletion request, deletion approval/denial, deletion confirmation - should be recorded in an audit log that persists indefinitely (or as long as the user needs it to).
See Miro for the full proposed workflow, including status updates for the package.
Describe alternatives you've considered
We've gone through many iterations of this workflow, but this seems to be the simplest flow without compromising auditability of the deletion action.
Additional context
Copy of the Miro diagram as of 22 November 2024.