Patron Notices (UXPROD-18)

[UXPROD-1627] Audit/history section of notices sent on user record Created: 25/Mar/19  Updated: 19/Jul/21  Resolved: 19/Jul/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Patron Notices

Type: New Feature Priority: P3
Reporter: Emma Boettcher Assignee: Darcy Branchini
Resolution: Won't Do Votes: 0
Labels: circ-log, delete_candidate, error_handling, notice_enhancement, swag
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Potential Workaround: Circ log UXPROD-1703
Epic Link: Patron Notices
Front End Estimate: Large < 10 days
Front End Estimator: Cate Boerema (Inactive)
Front-End Confidence factor: Low
Back End Estimate: XL < 15 days
Back End Estimator: Cate Boerema (Inactive)
Estimation Notes and Assumptions: CB: Per discussion with the cap planning team and Jakub, a few of us non-developers will estimate the remaining unestimated features so as not to disrupt development. I will tag this feature with "swag" as a reminder to revisit when we have more information. My assumption with this estimate was that we built just what was needed for patron notice display on Users. If we decide to pursue the Circ Log (UXPROD-1703), this feature might become redundant.
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 12
PO Rank: 30
PO Ranking Note: Circ log is providing this information, although multiple items per notice needs to be improved from a UX perspective.
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R2
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

NOTE added 4/9/21: Does the circulation log suit the libraries' needs at this time? Or does the user record need to have a notices accordion that displays this information as well? Or could we simply add a link on the user's record that would go to the circulation log filtered by the user?

Current situation or problem:
Notices are sent for several activities/events in the system. A full list of possible notices that have been implemented as of Goldenrod can be found here. Since then, automated fee/fine notices have also been implemented for overdue and aged to lost fees/fines. There no easy way to find what notices they might have received.

Use case(s)
In reviewing a patron's history, staff may want to review what notices a patron has received.

Proposed solution/stories
Early analysis indicates that a list of notices sent by user is needed. Sort-able fields and filters might include type of notice, item and date/time sent. This will be a (accordion) section on the user record, similar to how fee/fines, loans and requests are accessible from a user record.



 Comments   
Comment by Anya [ 05/Apr/19 ]

FC: Staff need to know, what type of notice was sent to the patron, the date it was sent.... a copy of the message is nice to have but a log of the dates and what is a must.

Comment by Emma Boettcher [ 16/May/19 ]

Assumptions in assigning to Vega: that the scope of this feature is to show the notices sent relative to a loan, perhaps in loan action history.

Comment by Darcy Branchini [ 13/Jun/19 ]

Emma Boettcher, I don't think these would be limited to notices relative to a loan. I think instead we'd want to show all notices sent to patron, including those relative to their loans, requests and fee/fines, although I still think Vega is the right dev team and we still need more analysis on this.

Comment by David Bottorff [ 01/Jul/19 ]

If Circulation log ( UXPROD-1703 Closed ) fulfills this need and is available go-live, Chicago could wait up to 1 year for being able to look this up from the user record. If Circulation is not available at go-live, then Chicago would want this sooner--either go-live or waiting 1 quarter.

Comment by Darcy Branchini [ 02/Jul/19 ]

From RA SIG meeting on 7/1/2019: As mentioned above, there is a significant overlap with the circulation log. Either the circ log or this would be needed by go-live, but not both. If the circulation log was developed, could it be re-used as a partial in the user record or linked to so that there were several different (custom) views of it, such as a list of notices, or a list of request history, or a list of all circ actions/events for a patron?

Comment by Anya [ 02/Jul/19 ]

The FCs agree with David Bottorff and is going to lower this rank to a year out in favor of 1703.

Comment by Erin Nettifee [ 03/Jul/19 ]

Assuming that UXPROD-1703 Closed is available from both the patron and the item records, Duke would bump this down to up to a quarter or up to a year.

Comment by Darcy Branchini [ 19/Jul/21 ]

Deleting per RA SIG conversation on 7/19/21. SIG proposed that instead there's a feature for the last few actions/events (a subset of the circ log data) on the user record as a separate accordion.

Comment by Darcy Branchini [ 19/Jul/21 ]

Created UXPROD-3185 Open instead which includes all circ log data instead of just notices.

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