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: Joripo Collect

Joripo Collect is Joripo's Android app. It runs the same engine as the tester and web forms, works offline, and sends finalized forms when it has a connection.

1. On the phone, open this server's /app page (Get the app shows the address) and install Joripo Collect.
2. Sign in with the person's Joripo email and password (the eye button beside the password shows what was typed). A collector account is enough, and has no console access.
3. The phone appears under Joripo Collect devices. Depending on your policy it is approved at once or waits for an owner or manager to approve it.
4. Once approved, Get blank forms on the phone downloads the forms that person may fill.

See Phones and devices for approval, revoking a lost phone, and moving phones to a new server address.

Phones: ODK Collect

ODK Collect works with a device key. New device issues one, with its own QR code: in ODK Collect choose Add project › Configure with QR code and scan it. Treat the QR like a password: anyone who scans it can submit as that device. Forms shows which forms the key can fill; Revoke stops it, and keeps everything it already sent.

Web forms

Each deployed form has a web link (Share). Anyone you send it to fills the form in a browser and submits it to this server.

• With Allow anonymous form access off (the default), people must sign in to this server first, as a member of your organisation.
• With it on (the form's Anonymous access switch, or Change form settings), anyone with the link can fill it out.
• The Web data collection switch turns every web form in the workspace off or on at once; off, no link opens, whoever asks.

Datasets and anonymous web forms

A form that allows anonymous access gives a visitor its questions and its own media (images, audio), and never the server datasets attached to it, so its preloaded values are blank for them. To let such a form use a dataset, open the dataset's card on Design and choose Share with anonymous web forms.

• What becomes reachable without signing in: the dataset's whole file, as attached to the form. Anyone who has the link of a form that allows anonymous access and uses that dataset can download it, not only the row their answers look up. Share only a list you would publish.
• What it does not change: the dataset is not sent to anonymous forms that do not use it, and a form without anonymous access still asks everyone to sign in. Phones and signed-in data collectors receive the form's datasets either way.
• Never shared, whatever is chosen: the case list, a garbling enumerator sheet and any dataset marked as holding identifying data.
• Stop sharing with anonymous web forms takes it back at once: the next visitor who is not signed in cannot download it. Each change is recorded in the activity log.

Change form settings

Each form on Collect has Change form settings: click it to open, click again to close. Each switch changes what the web form does:

• Auto-detect browser language: opens the form in the respondent's browser language when the form has it.
• Finalize and accept incomplete submissions: lets a respondent submit with required questions unanswered, after confirming. An answer that breaks a constraint must still be corrected.
• Allow non-linear form navigation: off, only Next and Previous; Allow the Go To menu, Allow jump to start and Allow jump to end each show one of those controls.
• Allow skip to next: Options › Skip to next moves on without answering.
• Show location within groups: the line above the questions names the group the respondent is in.
• Override default form width: a width in pixels for a computer screen; a phone keeps its own.
• Allow start over, Hide login options (the Sign in link on an anonymous form) and Disable swipe navigation.

Hyperlink field references and Use legacy UI are not available: Joripo's web form cannot honour them, so they are listed but cannot be switched on.

If you are sending the link to many people, space the invitations out so not everyone arrives at once.

When a phone cannot connect

• Scanned, but no forms appear: the key has no form yet. Deploy a form, or check the key's Forms.
• The phone cannot reach the server: the server address in its settings no longer answers, usually because a tunnel restarted under a new address. The address phones use is shown at the top of Mobile data collection.
• A QR goes to the wrong server: the key was made before the address changed. Make a new key and scan again.

Case lists (panel and follow-up studies)

A workspace's Cases page (owners and managers) holds the households or respondents enumerators visit again. Enumerators find their cases under Manage cases in Joripo Collect.

• Who gets a case is its users column: full email addresses, or a username (the part before the @) when only one person in your organisation has it. A username two people share gives the case to neither; the Cases page says so, and so does every upload, the set-up wizard and Give them. Write the full email to be sure.
• The form's case field is its question of type caseid, whatever it is called (caseid, id, hhid): Joripo finds it by its type.
• The case table has a filter box under each column and pages of 100 cases. Click a case ID to open the case's page: where it stands for each form, who interviews it, its interviews, its notes and everything that happened to it.
• Notes on a case are kept with the writer's name and cannot be changed or deleted. Enumerators do not see them.
• The case list cannot be deleted while it is the case list: phones would lose every case. Choose Stop using it on the Cases page first; the data stays as an ordinary dataset, which can then be deleted.