Joripo- Home
- Documentation
- Glossary
- Terms A to Z
Glossary
Terms A to Z
Every Joripo term in one list, from activity log to XLSForm, with what it means and where it is explained.
Joripo documentation · https://joripo.com/docs/glossary/terms
A to D
| Term | Meaning |
|---|---|
| Activity log | An organisation's own audit trail: one entry for every action that changes something, refused ones included. Configure › Activity log. See The activity log. |
| Anonymous access | A web form anyone with the link may fill in, without signing in. Off by default, per form. See Web forms. |
| API token | A personal credential (Authorization: Bearer …) with which a script reads the same files as the Export tab. Read-only. See Pulling data with a script. |
| Approval | The decision an owner or manager takes on a new Joripo Collect phone before it may collect. See Signing in on Joripo Collect. |
| Approved, rejected, awaiting review | A submission's review status. A submission nobody has reviewed counts as approved, and default exports hold approved submissions only. See Statuses and the review workflow. |
| Attachment | A file deployed with a form: an image, a sound, a preload CSV, a plug-in. See Media and attachments. |
| Back-check | A second, shorter visit by another team member whose answers are compared with the original interview's. See Every check explained. |
| Block | In garbling, a group of respondents (by factory and gender, for example) within which exactly the chosen share is assigned. See Designing a garbling scheme. |
| Case, case list | A household, person or place to be interviewed, and the workspace's list of them, sent to Joripo Collect with who gets each case. See Case management. |
| Connected computer | A computer running Joripo Desktop signed in as you, listed on Your account with Revoke. |
| Correction | A changed answer, with its reason, kept beside the submission; the submission as sent is never rewritten. See Correcting answers. |
| Dashboard | A field-monitoring page of KPI cards, charts, tables, maps and tracksheets built from a form's data. See Dashboards. |
| Data collector | The role that collects on Joripo Collect and web forms and never opens the console. See Roles and permissions. |
| Data Explorer | Monitor's page of a form's submissions: filters, labels in any language, and Export current data. See Submissions and the Data Explorer. |
| Data Exporter | Export files on the Export tab: every option of an export in one place. See Downloading a form's data. |
| Data key | The key that turns on encryption at rest, given to the server outside its data folder. See Keys and secrets. |
| Device address | The one public address the server puts in phone sign-in codes and collection links, checked to answer as this server. See Reaching the server from the field. |
| Device configuration | What every Joripo Collect phone applies (auto-send, swiping, GPS accuracy, the app lock …), set by the server's maintainer. See Server settings. |
| Device key | A credential in a QR code, for ODK Collect or a Joripo Collect app set up without an account. Belongs to one workspace and to no person. See Phones and device keys. |
E to K
| Term | Meaning |
|---|---|
| Encryption at rest | Sealing collected data on the server's disk and in its database with AES-256-GCM. Off until the server's data key is set. See Encryption at rest. |
| Enumerator | Whoever conducts the interview. Several checks need to know which question holds the enumerator. |
| External client | A person outside the organisation (a funder, a partner) given access to one workspace by a grant, with a role of its own and a password per grant. See Sharing a workspace with external clients. |
| Field monitoring | A workspace's monitoring projects: variables, derived variables, indicators, targets, rules, dashboards and tracksheets over a Joripo form, a SurveyCTO form or an imported file. See Field monitoring projects. |
| Finding (flag) | What a quality check raised about an interview, an enumerator or a form: open, resolved or dismissed. See Reviewing flags and the quality report. |
Form ID (form_id) | The identifier on a workbook's settings sheet. Fixed once the form exists; phones, exports and storage know the form by it. See Versions and form files. |
| Garbling | Randomised response: an assigned respondent's No to a sensitive question is recorded as Yes, so a recorded Yes proves nothing about one person while the true share can still be estimated. See How garbling works. |
| Grant | One workspace shared with one external client in one role: viewer, downloader, data manager, or form and data manager. |
| HFC (High Frequency Checks) | Joripo's 28 quality checks, run on each interview as it arrives or over a whole form on demand. See Every check explained. |
| Identity access | Seeing a workspace's identifying answers as they were given. Owners always have it; an owner gives it to particular managers and reviewers. See Identity access and privacy. |
| Identity map | Each pseudonym of a workspace with the answer behind it, made on request for people with identity access; every download is recorded. |
| Index | The database's record of what the storage root holds. It can be rebuilt from the files. See The database. |
| instanceID | The identifier a phone or web form gives each submission. A re-sent submission with the same instanceID never overwrites the stored one. |
| KEY | The export column identifying a submission (and, in the long format, a repeat instance). |
| Key custodian | A person an owner names who may open a garbling scheme's sealed vault. See How garbling works. |
L to P
| Term | Meaning |
|---|---|
| Long format | An export with one file per repeat group, each row one instance, joined back by PARENT_KEY. See Repeat groups and the long format. |
| Maintainer | Whoever runs the server, with a sign-in of their own to Server administration. Not a role in any organisation. See Maintainers and their sign-in. |
n_flags | The number of quality findings on a submission, in the Joripo export layout. |
| OpenRosa | The standard protocol phones use to list forms, download them with their media, and send submissions. Joripo serves its own endpoint, so ODK Collect works unmodified. |
| Organisation | One customer of a Joripo server: its people, workspaces, forms, data and plan. Nothing crosses from one organisation to another. See Organisations and workspaces. |
| Plan | An organisation's limits on forms (firm), submissions and storage (soft). See Plans, limits and usage. |
| Preload | Values a form reads from an attached CSV or server dataset with pulldata() or search(). See Server datasets and preloads. |
| Pseudonym | What someone without identity access sees in place of an identifying answer: P and ten characters, the same for the same answer across the workspace, and not reversible without the workspace's key. |
| Purge | Deleting a form's submissions by date or key after typing how many, always with a verified backup and an entry in the log. See Purging submissions. |
Q to S
| Term | Meaning |
|---|---|
| Quick tunnel | A free Cloudflare tunnel that gives a server on a laptop an https address, new at every start. See Reaching the server from the field. |
| Quota | A target number of interviews per stratum, tracked on Monitor. See Enumerator scorecards and quotas. |
| Restricted workspaces | An organisation setting that limits managers and reviewers to the workspaces they are assigned to. See Roles and permissions. |
| Review workflow | A form setting: on, every new submission arrives awaiting review. See Statuses and the review workflow. |
| Roster | In garbling, the list of people a scheme covers, stored encrypted. |
| Round | One wave of a panel: starting the next round makes every case due again. See Rounds, progress and updates from data. |
| Scheme | A form's garbling set-up: which questions, the rate, IID or block, how answers are captured. Frozen before fieldwork. |
| Scorecard | An enumerator's submissions, findings, median duration and last activity, side by side with the rest of the team. |
| Secret key | The server's SECRET_KEY: signs sign-ins, gives the server the identity phones recognise, and seals the garbling vault. Set once. See Keys and secrets. |
| Server administration | The maintainers' control panel (/admin) above every organisation; not found for everyone else. See Server administration. |
| Server dataset | A table held on the server and attached to any number of forms, updated in one place. See Server datasets and preloads. |
| Server name | An organisation's short name (riverbank-research), typed in Joripo Collect and part of ODK Collect's server URL. |
| Storage root | The folder of plain files that is the server's record: every form version and every submission. See The storage root. |
| Stratum | The category quotas are counted in (a district, a sex, a treatment arm), taken from the question mapped as the stratum. |
| Submission | One sent interview: its XML, its attachments and a record of how it arrived. |
T to X
| Term | Meaning |
|---|---|
| Tester | The console's browser preview of a form, on the same engine as web forms and Joripo Collect. See Testing a form. |
| Text audit, audio audit | A record of how long each question was on screen, and a recording of the interview, made by the device. |
| Tracksheet | A field-monitoring table of the sample list against what has been collected: who was reached, with what outcome, and what is left. See Tracksheets. |
| Version | A form's settings-sheet version: one whole number, higher than the deployed one, with the same number of digits. Every deployed version is kept. |
| WIDE | The SurveyCTO-compatible export layout: one row per submission, repeats as name_1, name_2. See File formats, Stata and SPSS. |
| Workspace | A group of forms with the people and device keys that work on them, inside an organisation. Its forms share nothing. See Organisations and workspaces. |
| XForm | The XML form definition phones run. Joripo compiles it from the workbook at deploy time and keeps it with every version. |
| XLSForm | The spreadsheet form standard Joripo reads, SurveyCTO-compatible and ODK workbooks alike: survey, choices and settings sheets. See Forms and XLSForm. |