We recently ran into an issue where old transactions were uploaded from offline circ. This caused a BIG MESSS. Mistakes will happen. It would be great if there was a setting in Koha to limit the number of days old a file can be when uploaded.
Even better would be the ability to revert the operations completed by a .koc upload.
Or prevent duplicate files from being uploaded, period.
Perhaps a unique key should be included in the file, and Koha should keep track of these keys to show that it has been processed already.
The feature we brainstormed over (not at all a complete idea) was a feature rather like staged marc imports, but for KOC files. i.e. you upload a file, it is staged, you can see what's in it and what will happen when it is applied. You can apply the file to the catalogue, and also have the option to reverse the actions it has taken, with full accounting in the case of fines.
We had an incident this year, where the same .koc file was uploaded again, just three days after the first one. Unfortunately, this caused a bit of a mess in the 'old_issues' table. For example, I've spotted loans where the 'old_issues.returndate' (2023-12-08 10:23:49) seems to be time-travelling back before the 'issuedate' (2023-12-08 12:40:08). Is there a way to prevent multiple uploads of the same file?
Maybe the file simply needs to be updated after being uploaded with an indicator that it has been uploaded. Can't be uploaded again unless someone physically opens the file and changes the indicator manually?