search

gigascience / gigadb-website

Source code for running GigaDB
http://gigadb.org
GNU General Public License v3.0
9 stars 15 forks source link

Trigger asynchronous backup of the files when dataset is set to Published #2039

Open rija opened 1 month ago

rija commented 1 month ago

User Story

As a curator I want the dataset files I'm publishing to Wasabi to be also backed up to S3 Glacier So that I have piece of mind that any dataset files we publish has a backup available

Acceptance criteria

Given a dataset being curated has files associated with it When the dataset upload status is changed to "Published" Then a message is sent to trigger asynchronously the backup of all the files from EFS

Given a dataset being curated has files associated with it When the dataset upload status is changed to "Published" And a message is sent to trigger asynchronously the backup of all the files Then a prominent flag file "backup.in.progress" is written to the user dropbox being backed up

Given a dataset being curated has files associated with it When the backup of all the files in the user dropbox has been triggered And the backup has completed successfully Then the prominent flag file "backup.in.progress" is removed

Given a dataset being curated has files associated with it When the dataset upload status is changed to "Published" Then the author access to the user dropbox is removed

Given a dataset being curated has files associated with it When the dataset upload status is changed to "Published" And a message is sent to trigger asynchronously the backup of all the files Then a new entry is add to the Curation log announcing starting of backup process

Given a dataset being curated has files associated with it When the backup of all the files in the user dropbox has been triggered And the backup has completed successfully Then a new entry is add to the Curation log announcing success of backup process

Given a dataset being curated has files associated with it When the backup of all the files in the user dropbox has been triggered And the backup has failed Then a new entry is add to the Curation log announcing failure of backup process

sub-stories: