Delete user dropboxes that have been published or rejected

[rija]

User story

As a curator
I want user dropboxes no longer needed to be deleted
So that the storage usage stay under control

Acceptance criteria

Given a manuscript has been accepted
When the datasets files are published And I marked the user dropbox for deletion Then the related user dropbox is deleted

Given a manuscript has been rejected
When the dataset files are not published And I marked the user dropbox for deletion Then the related user dropbox is deleted

Additional Info

suggestion of implementation: Curator marks any user dropbox no longer needed as to be deleted. A weekend automated job will delete any directory that's marked as such. To mark a user dropbox as archived, it's enough the rename the dropbox as <drop box name>.todelete e.g, on the bastion server:

$ cd /share/dropbox
$ mv user112 user112.todelete
$ mv user112.orig user112.orig.todelete

Product Backlog Item Ready Checklist

• [ ] Business value is clearly articulated
• [ ] Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
• [ ] Dependencies are identified and no external dependencies would block this item from being completed
• [ ] At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
• [ ] This item is estimated and small enough to comfortably be completed in one sprint
• [ ] Acceptance criteria are clear and testable
• [ ] Performance criteria, if any, are defined and testable
• [ ] The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

• [ ] Item(s) in increment pass all Acceptance Criteria
• [ ] Code is refactored to best practices and coding standards
• [ ] Documentation is updated as needed
• [ ] Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
• [ ] No deviation from the team technology stack and software architecture has been introduced
• [ ] The product is in a releasable state (i.e. the increment has not broken anything)

[rija]

This might be too soon, we should wait until the associated manuscript is published (which could be several weeks). This might be too soon, currently we wait 3 months incase the authors wish to resubmit a revised manuscript, or to refute the >editors decision to reject.

Hi @only1chunts ,

I've updated the acceptance criteria to make it clearer that you curators you are in control of what and when is to delete as per the suggested implementation.