Patron Notices (UXPROD-18)

[UXPROD-932] Bounced email report for patron notices Created: 13/Jun/18  Updated: 03/Jan/24

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

Type: New Feature Priority: P3
Reporter: Darcy Branchini Assignee: julie.bickle
Resolution: Unresolved Votes: 0
Labels: appreport, error_handling, notice_error, patron_notice, resourceaccess, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Duplicate
is duplicated by UXPROD-1703 Circulation log of all actions filter... Closed
Potential Workaround: EBSCO hosting configured their libraries email service (AWS SES) to notify select staff via email for each bounced email
Epic Link: Patron Notices
Analysis Estimate: Medium < 5 days
Analysis Estimator: Darcy Branchini
Front End Estimate: XL < 15 days
Front End Estimator: Darcy Branchini
Back End Estimate: XL < 15 days
Back End Estimator: Jakub Skoczen
Development Team: Volaris
Report ID (pre-May 2019): ID449
Report Contact(s):
Cheryl Malmborg, David Bottorff, Joanne Leary
Report Functional Area(s):
Resource Access
Kiwi Planning Points (DO NOT CHANGE): 11
PO Rank: 30
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R1
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Problem/Purpose:
Errors, such as bounces, may occur in sending emails. These errors occur if there is an invalid address, the email server no longer exists or is temporarily unavailable, misspelled domain names, etc.. The invalid addresses might happen for a couple of reasons, such as the user closed their email account or the email address was incorrectly imported, migrated or entered for a user. Additionally, email services typically capture if a user has reported an email as spam, so libraries might be interested in these statistics as well in order to improve notification services to patrons. These errors happen outside of the FOLIO system. Most implementers are using a third party service, such as AWS SES, and these email services capture these errors.

Knowing which user records don't have an email address would also be useful as a proactive measure to prevent errors in sending.

Implementation Thoughts:

  • Bounced emails are already captured and logged by third party email services
  • Email services typically expose bounced email data via an API endpoint
  • Presumably, each email service would (or could) structure the data differently and provide it in different formats
  • FOLIO could import the data; however, if it is done this way, then there needs to be a way to map the data to the FOLIO report
  • Additionally, a user record should be flagged that a notice was sent and bounced
  • For GDPR, logs with patron information will need to be cleared every 90 days or when set to do so


 Comments   
Comment by Theodor Tolstoy (One-Group.se) [ 19/Sep/18 ]

If bouncing emails could be routed to a central inbox, that would be enough at the moment.

Comment by Sharon Beltaine [ 30/Oct/18 ]

Please let me know if this needs to become a data warehouse report so we can get it developed in time. Thanks.

Comment by Darcy Branchini [ 30/Oct/18 ]

Sharon Beltaine - I believe it will be data warehouse report.

Comment by Khalilah Gambrell [ 29/Mar/19 ]

Darcy Branchini - is there a way to address this comment "If bouncing emails could be routed to a central inbox, that would be enough at the moment." currently?

Comment by Darcy Branchini [ 29/Mar/19 ]

Khalilah Gambrell, I don't know, I can ask Vega, but I also want to be careful that we're not spending time on a quick fix, which means we have to circle back and rethink it later. I'm planning to more thoroughly analyze this feature beginning in mid-April.

Comment by Martina.Schildt [ 13/May/19 ]

In any case, as a system user I need to be able to view all the letters and e-mails I have created, even retrospectively. This issue only seems to generate a list of the generated notes.
For the above mentioned need a file would be sufficient.

Comment by David Bottorff [ 01/Jul/19 ]

Chicago could wait up to 1 year for this

Comment by Holly Mistlebauer [ 17/Jun/20 ]

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

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