1. Home
  2. Documentation
  3. Exporting data
  4. Downloading a form's data

Exporting data

Downloading a form's data

Quick downloads, and every option of Export files: layout, repeat groups, language, which submissions, answers and file format.

Joripo documentation · https://joripo.com/docs/exporting/downloading-data

On this page

Quick downloads

Each form on Export offers its WIDE .csv, the Stata import .do file for it, and a zip with the CSV, the do-file and the .dta the do-file makes. A form with several label languages also offers every language at once: the CSV once, and a do-file and .dta for each language.

Export files: every option

Export files (the Data Exporter) opens the full set of choices. Every file of one export is made from the same choices and the same submissions.

OptionChoices
Repeat groupsWide: one row per submission, repeated questions as name_1, name_2, …. Long: one file per repeat group, zipped. See Repeat groups and the long format.
Column layoutSurveyCTO-compatible WIDE, or Joripo, with quality-flag columns, which adds each submission's number of findings (n_flags).
Label languageThe labels of one language, or every language.
Submissions to includeAll of them, a random subset of a number you choose, or those of the last few days.
Review statusApproved only (the default); tick Awaiting review or Rejected to add them. See Review and correct.
AnswersCorrected (the default), or As first submitted: exactly as received.
File format.csv, .xlsx (Excel), .sav (SPSS) or .dta (Stata).
Also includeThe Stata .do file for the CSV, and the quality report (.xlsx).

The Data Exporter lists the export's attachments by submission, and offers them as one zip.

Exporting what you are looking at

On Monitor, a form's Data Explorer filters its submissions by enumerator, quality, the days received and a search. Export current data there downloads the WIDE CSV of exactly those submissions, every page of them, whatever their review status.

Privacy in every export

Every export file is masked for the person downloading it as the workspace's Privacy page says: without identity access, an identifying answer is a pseudonym, nothing, or a rounded location, and a protected photo is withheld. The stored data is never changed. Someone the workspace is shared with downloads only if their access includes exports.

Every download is counted

Each export download is counted in your organisation's usage, and a script's downloads count as API calls too.