Web Client: Transits Don't Always Clear
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Critical
|
Unassigned | ||
3.0 |
Fix Released
|
Critical
|
Unassigned | ||
3.1 |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Evergreen 3.0.8
Since we moved to the web client, we have had way more reports of items showing an active transit record not actually being in transit. We have not been able to determine why this is.
There's a couple things that could be contributing, like bug 1738688 and bug 1780315, but I don't see these contributing enough to effect the numbers we are seeing.
One working theory I have is that keeping check in modifiers on, (like Retarget Local Holds, Retarget All Statuses, and Clear Holds Shelf), is slowing down check-in and leading to transits not be calculated correctly. I have not been able to duplicate it. But in the reports that staff remember, at least one of these modifiers is usually turned on.
Below are a few comparison numbers based on transits created in the previous 2 months*.
The current numbers come from our production server, (we have been up on the web client since 5/28/18).
The old numbers come from a training server containing data from January-ish 2018 (*transits created Nov 2017 and newer). Because of this, the old numbers can be taken as more of an estimate, but since active transits will continue to stay active until something happens to the item, it should still be a good estimate.
Number of items that have multiple active transits:
Current: 131 | Old: 15 (773.33% increase)
Number of items that have an active transit but not a status of In Transit:
Current: 806 | Old: 170 (374.12% increase)
Number of items that have an active transit and specifically a status of Available or Recently Returned
Current: 484 | Old: 59 (720.34% increase)
I'll update this bug if future testing provides any insights.
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
I'll note that when referring to active transits, I'm referring to transits that have a NULL receive time and a NULL cancel time.