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

Request: Allow Override of Request Policy Prevented Request

    XMLWordPrintable

Details

    • Not Scheduled
    • Volaris
    • 74
    • Hide
      2021-03-30 - BT: Updating to calc rank.
      2021-03-03 - BT: Updating PO rank to calculated rank.
      2021-02-08 - BT: Updating PO rank to new calculated total rank based on new SU21 implementer R1/R2 rankings.
      2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
      Show
      2021-03-30 - BT: Updating to calc rank. 2021-03-03 - BT: Updating PO rank to calculated rank. 2021-02-08 - BT: Updating PO rank to new calculated total rank based on new SU21 implementer R1/R2 rankings. 2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
    • R3
    • R4
    • R1
    • R1
    • R2
    • R3
    • R2
    • R2
    • R1
    • R1
    • R1
    • R2
    • R1
    • R2

    Description

      Current situation or problem: Request policies can prevent requests of certain types being created by certain patron groups. There is currently no way to override this.

      In scope: Override request policy that says an items is not requestable by a patron. Overrides should be flagged as such for reporting/audit trail purposes, and staff may want to enter comments about why the item had an override (assuming this affects loan structure).

      Out of scope:

      • Permission escalation for overriding when you don't have permission to do so - see UXPROD-2645
      • Displaying pre-filtered view of the circ log on the Request record is out of scope for this. See UXPROD-1056
      • Distinguishing between title-level and item-level requests (e.g., allowing override for one type but not the other.)

      Use case(s):

      • Scenario: Request policies are configured to disallow holds to be placed by patrons. A patron contacts the library requesting to be notified when an item is available for checkout, and asks that the item be held for pickup. Currently, there is no way to place this hold on behalf of the patron (eg. “Request not allowed for this item/patron combination”). Staff (with proper permissions) should be able to override this, similar to loan policy overrides in Checkout.
      • Scenario 2: Request policies are configured to disallow recalls by patrons. A patron contacts the library with an urgent request for an item that has been checked out by the same faculty member for three years, so the staff decides it is appropriate to allow a recall of the item for the requesting patron. Current functionality does not permit this recall to be created for the requesting patron (eg. “Request not allowed for this item/patron combination”). Staff (with proper permissions) should be able to override this, similar to loan policy overrides in Checkout.
      • Scenario 3: Request policies are configured to disallow pages by a patron for an item. A patron contacts the library to request an item to be paged. The staff member determines that the library will retrieve the item from the stacks for the patron due to a temporary accessibility accommodation. Currently, creating this page request would not be allowed. The staff member (with appropriate permissions) should able to override this, similar to loan policy overrides at checkout.

      Proposed solution/stories (optional):
      Solution discussed with RA SIG on 2020-10-12: https://wiki.folio.org/display/RA/2020-10-12+Resource+Access+Meeting+Notes Stories:

      • Requests App: Support override of prevented request
        • Should display when request is prevented
        • Should include the ability to add a comment
      • Circ Log: Indicate that a request was created with override
      • Permission: Add permission for request override

      Links to additional information:

      Questions/Comments:

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                auger Tim Auger
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases