http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8991
David Cook <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #20 from David Cook <[email protected]> --- I agree with Galen and Katrin. I don't think that many libraries would find this script useful. In fact, from a regulatory financial perspective, it could be extremely problematic. Libraries aren't always known for keeping the best accounting records, so acquisitions data is often the only record. If it disappears, there could be trouble as one of the key components of the audit trail vanishes. >From an archival/records management perspective, it doesn't make sense to erase these records. These data are records. If they aren't 'active' or relevant anymore, they should be exported into some type of "semi-active" or "inactive" state. As Galen suggests, an output of the purge should be kept. Going back to the regulatory perspective, when the time comes to officially dispose of the records, the archived output can be deleted. I think that probably makes the most sense. Of course, I might be biased, as I'm the one saying it :p. I could maybe see this being set up as a cronjob on an instance by instance basis, but definitely not setup as a default cronjob. I imagine there would be quite a few furious acquisitions librarians otherwise. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
