https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42852

            Bug ID: 42852
           Summary: SIP2 self-check check-in does not resolve mis-routed
                    transfers
   Initiative type: ---
        Sponsorship ---
            status:
           Product: Koha
           Version: Main
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: SIP2
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
            Blocks: 42851
  Target Milestone: ---

Split off from bug 42851.

When an item that is in transit (datesent set) is checked in via the SIP2
self-check interface at a branch that is NOT the transfer's tobranch,
AddReturn returns a WrongTransfer message but does not close the row.
C4/SIP/ILS/Transaction/Checkin.pm:158-161 only sets destination_loc and an
alert; it never cancels/redirects the stale transfer. The original
in-transit row is orphaned and shows forever on the "Transfers to receive"
report. (The staff page circ/returns.pl:554-578 does handle this; SIP does
not.)

Proposed approach:
- Complete the original transfer, recording the actual branch it ended up at
  (update tobranch / comment so the error is recorded, not lost).
- Open a new transfer from the check-in branch to the original tobranch.
- Re-link anything pointing at the old transfer (e.g. holds) to the new one
  so a subsequent check-in at the correct branch triggers correctly.

Test plan:
1. Transfer an item from A to B (in transit).
2. Check it in at branch C via a SIP2 self-check device.
3. Before: branchtransfers row A->B stays open forever.
4. After: original transfer recorded as resolved at C, new transfer C->B
   created and in transit, holds re-linked.


Referenced Bugs:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42851
[Bug 42851] [OMNIBUS] Items left stuck in transit when checked in outside the
staff returns page
-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to