Feature: create exportable report for critical content errors #131
Description
Is your feature request related to a problem? Please describe.
When a critical error occurs (one that halts the workflow), the user often needs to send details of the error to the department/producer that created the package. This producer may not have access to Enduro to view the error in the UI. The producer needs enough information about the package and its errors to fix them before resubmitting the package.
Describe the solution you'd like
I would like the user who initiated the transfer, or a user/users defined in the Enduro settings, to receive an emailed PDF report that details which job(s) resulted in the error, next steps, and any available logs or output. I would also like to be able to download the error report from the SIP detail page (or maybe a dedicated error reporting page).
We can take an incremental approach to this. For the first iteration, Enduro can produce something as minimal as a text-based (literally plain text) report that can be copy-pasted from the browser. However, the goal is to collate all of the necessary information about errors in one place so that the information is easy to forward on to another party (e.g. can copy-paste in one go, doesn't require multiple screen captures, etc.)
The error report should contain, at a minimum, the following information:
SIP name: [package name]
Date: [date that package was started]
The following activities had errors or failed:
[Activity name] - [datetime]
Error message[Activity name] - [datetime]
Error message
(The formatting doesn't need to match the above, and in fact all of this needs proper mockups)
Additional context