Overwrite Compressed File

Problem/Motivation

Archives are generated from files uploaded to entity and serve as either a backup or a convenient way to download them all. It is likely, there is no need to save version (revisions) of a file generated from other files already tracked in revisions. Archives tend to be large and consume a lot of space on filesystem.

Proposed resolution

I would very much appreciate ability to have only one archive on filesystem. The archive file would get overwritten upon update instead of generating a new one.

Remaining tasks

User interface changes

Add checkbox "Overwrite archive file upon update instead of generating a new file."

API changes

Data model changes