Joripo help
How to design a survey, collect with phones and web forms, watch quality as data arrives, and export it for analysis. Pick a topic:
- Getting started
- Joripo collects survey data on phones and in web browsers, checks its quality as each submission arrives, and exports it ready for analysis. The console has four tabs, Design, Collect, Monitor and Export, on the left, with Configure (the gear) below them.
- Designing forms
- The Design tab holds your forms and server datasets. A form is an XLSForm workbook (.xlsx or .xlsm): Joripo compiles it itself and serves it to phones, web forms and the tester. A form only reaches phones once it is deployed.
- Testing a form
- Test (on a form in Design) opens the deployed form in your browser, running on the same engine and the same definition as Joripo Collect and web forms. If it works in the tester, it works on the phone.
- Collecting data
- The Collect tab sets up the two ways data comes in: phones in the field (Mobile data collection) and forms filled in a web browser (Web data collection). Either way, every submission lands on this server, is checked as it arrives and appears under Monitor.
- Phones and devices
- Every phone that sends data to this server is either a Joripo Collect device, signed in by a person, or holds a device key (for ODK Collect). Both are managed on the Collect tab, by owners and managers.
- Monitoring quality
- The Monitor tab is where you watch data arrive and act on its quality. Joripo checks every submission the moment it lands; what the checks find appears here as quality flags.
- Form dashboards and tracksheets
- Every form has a dashboard of its own: its field status (how many interviews are done, at what pace, by whom) and, when the form has a preload list, a tracksheet of everyone on the list and who is done. It is made from the form's own variables, so a new survey has one the day its form is deployed.
- Reviewing and correcting submissions
- Review and correct is how a team signs off on its data: each submission is approved, rejected or awaiting review, and a reviewer can correct an answer that is wrong, saying why. Nothing is ever lost: the submission stays exactly as the phone or web form sent it, and every decision and correction is kept with who made it, when and why.
- Reports
- Reports (Monitor, and each workspace's Reports page) turn a form's submissions into a document you can read, print and send: a summary of every question with counts, percentages and charts, numbers described, dates spread over time, cross-tabs, the words people used in open answers and the themes you coded them with, and your own text between them. A report is saved: open it again and it is computed afresh from the submissions on the server, with the same blocks and filters.
- Exporting data
- The Export tab gives you each form's data ready to analyse. The default download is the WIDE CSV, in the SurveyCTO-compatible layout and with the same file names, so an existing Stata pipeline for WIDE files runs on Joripo's without changes.
- Joripo Desktop
- Joripo Desktop is a Windows app that keeps a copy of a workspace's forms, submissions and attachments on your computer, and exports them without a connection. Its exports are the console's own: the same WIDE CSV, Stata do-file, .dta and .sav, made by the same code.
- Configuring your server
- Your organisation's administration: its settings, its people, its plan and its workspaces. In Joripo 2.0 it is all under Configure (the gear on the left): Server settings, People, Plan & usage, API tokens and computers, and each workspace's settings. The account menu (your initials, top right) holds only your own things: theme, password, Joripo Desktop, help and sign out. In the Legacy console it is all on the Configure tab.
- Garbling sensitive questions
- Garbling protects the answers to sensitive yes/no questions (harassment, theft, illegal work). For a set share of respondents, chosen at random, a "No" is recorded as "Yes". A recorded Yes therefore never proves that a person said Yes, yet the share answering Yes can still be estimated for the whole sample and for groups. A recorded No is always a true No. Garbling is set up per form, on the workspace's Garbling page (managers and owners see it; only an owner changes it).
- Signing in
- Joripo asks three things, one at a time: your server name, your e-mail (or username), and your password.