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

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

    XMLWordPrintable

Details

    • Vega
    • 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}
    • University of Chicago
    • TBD

    Description

      Overview: Patron automatic blocks are aged to lost, then the patron renews them- but the block is not removed
      Juniper HF 4+
      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

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                cmalmbor Cheryl Malmborg
                Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases