Comment 4 for bug 1858448

Thinking about this a bit more, sites that age circulations very soon after completion (e.g. after 7 days) likely don't want the money data to be aged that quickly, regardless of whether all of the data is tracked. Once it's aged, it becomes read-only and more difficult to access from the interface. 7 days is just too quick for that to take effect.

The aging process assumes you are essentially done with the data. So, while I think adding the columns is a needed improvement, I'm going to start by decoupling the money aging from the circulation aging.

So I propose a combination of Jason's option 2 and 3. Add a flag to enable money aging concurrent with circulation aging (requires opt-in) and provide a way to age money data manually via SQL function and srfsh script.

The setting will be documented with a caveat re: data loss pending future development.