https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 --- Comment #5 from David Cook <dcook@prosentient.com.au> --- (In reply to Marcel de Rooy from comment #4)
Hmm. This *issue* will probably not come up often in a well defined workflow?
I think that relies on a number of assumptions. I've had complaints about this from multi-branch/multi-library users of Koha, but you could have the following scenario in a single branch: 1. Library technician transcribes book and sends it to cataloguer for subjects and classification and leaves the catalogue editor open 2. Librarian starts opens record on screen and does their work 3. Library technician notices a typo in the existing editor tab on their browser. Saves it and accidentally erases the librarian's work
But on the other hand it should not be that hard to lock it somehow. Only when would you unlock if the page was abandoned?
I don't think DBIx::Class is database lock friendly at all. In general, locking does seem difficult, as how would you know if a page was abandoned or some other related scenario. I suppose that's where session timeouts would come in, but that could also be problematic. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.