Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-1873

CheckSum Checker Emailer sends emails for 0 issues, doesn't specify any site info

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.7.3, 1.8.3, 3.2, 4.0
    • Fix Version/s: 4.1, 5.0
    • Component/s: DSpace API
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      6
    • Documentation Status:
      Needed

      Description

      When using the DSpace Checksum Checker Emailer ([dspace.dir]/bin/dspace checker-emailer), the "mail.admin" email address will receive a lot of emails with a subject of:

      "Checksum checker Report - 0 Bitstreams found with POSSIBLE issues"

      There's two problems with these email reports:
      (1) Often the majority of the emails report "0 Bitstreams". While it could be nice to see the checker is being active, it's rather annoying to consistently see empty reports. This annoyance can be compounded if you are managing several DSpace sites at once.

      (2) The emails sent by the Emailer have no information regarding the DSpace instance. Nothing in the email or attached report identifies the source. This makes it extremely difficult to tell which DSpace instance the email was sent from if you are managing multiple DSpace instances (even just a test and production instance).

      Both of these issues make using the Checker Emailer more painful than it should be.

      For DSpaceDirect service, we've made some minor fixes to solve both of these issues:
      1) Do not send an email unless >=1 bitstreams are found with possible issues
      2) Ensure the email sent includes the "dspace.hostname" in the subject line. E.g. "Checksum checker Report - 2 Bitstreams found with POSSIBLE issues on demo.dspace.org"

      A PR including these simple fixes is forthcoming.

      I believe these fixes could be considered "bug fixes" rather than "improvements". So, I've tentatively scheduled this fix for 4.1. But, if anyone disagrees, we can reschedule it for 5.0 instead.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tdonohue Tim Donohue
                Reporter:
                tdonohue Tim Donohue
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: