Joripo- Home
- Documentation
- Review and correct
- Correcting answers
Review and correct
Correcting answers
Correcting an answer with a reason, what cannot be corrected, and where corrected values appear.
Joripo documentation · https://joripo.com/docs/review-and-correct/correcting-answers
On this page
Making a correction
On a submission's page, each answer you may correct has Correct under it. Type the new answer and the reason, which is required, and Save correction. The answer is checked against the question: a whole number for an integer, one of the choice codes for a choice question, a date written YYYY-MM-DD, a latitude and longitude for a location. A blank clears the answer.
- A corrected answer is marked Corrected, with what it was, who corrected it and why.
- To undo a correction, correct the answer back to the original; the history keeps both steps.
- If someone else changed the submission's review while you had the page open, nothing is saved and you are asked to reload: no correction ever overwrites another one unseen.
What cannot be corrected
- photos, recordings and other files, and text and audio audits;
- the device's and the server's own fields: start and end times, the KEY, and the like;
- anything the form does not describe;
- the fields a garbling scheme governs, since a garbled answer is randomised on purpose.
An answer marked as identifying on the workspace's Privacy page can be corrected only by someone with identity access. Anyone else sees it, its corrections and its history masked, as everywhere else.
Where corrected data goes
| Where | What it shows |
|---|---|
| Exports (WIDE CSV, Excel, SPSS, Stata and its do-file, the long format, the Joripo layout) | The corrected answers. Under Answers, As first submitted gives the answers exactly as received. |
| Which submissions an export holds | Approved only. Under Review status, tick Awaiting review or Rejected to include them. |
| The Data Explorer and the submission page | The corrected answers. Export current data in the Data Explorer exports exactly the rows on screen, whatever their status. |
| Joripo Desktop | The corrected answers, and approved submissions only in its exports; its export report says how many were left out. |
| The quality checks | The corrected answers, the next time they run (Run HFC checks). Findings already raised are not re-run by a correction. |
| The correction log (on the review page) | Every correction of a form: the KEY, when, who, the field, the answer before and after, and the reason. |
Attachments, text audits and audio audits are never changed, and a correction is never sent to phones or applied to a case list.
Where it is kept
The stored submission is never rewritten. A submission's review (its status and its corrections) is kept on the file server beside it, sealed like it when encryption at rest is on, so it survives rebuilding the database; corrections are applied wherever the data leaves the server. Every decision and correction is also recorded in the organisation's activity log, naming the field but never the answer.
An export that cannot read a submission's review leaves that submission out and names it, rather than export it uncorrected.