Refactor feedback into a computer-friendly structured report [Needs scoping]

[peterMuriuki]

from web I would like to be able to read the importer's output easily parse it and tell:

• how many records of the csv were processed successfully
• actionable feedback for each csv record that failed, such that user understands how to fix the respective record in the template.

Related: #140

[Wambere]

@peterMuriuki can you provide more information on this? Or maybe even examples of what the current output is vs what you want it to be?

[peterMuriuki]

• Whats the assumed behavior on fail
  • Rejects all records, no record is posted?
  • safer to assume likelyhood of processed records.

Proposed report structure

{
  status: failed, completed
  totalRecs: number
  processedRecs: number
  failedRecs: number
  errorDetails:[
    {
      rowNumber: number
      error: string
      originalRow: string
    },
    {
      // execptions not linked to a record.
      error: string
    }
  ]
}

If job runs to completion:

• if some records failed
  • set status to failed.
• if no record failures or any other errors
  • set status to complete

How the report is extracted by web.

1. Writes report to end of std after a run.

• Web will deal with exceptions(scenarios that make the importer exit without a proper response)

2. Agree on proper delimitation of said report.

• Wrap report between 2 lines of 60 equal signs(=). ============================================================

Non Objectives:

• reporting real time progress