Bug 4373 - Placing and processing items simultaneously causes multiple issues
Summary: Placing and processing items simultaneously causes multiple issues
Status: RESOLVED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: PC All
: P2 normal (vote)
Assignee: Galen Charlton
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-05 07:18 UTC by Liz Rea
Modified: 2023-06-22 18:40 UTC (History)
8 users (show)

See Also:
Change sponsored?: Seeking cosponsors
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 Chris Cormack 2010-05-21 01:26:24 UTC


---- Reported by wizzyrea@gmail.com 2010-04-05 19:18:54 ----

Since we added seven libraries to our consortium, we have noticed an increase in ‘strange holds behavior‘ such as one patron receiving two copies of book or movie, when only one of the two items will actually fulfill the patron’s hold.  The more we thought about this, the more we realized that it was an issue of timing: Koha seems to be mishandling simultaneous submissions of data.  For example two libraries processing their Pick list at the same time or two libraries checking in items or placing holds at the same time.  

This five-minute video http://www.screencast.com/users/lizrea/folders/Jing/media/16ea23e8-e3e9-42cb-a98c-79d17a8df438 shows a number of problems that can occur when items are picked, holds are placed and transfers are initiated at about the same time on different copies of the same item.

This three-minute video http://www.screencast.com/users/lizrea/folders/Jing/media/de71880c-df72-4313-a284-84bed693c042 shows what happens when you receive an item routed to you to fill a ‘phantom’ hold.

Bugs that may be related to this:
4201



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:26 UTC  ---

This bug was previously known as _bug_ 4373 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4373

Actual time not defined. Setting to 0.0
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
CC member jwagner@ptfs.com does not have an account here

Comment 1 Liz Rea 2013-04-08 22:16:13 UTC
Heather,

Do you guys still see this problem?

It seemed like, before I left, that this happened a lot less frequently.

Liz
Comment 2 Chris Cormack 2014-12-16 00:57:39 UTC
Yes still a problem
Comment 3 Katrin Fischer 2019-05-04 13:31:52 UTC
Another 4+ years have passed and holds activity in our libraries is too low to have seen this I guess. Is this still valid?
Comment 4 Katrin Fischer 2023-01-07 21:56:30 UTC
The mentioned bug 4201 has been fixed since.

I haven't seen newer reports on this, but it could still be an issue for bigger consortiums I guess. Could anyone weigh in here with their experience maybe?
Comment 5 Liz Rea 2023-06-22 18:40:34 UTC
Haven't heard this in a good long while. Just... going to retire this. :)