[Bug 22259] New: If two catalogers work on same record, one overwrites the other
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 Bug ID: 22259 Summary: If two catalogers work on same record, one overwrites the other Change sponsored?: --- Product: Koha Version: 18.05 Hardware: Other OS: Windows Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs@lists.koha-community.org Reporter: karin.hochschein@linklaters.com QA Contact: testopia@bugs.koha-community.org CC: m.de.rooy@rijksmuseum.nl Target Milestone: --- If 2 librarians edit the same cataloguing record at the same time, the last one to save overwrites the work of the other. There is not way to block the catalogue record for other cataloguers in your library. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #1 from David Cook <dcook@prosentient.com.au> --- I raised this issue many years ago but I don't think there was any interest in fixing it. My original idea was to implement row locking in the database. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |All Version|18.05 |master CC| |katrin.fischer@bsz-bw.de OS|Windows |All --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to David Cook from comment #1)
I raised this issue many years ago but I don't think there was any interest in fixing it.
I think the problem is not interest, we can easily agree that this is not a good situation. But it will also need funding and agreeing on the right method in order to be able to fix it. I think it's good the problem is on bugzilla now, thx Karin! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 Josef Moravec <josef.moravec@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |josef.moravec@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 --- Comment #3 from David Cook <dcook@prosentient.com.au> --- (In reply to Katrin Fischer from comment #2)
But it will also need funding and agreeing on the right method in order to be able to fix it.
This is the part where my optimism fails.
I think it's good the problem is on bugzilla now, thx Karin!
This is true. I'm actually surprised there aren't any Bugzilla issues about this already. Maybe Robin talked me down from posting it years ago... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 --- Comment #4 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Hmm. This *issue* will probably not come up often in a well defined workflow? 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? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 Josef Moravec <josef.moravec@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |black23@gmail.com -- You are receiving this mail because: You are watching all bug changes.
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.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 --- Comment #6 from Alex Arnaud <alex.arnaud@biblibre.com> --- Created attachment 90378 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=90378&action=edit Bug 22249: Mana - Move comment process in a dedicated sub -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 Alex Arnaud <alex.arnaud@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex.arnaud@biblibre.com Attachment #90378|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22259 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- *** This bug has been marked as a duplicate of bug 23705 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org