Consider: slowing down the orphan processor

[swirtSJW]

User Story

There are times when there may be a data hiccup (a datadictionary gets modified...) and within a few cron runs the orphan processor has already removed the resources from the files. By the time the problem is noticed, there is no easy way to go back. Reverting a revision is not really an option.
It would be nice if the orphan removal did not take place so rapidly and put us in a position of data loss.

Detailed Feature Description

This could be achieved in a number of ways:

• Restrict the queue: The orphan removal queue only runs the first day of the month or every 10 days ...
• Restirct queue items: The processor does not process it and puts an item back in the queue if it is less than X days since it was added to the queue.
• Orphanage: Move orphans to a different location in the files directory where they can sit until the orphanage gets burned down every month or year. (this method would not make it as clean to revert a revision)
• ?

Problem and Motivation

Loss of data due to hiccups of one kind or another is bad. By the time we are alerted to a problem, it is too late and we only get lucky if there are ways for us to recover the file(s) that were removed.

Target Audience

• End Users
• Developers
• Administrators
• Other

Possible Implementation

See feature description.

Acceptance Criteria

Files don't get removed so quickly