Bug #9875

Deletion requests/deletions made through API do not update Archival Storage tab

Added by Sarah Romkey over 5 years ago. Updated over 4 years ago.

Status:NewStart date:05/20/2016
Priority:LowDue date:
Assignee:-% Done:

0%

Category:AIP Management
Target version:-
Google Code Legacy ID: Pull Request:
Sponsored:No Requires documentation:

Description

To reproduce:

1. Initiate a deletion request through the API, using a curl command or this bash script: https://gist.github.com/jhsimpson/14778f0c81edbf2cea0a14f589ff96a2#file-delete_aip-sh

2. Complete the deletion request through Storage Service interface

Result: Archival Storage tab is not updated with new AIP status- it remains listed as "Stored"

Desired result: Archival Storage tab should list AIP as "Deletion requested" after the command/script is run, and then removed from the list of AIPs after the deletion is completed in the Storage Service.

History

#2 Updated by Sarah Romkey about 5 years ago

  • Subject changed from Deletion requests/deletions made through API do not update Archival Storage tab to Deletion requests/deletions do not update Archival Storage tab

Updated the title to accurately reflect that this bug is present regardless of how the deletion request is made- either through the API or through the user interface.

#3 Updated by Sarah Romkey about 5 years ago

  • Subject changed from Deletion requests/deletions do not update Archival Storage tab to Deletion requests/deletions made through API do not update Archival Storage tab

Changing title back, this is working through the UI in 1.6.

#4 Updated by Nick Wilkinson about 5 years ago

  • Target version changed from Release 1.6 to Release 1.7.0

#5 Updated by Sarah Romkey almost 5 years ago

  • Assignee set to Nick Wilkinson

Nick, could you please assign to a developer?

#6 Updated by Nick Wilkinson almost 5 years ago

  • Assignee deleted (Nick Wilkinson)

#7 Updated by Nick Wilkinson over 4 years ago

  • Assignee set to José Raddaoui Marín

#8 Updated by José Raddaoui Marín over 4 years ago

  • Assignee changed from José Raddaoui Marín to Justin Simpson

Hi Justin,

There is more info about the issue in this update. I discussed this with Jesús and we’ve found some different solutions:

1) crontab: new djando command added to dashboard that it’s triggered by crontab periodically to fetch data from SS and update the ES index. Simple setup and implementation.
2) django-celery: complex, specific to SS, python-oriented, rigid, risky.
3) archivematica-search: we could start with a small tool that acts as a gearman worker and updates the search index asynchronously. the solution could be extended in the future to add more business logic related to searches, e.g. indexing, mapping, indice management, etc…
4) AM endpoint: request from the SS to AM each time an AIP is deleted (or requested deletion). Hard to achieve consistency in case of errors (DB or ES removal), adds to technical debt.

I'd like to know your thoughts and how much time do we have for this task.

#9 Updated by Nick Wilkinson over 4 years ago

  • Assignee deleted (Justin Simpson)
  • Priority changed from Medium to Low
  • Target version deleted (Release 1.7.0)

Not a priority for the 1.7 release -- this is a wishlist item.

This could be accomplished with sponsored development.

Also available in: Atom PDF