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

Multiple items on a request notice for a single patron

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Medium
    • Development Team:
      Vega
    • Calculated Total Rank:
      74
    • Kiwi Planning Points (DO NOT CHANGE):
      8
    • PO Rank:
      20
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R2
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Grand Valley (Full Sum 2021):
      R1
    • Rank: hbz (TBD):
      R2
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Mainz (Full TBD):
      R1
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R3

      Description

      Dec 2019 - split from:

      • UXPROD-1684 DONE (multiple items on overdue and courtesy notices)
      • UXPROD-2187 DONE (multiple items on check in and check out receipt notices)

      Jan 2020 - narrowing the scope of this feature to multiples on request notices and created a new feature - UXPROD-2252 - multiples on fee/fine notices

      Purpose/Problem: Frequently a single patron has several requested items available and awaiting pick up (from a service point's hold shelf) at the same time. Instead of sending several reminder notices that items are awaiting pick up, it is preferred to send a single notice that refers to all items. Other request notice examples with multiple items might include a request expiration and/or even request confirmation notices (all requested items within a certain period of time). If policies that define when/how to send are not set to real-time, then a frequency for bundling and sending together needs to be determined. Daily may meet most needs and this is what is currently implemented for loan overdue and courtesy notices.

      Description:

      • Need to be able to include several items a single notice sent to a patron.
      • In order to include multiples on request notices, a process would need to be run periodically. Libraries may want to define that time frame, or perhaps daily is a viable frequency if they are not set to "real-time."
      • Real-time may still be needed for some libraries where short-term requests are allowed - NEED to verify.

      Implementation Thoughts:

      • Create FE story for UI to be added to template options (it was commented out since it wasn't functional)
      • Create BE stories by type of notice (time based, such as hold shelf expiration, or event/status based, such as confirmation notice) for processing multiples
        • Frequency for bundling multiple requests/items for time-based notices, such as hold shelf expiration or request expiration, must be determined. It might be designed similar due date notices (courtesy and overdue) which can be sent immediately – OR – bundled and sent daily as determined by the FOLIO user in the policy settings.
        • Bundling for multiple requests/items event/status (request confirmation) notices would need to be designed. We don't currently have a parallel in loan multiples.

      Additional Information

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                JulieBickle_LMU Julie Bickle
                Reporter:
                dbranchini Darcy Branchini
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases