Uploaded image for project: 'mod-patron-blocks'
  1. mod-patron-blocks
  2. MODPATBLK-129

Kiwi: Automated Block for Max Amount Owed Not Removed When Aged to Lost Item Returned

    XMLWordPrintable

Details

    • EPAM-Veg Sprint 139, EPAM-Veg Sprint 140
    • 3
    • Vega
    • Morning Glory (R2 2022)
    • Yes
    • Hide
      This can be caused by some of the event messages being lost on the way from mod-feesfines to mod-patron-blocks through pub-sub/Kafka, so the data is out of sync. We have a synchronization mechanism that can be a temporary workaround in such cases.

      We have a synchronization mechanism that can be a temporary workaround in such cases. You can re-sync automated patron blocks data for a single patron like this:

      POST /automated-patron-blocks/synchronization/job
      body:

      {
        "scope": "user",
        "userId": "{USER_ID}"
      }
      or you can do a full re-sync for all patrons (this can take a lot of time depending on the amount of loans, fees/fines and other data):

      POST /automated-patron-blocks/synchronization/job
      body:

      {
        "scope": "full"
      }
      These calls return a sync job object with an ID, you can use this ID to monitor its status, number of processed objects, errors etc.:

      GET /automated-patron-blocks/synchronization/job/{SYNC_JOB_ID}
      Show
      This can be caused by some of the event messages being lost on the way from mod-feesfines to mod-patron-blocks through pub-sub/Kafka, so the data is out of sync. We have a synchronization mechanism that can be a temporary workaround in such cases. We have a synchronization mechanism that can be a temporary workaround in such cases. You can re-sync automated patron blocks data for a single patron like this: POST /automated-patron-blocks/synchronization/job body: {   "scope": "user",   "userId": "{USER_ID}" } or you can do a full re-sync for all patrons (this can take a lot of time depending on the amount of loans, fees/fines and other data): POST /automated-patron-blocks/synchronization/job body: {   "scope": "full" } These calls return a sync job object with an ID, you can use this ID to monitor its status, number of processed objects, errors etc.: GET /automated-patron-blocks/synchronization/job/{SYNC_JOB_ID}
    • Cornell, University of Chicago
    • Implementation coding issue

    Description

      Overview: Patron automatic blocks are aged to lost, then the patron renews them- but the block is not removed
      Kiwi HF2, patch 3
      Steps to Reproduce:

      Patron checks out item
      a trigger to automatic block happens
      the item ages to lost
      patron ties to renew - but can't so it is overriden to renew
      the automatic block is not removed

      Expected Results: the block is removed
      Actual Results: the block remains

      **The workaround used for this issue in Juniper does not appear to work for Kiwi. 

       

      Tom Trutt uploaded a screenshot for the patron in question and as well as all the API calls from before showing the user summary pre and post sync and fine-fee summary.

      •  In this instance, the item was checked in and not renewed, but the fine is still counting against the patron.
      • I ran the sync process for the user, checked and it finished without error however the block is remaining. The Patron Summary has not changed from what it was prior to the sync.

      TestRail: Results

        Attachments

          1. accounts Summary - post sync
            0.3 kB
          2. accounts Summary - pre sync
            1 kB
          3. fine detail.PNG
            fine detail.PNG
            67 kB
          4. patron summary.PNG
            patron summary.PNG
            79 kB
          5. synce results
            0.3 kB
          6. Sync Exicute
            0.1 kB
          7. transactions pre sync
            0.8 kB
          8. User_Summary-pre-sync
            0.3 kB

          Issue Links

            clones

            Bug - A problem which impairs or prevents the functions of the product. MODPATBLK-112 Juniper: Automated Block for Max Amount Owed Not Removed When Aged to Lost Item Returned

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed
            defines

            New Feature - New feature requests UXPROD-3418 Vega - Morning Glory Enhancements/Bugfixes/Tech Debt

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is cloned by

            Bug - A problem which impairs or prevents the functions of the product. MODPATBLK-130 Lotus: Automated Block for Max Amount Owed Not Removed When Aged to Lost Item Returned

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODPATBLK-134 Kiwi HF3: Automated Block for Max Amount Owed Not Removed When Aged to Lost Item Returned

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODPATBLK-135 Lotus HF1: Automated Block for Max Amount Owed Not Removed When Aged to Lost Item Returned

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed
            relates to

            Task - A task that needs to be done. MODPATBLK-131 Release v1.4.2

            • TBD - To be determined
            • Closed

            Task - A task that needs to be done. MODPATBLK-132 Release v1.5.3

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-2185 User-level synchronization is fixed (MODPATBLK-129)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODPATBLK-128 Unable to remove invalid fee/fine related block with user-level sync

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                OleksandrVidinieiev Oleksandr Vidinieiev
                stephaniesbuck Stephanie Buck
                Votes:
                0 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases