Bug 17507 - Can upload the same .koc file twice
Summary: Can upload the same .koc file twice
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-26 19:18 UTC by Christopher Brannon
Modified: 2024-01-17 21:13 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2016-10-26 19:18:06 UTC
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.
Comment 1 Liz Rea 2018-08-24 02:45:27 UTC
Even better would be the ability to revert the operations completed by a .koc upload.
Comment 2 Liz Rea 2018-08-28 01:46:57 UTC
Or prevent duplicate files from being uploaded, period.
Comment 3 Christopher Brannon 2018-08-28 16:26:34 UTC
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.
Comment 4 Liz Rea 2018-08-28 23:00:49 UTC
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.
Comment 5 Marie-Luce Laflamme 2024-01-17 17:37:34 UTC
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?
Comment 6 Christopher Brannon 2024-01-17 21:13:22 UTC
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?
Comment 7 Christopher Brannon 2024-01-17 21:13:30 UTC
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?