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.

Finding your way

Design is where you land: every form, in its workspace and group. Each form has Test, Edit, Upload (a revised form definition) and Download in sight, and Tools, Encryption, Duplicate and Delete under More. Create form, Create group and Create workspace are at the top; the + handles between items insert a form, group, server dataset or workspace right there.
Collect: each workspace's web data collection, field team (data collectors, phones and device keys) and case list, then each form's web link and who may use it.
Monitor: where things stand (workspaces, forms, submissions, open quality flags), then each form's submissions, Data Explorer, Quality checks and reports; what needs attention is below.
Export: each form's Download data (format, layout, language, which submissions), the Data Explorer and every other file; Joripo Desktop keeps a copy on your computer.
Configure: server settings, People, the organisation, plan and usage, API tokens and computers, and each workspace's settings, external access, privacy and garbling. A workspace's own pages are also in its ☰ menu on the Design page. See Configuring your server.

The Legacy console (obsolete)

The older layout, with the Discover, Design, Collect, Monitor, Export and Configure tabs, is obsolete and no longer maintained; every page of it says so. It is still reachable from Legacy console (obsolete) in the account menu (your initials, top right), and Back to Joripo 2.0 on any of its pages returns. Both show the same data with the same permissions; switching changes nothing.

Signing in and out

Closing the browser signs you out, and so does leaving Joripo unused for two hours; sign in again and you are back on the page you were on. Typing in the form editor, the form tester or a web form counts as using Joripo. If you are signed out anyway while working there, nothing is lost: Joripo asks you to sign in again in a new tab, and sends your work when you come back and press Try again. On your own computer, tick Keep me signed in on this computer when you sign in to stay signed in for 14 days unless you sign out; leave it unticked on a shared computer. Sign out in the account menu signs you out in every browser.

The workflow

Design: upload your XLSForm workbook (or start a new form in the browser), attach any media and preload files, test it, and deploy it. Server datasets are added from the + handles. See Designing forms.
Collect: sign phones in to Joripo Collect, or give ODK Collect a device key, and share web-form links. See Collecting data and Phones and devices.
Monitor: watch submissions arrive, review them in the Data Explorer, and work through quality flags, enumerator scorecards and quotas. See Monitoring quality.
Export: download the data as a SurveyCTO-compatible WIDE CSV, Stata, SPSS or Excel files. See Exporting data.

Workspaces and forms

A workspace groups forms with the people and device keys that work on them. Forms in one workspace share nothing else: each has its own questions, quality checks and data. When you have more than one, switch between them with the workspace menu at the top of the page. New workspace (owners and managers) creates one; two workspaces of one organisation cannot share a name.

Who can do what

Owners do everything in the organisation, including managing users.
Managers design and deploy forms, issue device keys, approve phones, edit quality checks and export data.
Reviewers read data and review quality flags; they cannot deploy, delete or collect.
Collectors only collect, with Joripo Collect or web forms; they have no console.

The full documentation

These help pages explain each screen in the words on it. The documentation goes further, section by section: how each feature works and who may use it, every quality check explained, the function reference built from the compiler, security and privacy (including what is not yet encrypted or proven), running your own server, troubleshooting and a glossary. It is public, needs no sign-in, can be searched and printed, and says under a page's title when what it describes is partly built or still being finalised.