JoripoGetting started
What Joripo is, how an organisation, its workspaces and its people fit together, and who may do what.
- Home
- Documentation
Documentation
Joripo documentation
How Joripo works, from an organisation's first form to a cleaned, analysis-ready dataset: what each part does, who may use it, and plainly where something is partly built or still on the roadmap.
/
Designing forms
Writing a questionnaire as an XLSForm workbook, the question types and functions Joripo runs, media, datasets and preloads, versions and testing.
Collecting data
Joripo Collect on Android, ODK Collect, web forms and device keys: installing, signing in, approving phones, working offline and sending.
Case management
Panel and follow-up studies: a list of households or people to visit again, assigned to enumerators, opened from the phone, and kept up to date from the data.
Answer garbling
Protecting individual answers to sensitive yes/no questions with randomized response, while the share answering Yes can still be estimated.
Monitoring and quality checks
Watching data arrive, the High Frequency Checks and every check explained, reviewing findings, scorecards and quotas, field-monitoring dashboards, maps and tracksheets.
Review and correct
Approving, rejecting and correcting submissions with a reason, the per-form review workflow, and where corrected data goes.
Exporting data
Downloading a form's data as CSV, Excel, Stata or SPSS in the SurveyCTO-compatible layout with its do-file, repeat groups in long format, attachments, scripts and Joripo Desktop.
Security and privacy
How access is enforced, identity access and masking, sharing with external clients, encryption at rest and what it does not cover, the activity log, and the known gaps.
Running your own server
What a Joripo server is made of, running one on a Windows computer, where the data lives, the database, keys, backups, and reaching it from the field.
Server administration
The maintainer's panel above every organisation: two-step sign-in, organisations, accounts and phones, usage and health, backups, device settings and apps.
Troubleshooting
What to look at first when a form will not deploy, preloads are empty, a phone cannot connect, the checks stay quiet, an export is missing rows, or the server will not start.
Glossary
The words Joripo uses, from approval to XLSForm, each with a line of meaning and the page that explains it.
Partly built, roadmap, being finalised. A page that describes something not finished says so under its title, and the text says what works today and what does not. Joripo's documentation describes the software as it is, not as it is planned.
Looking for one screen? The help centre explains each part of the console in the words on screen. Integrators who are signed in as an owner will find the REST API reference at /api/docs.