Uploaded image for project: 'mod-inn-reach'
  1. mod-inn-reach
  2. MODINREACH-169

INN-Reach Circulation Flow: React to Loan Record Changes for INN-Reach Transactions - Item Hold: Final Check-in

    XMLWordPrintable

Details

    • Volaris Sprint 132
    • 3
    • Volaris
    • Lotus R1 2022

    Description

      Purpose/Overview:

      mod-inn-reach needs to be aware of and respond (when necessary) to the return of loans in mod-circulation. The module should consume appropriate domain events for loans and respond accordingly when indicated.

      Requirements/Scope:

      1. mod-inn-reach should consume loan-storage domain events via Kafka (CIRCSTORE-300)
      2. mod-inn-reach should check if the loan is associated with an active INN-Reach transaction
      3. If so, and the last loan action is "checkedin", the loan status is "Closed" and the INN-Reach transaction is a an Item Hold, remove the due date, patron name, and patron ID from the transaction record,  issue the final check-in message to the central server (D2IR API Reference pg. 54), and update the transaction status to FINAL_CHECKIN

      Approach:

      Acceptance criteria:

      • Check-in of item that is loaned to a borrowing site reliably triggers a final check-in message to the central server and related transaction status update to FINAL_CHECKIN for the INN-Reach transaction
      • The patron name and patron ID values are also removed from the transaction

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                brookstravis Brooks Travis
                brookstravis Brooks Travis
                Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases