Uploaded image for project: 'ui-circulation'
  1. ui-circulation
  2. UICIRC-218

End to End Testing: Send hold request-related notices (item status change)



    • Story
    • Status: Closed (View Workflow)
    • P1
    • Resolution: Done
    • None
    • None
    • None
    • Vega


      Hold requests include items that are currently checked-out by another patron (Patron A). A hold request restricts Patron A from renewing the item. This differentiates it from a recall request where Patron A must return it sooner than the original due date/time. Once the requested item is returned, it is routed to the requested location, if necessary, and then placed on the hold shelf.

      The hold request process prompts several patron notices. Specific notices are outlined below.

      For each of these scenarios, exact timing and conditions are determined by a combination of notice policies and circulation rules, and exact wording is determined by templates. Each of these specific scenarios may or may not be used by every institution. If there's no corresponding policy defined in settings, then these scenarios won't apply.

      Scenario 1 - Available
      Given a requested item for hold
      When it is scanned in at requested location, item status is changed to "available - awaiting pickup," and it's put on hold shelf for the patron
      And there's a matching circulation rule, notice policy and template
      Then send an available notice to the requester at the top of the queue

      TestRail: Results


          1. Slide6.png
            96 kB
            Darcy Branchini

          Issue Links



                Unassigned Unassigned
                dbranchini Darcy Branchini
                Darcy Branchini Darcy Branchini
                0 Vote for this issue
                2 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases