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

Improved logging of activities throughout patron notice process

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: P2
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Epic Link:
    • Back End Estimate:
      Medium < 5 days
    • Development Team:
      Vega
    • Calculated Total Rank:
      30
    • PO Rank:
      90.3
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: MO State (MVP June 2020):
      R2

      Description

      COMBINED with UXPROD-2385.

      Problem: There are many steps in processing emails for patron notices, including: 1.) matching notice policies to location, material type, loan type and patron group using circulation rules; 2.) building emails from templates for each patron; 3.) running when scheduled; and 4.) sending to email service/server. An error might occur at any of those steps or the SMTP credentials might be incorrect or a bug or another issue might interfere with the processing of patron notices. Library staff need to know if notices are not being processed. Ideally they'd prefer to have visibility of errors or problems, but also successful statistics (i.e., how many were sent overnight).

      Description: In early discussions about this feature, we've identified a options and/or steps that improve this visibility of both successful and problematic processing of notices with information about which step failed.

      • Improved logging of activities throughout patron notice process (THIS FEATURE - UXPROD-2394)
      • Monitoring of patron notice process with visual of system health (dashboard) (UXPROD-2382)
      • Handling of errors for patron notices (i.e., retry sending) (UXPROD-2384)

      SPLIT: This feature is being split (April 2020) for each of these steps/options, and this feature is for better logging of errors. One potential idea discussed was a separate module for logging.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                dbranchini Darcy Branchini
                Reporter:
                dbranchini Darcy Branchini
                Back End Estimator:
                Darcy Branchini Darcy Branchini
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases