Uploaded image for project: 'mod-circulation'
  1. mod-circulation
  2. CIRC-1112

Recalls not being honored when there has been a renew or change due date

    XMLWordPrintable

    Details

    • Template:
      Standard Bug Write-Up Format
    • Sprint:
      Prokopovych - Sprint 111, Prokopovych - Sprint 113, Prokopovych - Sprint 114, Prokopovych - Sprint 115, Prokopovych - Sprint 116, Prokopovych - Sprint 117, Prokopovych - Sprint 123, Prokopovych - Sprint 124, Prokopovych - Sprint 125, Prokopovych - Sprint 126, Prokopovych - Sprint 127, Prokopovych - Sprint 128
    • Story Points:
      5
    • Development Team:
      Prokopovych
    • Release:
      R3 2021 Bug Fix
    • Affected Institution:
      5 Colleges, BNCF, Caltech, Chalmers, Cornell, Duke, GBV, Grand Valley State University, Lehigh, MI State University/Library of Michigan, Middle Tennessee State University, MO State, Okanagan College, OTHER, SHL, Simmons, Skidmore College, Spokane Public Libraries, St. Michael's College, STU, TAMU, Trinity College, Universidad de Concepción, University of Alabama, University of Chicago, University of Leipzig, University of Tennessee Martin, University of Zaragoza, Warner, Washington-Jefferson

      Description

       

      We’re having trouble with recalls on loans that have been renewed or have changed due date.
      Our loan policy 90/14 days says the loan period is 90 days. If the item is requested, it is recalled and the minimum guaranteed loan period for the recalled item is 14 days. This works fine. The loan period will be shortened to the guaranteed 14 days with a recall return interval of 2 days.
      But if a patron has already had the item for 90 days and so made a renewal (that is now more than 14 days) or if we’ve used change due date, if a recall is made the loan period is not shortened. What are we doing wrong?FOLIO Steps to reproduce:
      1. Lend an item with a permanent loan type standard loan to a patron from any patron group.
      2. Wait until you can and renew or change the due date (to date more than 14 days in the future).
      3. As another patron make a request and recalls the item.

      Expected result:
      The loan period for the first patron is shortened making allowance for the guaranteed 14 days.

      Actual result:
      No change in the loan period.

       

      To test the flag clear for renewals:

      1.  Set up a loan policy in which the minimum guaranteed loan period for recalled items is less than the full check-out period and renewal check-out period (I've been using a 60-day checkout with a 14 day recall period and a 60-day renewal).  Attach that to an item.

      2. Check the item out to a patron.  I've been using the checkout-by-barcode endpoint directly with postman so that I can set the checkout date far enough in the past to make renewals possible.

      3. Place a recall on the item for a different patron

      4.  Verify that the due date is truncated and the loan object shows the 
      dueDateChangedByRecall flag is set to "true" when it's pulled from the circulation/loans endpoint

      5. Cancel the recall
       
      6.  Renew the checked-out item
       
      7.  The loan due date should now reflect the full check-out period for renewals (not truncated).  The loan object should show the "dueDateChangedByRecall" flag set to "false."  

      8.  Place another recall on the item.

      9.  Verify that the due date of the loan is truncated and the "dueDateChangedByRecall" flag set to "true"

      To Test Flag Clear Using Change Due Date

      1. Set up a loan policy similar to the one above and attach to an item.

      2. Check the item out to a patron

      3. Place a recall on the item for another patron.

      4.  Verify that the due date is truncated and the loan object shows the 
      dueDateChangedByRecall flag is set to "true" when it's pulled from the circulation/loans endpoint.

      5. Cancel the recall.

      6. Manually change the due date of the checked-out item using the UI. The value you change it to shouldn't matter, but it will make it easier to test if you lengthen the check-out period, as it will make date truncation easier to see.

      7. If you can, use postman to pull the loan object directly from the circulation/loans endpoint and verify the dueDateChangedByRecall flag is now set to "false."

      8. Place another recall on the item.

      9. Verify the due date is properly truncated, and the dueDateChangedByRecall flag is now set to "true."

       

      Interested parties: Marie Widigson

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                felkerk Kyle Felker
                Reporter:
                Anya N. Arnold Anya Arnold
                Votes:
                0 Vote for this issue
                Watchers:
                22 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases