Expanded tarballs retention policy - proposed changes

[ndokos]

During extended discussions, we came up with a proposed change in the retention policy of expanded tarballs. The current policy is to expand every tarball submitted to the server and keep it for ever. Although there are proposals for various phases of the project, I will try to describe here the proposal for the first phase only. N.B. this concerns only the expanded tarballs: the compressed tarball is kept "for ever" and backed up, so if something goes wrong, we still have all the data.

The proposed policy is as follows:

• When a result is submitted, the tarball is expanded with a default retention period set to one month.
• The retention period can be reset by the user to a shorter or longer period, or to make the expansion permanent (e.g. if there are documents that refer to such results).
• It will be possible to reexpand a tarball after its retention period has expired and it has been cleaned up. It will then be kept for another retention period (default or otherwise).

Questions, comments, additions, deletions, constructive criticism or snide remarks are all welcome.

[ashishkamra]

Couple of more related dashboard UI requirements:

1. A view on the dashboard where a user can view all the tarballs uploaded by him/her.
2. A user should be able to select a run (or multiple runs) on the dashboard and change the retention period.