Checking in migrated lost status copies and Lost/Long Overdue/Lost and Paid copies with no associated circ generates error when zero-balance lost OU setting is enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.0 |
Won't Fix
|
Medium
|
Unassigned | ||
3.1 |
Fix Released
|
Medium
|
Unassigned | ||
3.2 |
Fix Released
|
Medium
|
Unassigned | ||
3.3 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Evergreen version: 2.8+
This problem occurs for sites that enable the Do not change fines/fees on zero-balance LOST transaction OU setting that was introduced in 2.8.
If an Evergreen site migrated copies to a Lost status, checking those copies in will generate the following error (2.8 system):
{"payload"
See the IRC discussion on this error:
http://
Ben Shum was ultimately able to isolate the transactions that could cause the error with the following SQL:
SELECT COUNT(*) FROM asset.copy WHERE status = 3 AND deleted = FALSE AND id NOT IN (SELECT target_copy FROM action.
He then updated those copies to use a new status to prevent the error from occurring.
However, it is probably not uncommon for sites to use the stock lost status when migrating lost copies. One of our sites just came across this same error today. It would be better if the system could handle checkins for lost items with no associated transactions without generating an error.
Changed in evergreen: | |
assignee: | nobody → Michele Morgan (mmorgan) |
Changed in evergreen: | |
milestone: | none → 3.0.9 |
Changed in evergreen: | |
milestone: | 3.0.9 → 3.1.4 |
Changed in evergreen: | |
milestone: | 3.1.4 → 3.1.5 |
Changed in evergreen: | |
milestone: | 3.1.5 → 3.1.6 |
Changed in evergreen: | |
milestone: | 3.1.6 → 3.2.1 |
Changed in evergreen: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in evergreen: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in evergreen: | |
status: | Confirmed → New |
milestone: | 3.2.3 → 3.3-beta1 |
Changed in evergreen: | |
milestone: | 3.3-beta1 → 3.3-rc |
Changed in evergreen: | |
milestone: | 3.3-rc → 3.3.1 |
Changed in evergreen: | |
milestone: | 3.3.1 → 3.3.2 |
Changed in evergreen: | |
milestone: | 3.3.2 → 3.3.3 |
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
milestone: | 3.3.3 → 3.4-beta1 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
I was able to reproduce this as reported.
The same error message is also generated when attempting to check in items that have no associated transaction and status "Lost and Paid"
For items with no associated transaction and the "Long Overdue" status, I got a different error message when attempting a checkin:
"Communication Failure
We experienced a network/server communication failure. Please check your internet connection and try this action again. Repeated failures may require attention from your local IT staff or your friendly Evergreen developers.
Check In Failed. If you wish to use the offline interface, in the top menubar select Circulation -> Offline Interface"
Marking Confirmed.