Checks, data and exports

The quality checks do nothing

A check that lacks a question it needs does not raise an error: the duration check simply never fires, quotas never fill, scorecards stay empty. Open the form's HFC checks and look at Which question holds what at the top: the enumerator, the start and end times, the GPS reading and the stratum. Correct anything Joripo could not detect, and run the checks again. Each check run also says whether it ran, was not configured (naming the question it lacks), was not applicable, or failed. See How the High Frequency Checks work.

Checks that compare interviews or enumerators run only when you ask for them, with Run HFC checks on Monitor.

One finding about every interview

A finding raised on at least half of a form's interviews (and at least 30 of them) usually points at the form or its settings, not at the data: "no GPS coordinates" on a form that collects no GPS, for example. Joripo folds such a flood into one finding naming the count. Change the setting behind it (here, whether a missing GPS reading is a finding) rather than dismissing each interview.

An export has fewer rows than the Data Explorer

• Review status. Exports hold approved submissions only; a submission nobody has reviewed counts as approved. With a form's review workflow on, new submissions await review and stay out of a default export until approved. Tick Awaiting review or Rejected under Review status to include them.
• Which submissions. A random subset, or the last few days, under Submissions to include narrows the export.
• A purge removed submissions by date or key, keeping a backup of what it removed. See Purging submissions.
• A damaged stored file cannot be read into an export. It is left out and named: the Data Exporter gives the KEYs, and each zip's README.txt lists them. Ask your server's maintainer to look at the file; the server keeps it as it arrived.

Identifying answers are blank or pseudonyms

That is the workspace's Privacy page at work. Without identity access, an identifying answer is exported as a pseudonym, as nothing, or as a rounded location, and a protected photo is withheld. Only an owner gives identity access; see Identity access and privacy.

A correction does not change a finding

The quality checks read corrected answers the next time they run. A finding already raised is not re-run by a correction: run the checks again.

Stata cuts a long text answer

A text answer longer than 2,045 bytes is cut short when Stata imports the CSV through the do-file, a limit of Stata's CSV import. The .dta Joripo writes keeps the whole value. See File formats, Stata and SPSS.

The Stata do-file cannot find the CSV

The do-file names the CSV it was exported with, and looks for it next to itself, in the folder Stata runs from, and in your Downloads folder (including a browser's name (1).csv). Keep the two files together, under the names they were downloaded with.