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

Bounced email report for patron notices

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Potential Workaround:
      EBSCO hosting configured their libraries email service (AWS SES) to notify select staff via email for each bounced email
    • Epic Link:
    • Analysis Estimate:
      Medium < 5 days
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      XL < 15 days
    • Development Team:
      Vega
    • Report ID (pre-May 2019):
      ID449
    • Report Functional Area(s):
      Resource Access
    • Calculated Total Rank:
      64
    • 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

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                JulieBickle_LMU Julie Bickle
                Reporter:
                dbranchini Darcy Branchini
                Analysis Estimator:
                Darcy Branchini Darcy Branchini
                Front End Estimator:
                Darcy Branchini Darcy Branchini
                Back End Estimator:
                Jakub Skoczen Jakub Skoczen
                Report Contact(s):
                Cheryl Malmborg, David Bottorff, Joanne Leary
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases