Requests (UXPROD-790)

[UXPROD-1800] Patron Comments on Request Created: 25/Jun/19  Updated: 03/Jan/24  Resolved: 23/Apr/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R1 2021
Parent: Requests

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Khalilah Gambrell
Resolution: Done Votes: 0
Labels: Showstopper-Cornell, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-988 BE: Patron note on Request Closed
is defined by CIRCSTORE-255 BE: Patron note on Request Closed
is defined by UIREQ-530 Patron comments on Request Closed
is defined by UX-411 Check mockups for patron comments on ... Closed
is defined by CIRC-1036 BE: Display Patron Comments in Hold S... Closed
is defined by CIRC-1037 BE: Create staff slip token for Patro... Closed
is defined by EDGPATRON-33 Add patron notes to requests (EDGEPAT... Closed
is defined by MODPATRON-4 Add patron comments to requests (MODP... Closed
is defined by UICHKIN-208 Display Patron comments on Awaiting p... Closed
is defined by UICIRC-523 Create staff slip token for Patron co... Closed
is defined by UIREQ-549 Display Patron Comments in Requests CSV Closed
is defined by UIREQ-550 Display Patron Comments in Hold Shelf... Closed
Relates
relates to UXPROD-1801 Staff Note on Request Closed
Epic Link: Requests
Front End Estimate: Large < 10 days
Front End Estimator: Cate Boerema (Inactive)
Back End Estimate: XL < 15 days
Back End Estimator: Cate Boerema (Inactive)
Estimation Notes and Assumptions: 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.
Development Team: Prokopovych
PO Rank: 101
PO Ranking Note: 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.
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R2
Rank: hbz (TBD): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): 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: UXPROD-1801 Closed

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


 Comments   
Comment by David Bottorff [ 09/Jul/19 ]

This is go live for Chicago

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Cornell comment from Round IV Outliers spreadsheet: This outlier is a showstopper for Cornell

Comment by Debra Howell [ 29/Sep/20 ]

Cate Boerema and Holly Mistlebauer - The Workaround field has a comment in it rather than a workaround. Please move that comment to this Comments section. Requesting an update on this feature. This is a showstopper for Cornell.

Comment by Cate Boerema (Inactive) [ 29/Sep/20 ]

Hi Debra Howell. The capacity planning group will begin the Iris planning process next week and this feature will certainly be considered. We are aware that it's a showstopper for Cornell.

The comment in the Workaround field is related to the workaround (that there is none). I would think it belongs, there. Is it causing a problem for you?

Comment by Debra Howell [ 29/Sep/20 ]

Thanks Cate Boerema! The comment in the Workaround field is an issue, because it has recently come to my attention that some folks use it as a filter for searches. Some groups are not looking at features that have something entered in the Workaround field - whether or not the comment in the Workaround field is actually a workaround. I recently did a specific query to look at UXPRODs that Cornell had ranked R1 and had something entered in the Workaround field and found many features that were not being looked at as a result. I'm flagging these UXPRODs now and hoping to elevate them.

Comment by Cate Boerema (Inactive) [ 29/Sep/20 ]

Some groups are not looking at features that have something entered in the Workaround field - whether or not the comment in the Workaround field is actually a workaround.

Oh, that sounds like a bad idea. I'm glad you took a closer look, Debra Howell! I removed the comment from that field. Here's what it said:

Cate Boerema: No workaround for this. Many on SIG feel it's a must-have for mvp

Comment by Debra Howell [ 29/Sep/20 ]

Cate Boerema Thanks much!

Comment by Cate Boerema (Inactive) [ 01/Oct/20 ]

Hi Michal Kuklis and Bohdan Suprun could you please take a look at these estimates and make sure they still make sense? I have included mockups now (see link above) and a "story outline". I put creation of slip tokens in scope because it seemed easier than creating a whole feature for Vega to just add a couple of tokens. But if you guys think it really should be Vega who creates those, I am happy to mark that "out of scope". Also, please note, Core Functional will need to be responsible for the changes to EDGEPATRON and MODPATRON, as well.

Thanks much!

Comment by Michal Kuklis [ 01/Oct/20 ]

Cate Boerema is this story only about the changes in ui-requests? If so then I think the estimate looks good. If this also should cover some additional changes in ui-checkout / ui-checkin and creating additional tokens then it's very likely a larger work.

Comment by Cate Boerema (Inactive) [ 01/Oct/20 ]

Hi Michal Kuklis. Everything in the story outline is in scope. I changed the header to "In scope" so that's more clear.

Comment by Michal Kuklis [ 01/Oct/20 ]

Thanks Cate Boerema! I bumped that estimate to large from the front end perspective.

Comment by Bohdan Suprun (Inactive) [ 02/Oct/20 ]

Cate Boerema,

It is about 15 days. The changes are not complicated but we have to apply updates in numerous of places + we do not have a lot of experience in patron modules.

It is ok to have slips changes in the scope. It'd be good to have a sample story or some guidance/support from Vega. Just not sure how involved it can be.

Comment by Cate Boerema (Inactive) [ 02/Oct/20 ]

Thank you Bohdan Suprun and Michal Kuklis!!

Comment by Anya [ 22/Mar/21 ]

Khalilah Gambrell - just pinging to see what the status is on this 

Comment by Khalilah Gambrell [ 22/Mar/21 ]

Anya, the backend is ready. I need to confirm with EBSCO - EDS team on enabling this capability.

Comment by Anya [ 22/Mar/21 ]

Thanks Khalilah Gambrell

Comment by Khalilah Gambrell [ 26/Mar/21 ]

Posted to RA SIG Slack Channel
_@Kelly Drake, @Brooks Travis, @MarieWi, core functional completed the work to support a patron entering a note when making a request with Iris ( UXPROD-1800 Closed ). If you are an EDS customer that uses EDS as your discovery/OPAC layer then this functionality will be available on the EDS UI this summer. If you are an EDS customer that does not use the EDS UI then it is available with Iris to use. Please review edge-patron documentation. (edited) _

Comment by Anya [ 22/Apr/21 ]

Khalilah Gambrell will this be included in Iris? If so could it be added to the release notes?- thanks 

Generated at Fri Feb 09 00:18:37 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.