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

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

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P1
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Template:
    • Development Team:
      Vega

      Description

      Context
      Recall requests include items that are currently checked-out by another patron (Patron A). Recall requests typically ask Patron A to bring the item back before it's original due date/time. This differentiates it from a hold request where Patron A cannot renew the item. Once the requested item is returned, it is routed to the requested location, if necessary, and then placed on the hold shelf.

      The recall 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
      Given a recalled item
      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

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                dbranchini Darcy Branchini
                UX Lead:
                Darcy Branchini Darcy Branchini
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases