xact_finish (prematurely?) set on claimed returned item if transaction balance reaches zero
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.2 |
Fix Released
|
Medium
|
Unassigned | ||
2.3 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I believe this behavior has always existed with Evergreen (1.2 through trunk). A checked out item that is marked claimed returned retains a status of Checked Out, and gains a stop fines date and a stop fines reason of claimed returned. The transaction remains open. If any payment are made toward that transaction such that the balance owed is 0, then the transaction is closed, and the item status remains Checked Out. It no longer shows up on the patron's account. This is arguably non-intuitive, though I believe it was meant as a means of resolving claimed returns (I think a lot of libraries "check in" such items, though I don't believe that was intended for any case except when the item was actually found).
Here are some thoughts from an Evergreen staff user, quoted with permission:
On 1.6 with "checked out" as the status for claimed returned items I don't
think the transaction should be closed whether there is bill or not and whether
the bill has been resolved or not. For any checked out item there should be
linked open circulation.
With the new option of choosing a status for items marked claimed returned (new
entry on Library Settings Editor) on 2.0, things are indeed getting complex. I
think item's status should play a role.
On 2.0 the default status is still checkedout, so the circulation should remain
open regardless of bills. As we always tell our sites if the item has
checkedout status the transaction is not over yet though the patron claimed
returned it. ClaimedReturned is an action and one step in the whole process.
How to continue the process depends on whether the library buys the patron's
story. If yes, they should check in the item then mark it missing. If no, mark
the item lost and charge the patron.
The new library setting, Claim Return Copy Status, allows library to choose a
status for claimed returned item. I tested a couple and notice that there is no
consistency between the item's status and the circulation transaction. A
Missing or Temporarily Unavailable item can be still in a patron's account. It
is possible to have an Available item in a patron account. Though we believe
our library staff are sane enough not to make it happen, but they can if they
want to. Besides those two type of status can be edited in copy record. But
Lost and CheckedOut can not due the linked transaction. If status is changed,
the circulation record should be taken care of. (Personally I feel confused by
this new setting.)
To simplify the issue, I think maybe there should be a new status,
ClaimedReturned. Items being claimed returned should all have this status. It's
clear to both patron and staff what has happened to the item. As closing the
circ or not, it should be invidual library's choice. If the library chooses to
close the circ, put in a checkin date and fine stop reason of CR and
xact-finish if no bill. This is the end of the process. (If the item surfaces
later, checking it in will just change the status. The checkin date in the circ
will be the real CR date.) Libraries may use the CR count to control how many
times CR can be done for each patron.
If the library chooses to keep the circ open, they need to follow up. Now their
option is marking the item lost and charge the patron some time later. (If they
don't buy the patron's story now they should not buy it later. But they always
have the choice of checking in the item then marking it missing.) So in this
scenario there should not be checkin date but the fine stop reason in circ on
marking claimed returned.
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in evergreen: | |
status: | Confirmed → In Progress |
assignee: | nobody → Jason Stephenson (jstephenson) |
Changed in evergreen: | |
status: | In Progress → Confirmed |
tags: | removed: pullrequest |
Changed in evergreen: | |
assignee: | nobody → Dan Wells (dbw2) |
Changed in evergreen: | |
milestone: | none → 2.4.0-alpha |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
This is an ongoing issue for SC LENDS also. We have been discussing the intent of the software design as well and are still undecided but are currently leaning towards the design perspective of creating a new status as well.