Feature #5872

Add ability to delete an aip from the storage service

Added by Justin Simpson over 8 years ago. Updated over 5 years ago.

Status:FeedbackStart date:10/25/2013
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Sponsored:No Requires documentation:
Pull Request:

Description

This features needs to be reviewed with an analyst before implementation.

Currently, the only way to delete an AIP is be initiating the process from the dashboard (this is by design). However, if there is a failure in the storeAIP microservice, it is possible for an AIP to get POSTed to the storage service, but not get indexed by the dashboard. In this case, it is not possible to delete the aip at all.

So there are two things to consider in this issue - if the storeAIP microservice fails, what should the storage service do? It probably should not accept the AIP. Secondly, there should be a way to delete aip's directly from the storage service (requires synchronizing with Elastic Search so the dashboard does not show outdated info, also probably requires an audit log entry of some kind).

History

#1 Updated by Justin Simpson over 8 years ago

  • Target version changed from 0.2.0 to 0.5.0

#2 Updated by Courtney Mumma over 8 years ago

Functionality should be as follows:

- AIPs posted to the SS and not indexed should be allowed to be deleted by the SS admin or the SS should get a signal that the AIP failed storage and was not indexed, then eliminate the post automatically (this might be more functionality than is currently possible right now)
- AIPs posted and stored/indexed successfully should be allowed to be deleted by the SS admin without a request from the dashboard user

#3 Updated by Holly Becker over 8 years ago

  • Status changed from New to QA/Review
  • Assignee changed from Holly Becker to Justin Simpson

Committed to storage service branch dev/issue-6008-polish

#4 Updated by Sarah Romkey over 7 years ago

  • Target version changed from 0.5.0 to 0.6.0

#5 Updated by Justin Simpson over 7 years ago

  • Status changed from QA/Review to Feedback
  • Target version changed from 0.6.0 to 0.8.0

Not all the functionality described in this ticket actually exists yet. We need to verify that the sponsored portion of this work is in fact done, and decide how to roadmap the rest.

#6 Updated by Justin Simpson about 7 years ago

  • Target version deleted (0.8.0)

#7 Updated by Justin Simpson over 5 years ago

  • Assignee deleted (Justin Simpson)

Also available in: Atom PDF