Comment 2 for bug 1398076

This might involve a number of things, so it might be useful to talk about it, either here on the ticket or in chat. And you might prefer breaking it into multiple tickets.

I'm primarily interested in database size reduction. As such, one good first step might be, some Admin UI panels that show us the space consumed (various metrics) for different parts of the system. Presumably before we start on this project.

Some other notes:

- Any object in version history which is in a folder with the archived status is obvious for deletion

- Perhaps we need to bundle that operation into the "Archive to Box" operation

- If there is still a lot of space taken up in version history, we could discuss with Nat a policy for pruning, toss out revisions over 5 years old

- Doing this as an Admin UI is the best bet, as we can hand it over to Nat...unless of course these are very long running, in which case, monthly cron jobs