Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2565

Create requests for newly ordered items automatically from the POL

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Development Team:
      Thunderjet
    • Calculated Total Rank:
      42
    • Kiwi Planning Points (DO NOT CHANGE):
      4
    • PO Rank:
      89
    • PO Ranking Note:
      This can be done manually by navigating to the item record immediately after the order is placed. The ranking reflects that this allows room for error and a less than ideal workflow.
    • Rank: Chalmers (Impl Aut 2019):
      R3
    • Rank: Chicago (MVP Sum 2020):
      R2
    • Rank: Cornell (Full Sum 2021):
      R2
    • Rank: Duke (Full Sum 2021):
      R2
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: 5Colleges (ERM Jun 2020):
      R2
    • Rank: GBV (MVP Sum 2020):
      R3
    • Rank: Grand Valley (Full Sum 2021):
      R3
    • Rank: MO State (MVP June 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R3

      Description

      Overview:

      Allow users to add enough request information to the order to generate a request on the item being ordered when the order is opened. This way patrons can be notified that the item they requested has been ordered and follow it's progress.

      Note: proposed by Duke (Julie Brannon, Erin Nettifee)

      Use cases:

      • At Duke when a patron requests that we order a title, we would flag it as a rush order and capture the patron ID on the order record. Upon arrival a hold is put on the item so that it can't be loaned to anyone else. In this morning's demo you set up a patron request - there was no automation to create the request automatically.
      • The hold action needs to happen immediately at the time of order creation to preserve the "first dibs" priority of the original requestor so that they don't get bumped if a request sneaks in as soon as the item is created.
      • Library is ordering at vendor site and vendor does not have user ID. Allowing requester to NOT be a "user" account would be valuable.
      • The library does occasionally place holds at point of order without knowing the specific user id. In some cases the requester information could be in a separate system (Eg. Iliad) and a default user is used to identify that this item should be treaded a certain way in the workflow ultimately having a person update the request information so the item is put aside for the correct user.

      In scope

      • Allow user creating order to toggle a "Create request" action if the requester field is populate by a User ID.
      • If "Create request" is true than orders app will automatically place a request on the first item record created on behalf of the requester when the Order transitions to Open.
      • In order to create request the system must have a requester user id and Pickup service point in POL
      • If not making a request the system should allow free text in the requester filed.
      • Pickup service point and requester user id is ONLY required if "Create request" equals 'true'.

      Questions

      • It seems we may need to add an option for the Fulfillment preference after all?
      • Regarding Hold vs. Recall can an assumption actually be made here or would it need to be a setting?
      • Another use case: alerting a user to a newly-available, ordered eBook, which does not have an item record. Is there a way to create a patron request for that? Should that perhaps be a separate feature?

      Links

      See proposed mockups: https://drive.google.com/drive/folders/1SpOvkcoQLuI0P0tpf_Le-924gKtTYzPM?usp=sharing

        TestRail: Results

          Attachments

            Activity

              People

              Assignee:
              dennisbridges Dennis Bridges
              Reporter:
              abreaux Ann-Marie Breaux
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:

                  TestRail: Runs

                    TestRail: Cases