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

Assign Patron default service point for requests and general customer service

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Template:
    • Potential Workaround:
      Hide
      Cate Boerema: Ask patrons to select a pickup service point with each patron-initiated request. When staff are creating requests in FOLIO, they will need to ask the requester which service point they want to pick up at and select it. Chicago has somehow implemented default service points for patrons directly in discovery

      Note: default pickup service point isn't the only use for this information. When there is an issue with a patron, RA staff sometimes look to see what SP is their default. If it's in a different library, they might call the library and say "hey there's an issue with your patron". There is no real workaround for this use case.
      Show
      Cate Boerema: Ask patrons to select a pickup service point with each patron-initiated request. When staff are creating requests in FOLIO, they will need to ask the requester which service point they want to pick up at and select it. Chicago has somehow implemented default service points for patrons directly in discovery Note: default pickup service point isn't the only use for this information. When there is an issue with a patron, RA staff sometimes look to see what SP is their default. If it's in a different library, they might call the library and say "hey there's an issue with your patron". There is no real workaround for this use case.
    • Epic Link:
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      Small < 3 days
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      96
    • PO Rank:
      95.8
    • PO Ranking Note:
      Hide
      2019-07-18: Decreasing PO rank slightly per discussion with SIG to put this under Requests overdue/missing in transit feature and Patron notes on Requests
      2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
      Show
      2019-07-18: Decreasing PO rank slightly per discussion with SIG to put this under Requests overdue/missing in transit feature and Patron notes on Requests 2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R2

      Description

      Currently, when patrons request materials, the default pickup service point for the request is the first one in the dropdown menu. This means that, when patrons are creating their own requests through discovery, they need to find their preferred service point in the menu and select it each time (a minor hassle). That said, when a library staff member is creating the request on behalf or a patron, they may not even know which service point to select for the patron.

      To solve this problem, new requests should auto-populate with the preferred pickup service point for the requester. It should be possible to override the default, when desired.

      This feature used to be called "User branch/location" but, upon discussion with the RA SIG, the primary use of associating a patron with any type of location information would be to assign a service point as the patron’s default pick-up location for requests. Given that, we have renamed this feature "Assign Patron default pick-up service point for requests) and moved it to the Requests epic.

      Current thinking on design (needs review with SIGs): https://drive.google.com/drive/folders/1lqjdblpO_3wFLYcZdR4jabGCmp0iFsmC

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                cboerema Cate Boerema
                Reporter:
                cboerema Cate Boerema
                Analysis Estimator:
                Khalilah Gambrell Khalilah Gambrell
                Front End Estimator:
                Jakub Skoczen Jakub Skoczen
                Back End Estimator:
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases