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

Patron Comments on Request

    XMLWordPrintable

Details

    • Large < 10 days
    • XL < 15 days
    • BE: The changes are not big, but we need to update numerous of places and do not allow update of the property + we do not have a lot of experience with the patron modules.
    • Prokopovych
    • 101
    • Hide
      2019-07-18: Bumped ranking up again so this would be higher than default service point for requests (per SIG feedback)
      2019-07-12: Bumped rank way up on this because my impression from SIG discussions is that this is pretty high priority. Calculated rank on this is currently low because not many have had the chance to rank it.
      Show
      2019-07-18: Bumped ranking up again so this would be higher than default service point for requests (per SIG feedback) 2019-07-12: Bumped rank way up on this because my impression from SIG discussions is that this is pretty high priority. Calculated rank on this is currently low because not many have had the chance to rank it.
    • R5
    • R1
    • R1
    • R2
    • R2
    • R1
    • R4
    • R2
    • R1
    • R2
    • R2
    • R1
    • R2

    Description

      Purpose: Patrons sometimes want to communicate additional information with their requests. For example:

      • "I really need the 1989 volume for this but couldn't figure out how to find it."
      • "Can you deliver this to the History building for Professor Grant? He can't figure out how to get the request through with his account."
      • "I'm leaving town so I really need this in the next three days"

      Current thinking on design:

      • Implement simple Patron note field on the request record
      • Label should be something like "Patron message to staff" or "Patron comments" to differentiate it from the Staff note feature which already exists on the request form.
      • Note would not be editable after request is created (to prevent patrons from changing things after fulfillment has begun and saying "but I put it in the note")
      • Note should be available via API ("patron portal" edge api?) so patrons can create and view the note through discovery (create is more important as most discovery layers/OPACs don't support view of patron note after creation - but SMEs think it would be valuable!)
      • Note should display in requests csv and any other request reports
      • Token should be available for hold, transit and discovery slips
      • Nice-to-have: note should be visible on the hold/awaiting pickup popup at check-in
      • Not necessary to have it in the transit popup at check-in

      See discussion from RA SIG meeting here:

      Staff note functionality has been specified separately: UIU-1090

      In scope:

      • Request: Patron note on request
        • ui-req
        • mod-circ
      • Display patron note in Request CSV
      • Display patron note in Hold shelf clearance report
      • Display patron note on hold popup (at check in)
      • Display patron note on transit popup (at check in)
      • Create patron note token for hold slip, transit slip, delivery request slip and pick slip
      • EDGPATRON - Add and display patron note on request
      • MODPATRON - Add and display patron note on request

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                kgambrell Khalilah Gambrell
                cboerema Cate Boerema
                Cate Boerema Cate Boerema
                Cate Boerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases