ODK

ODK (Open Data Kit) is an open-source toolkit that helps organisations collect, manage, and use data, particularly in areas with limited internet connectivity. It enables users to create custom data collection forms on mobile devices and collect data offline. ODK Collect is the client-side app, and ODK Central is the server-side app.

To learn more about ODK, click here.

OpenG2P uses the ODK Collect App to collect and manage registrant information. The app works offline, allowing field registrations in areas without internet connectivity. The details are uploaded to ODK Central when the agent has internet access.

The app also has an integrated QR code scanning application to scan the ID card of the registrant. The scanning application automatically populates the KYC data of the registrant in the ODK form and verifies the digital signature to establish the card's authenticity.

Feature and functionality

Feature	Functionality
Offline Data Collection	ODK Collect allows users to collect data offline, which is crucial for field registrations in areas without internet connectivity.
Custom Forms	Users can create custom data collection forms tailored to their specific needs, enhancing the flexibility and adaptability of the platform.
Integration with ODK Central	The data collected using ODK Collect is stored and managed on ODK Central and allows organizations to access and analyze the data easily, even if it was collected offline.
QR Code Scanning	QR code scanning in ODK Collect allows users to quickly capture information from ID cards or other sources by scanning QR codes.
Digital Signature Verification	ODK Collect verifies the digital signature of scanned ID cards, ensuring the authenticity of the information provided.
Language Support
Calendar
Capture the Location Details

Feature

Functionality

Offline Data Collection

ODK Collect allows users to collect data offline, which is crucial for field registrations in areas without internet connectivity.

Custom Forms

Users can create custom data collection forms tailored to their specific needs, enhancing the flexibility and adaptability of the platform.

Integration with ODK Central

The data collected using ODK Collect is stored and managed on ODK Central and allows organizations to access and analyze the data easily, even if it was collected offline.

QR Code Scanning

QR code scanning in ODK Collect allows users to quickly capture information from ID cards or other sources by scanning QR codes.

Digital Signature Verification

ODK Collect verifies the digital signature of scanned ID cards, ensuring the authenticity of the information provided.

Language Support

Calendar

Capture the Location Details

Registration process

The three steps involved in the registration process using the ODK Collect App are:

ODK Central Configuration
Field Registration
Use ODK Importer or MTS Connector

ODK Central Configuration

A program administrator/manager performs the configuration. The program administrator/manager must perform these necessary configurations to enable the field registration agent to collect information on the ODK Collect App.

Program creation - To learn the steps, click here.
Create ODK form in ODK Central - To learn the steps, click here.
Provide ODK form access to the field registration agent - To learn the steps, click here.

Field registration

The field registration agent downloads the ODK form using the ODK Collect App. To learn the steps, click here.

After downloading the app, the agent visits the field and follows these steps for registration:

Captures the registrant's consent and records it.
Scans the ID card of the registrant to populate his/her KYC data.
Record further information such as household size, income, and home size.
Submits the registrant's information.

The submitted forms are uploaded to ODK Central once the agent moves to an area with internet connectivity.

Create ODK MTS Connector

ODK Importer

ODK and OpenG2P are connected through the ODK Importer module, which is specifically designed to import ODK forms of beneficiaries into OpenG2P Systems. The ODK Importer streamlines data transfer from ODK forms directly into OpenG2P Systems, eliminating manual data entry and improving data accuracy and efficiency in data management.

The ODK Importer module acts as a bridge between ODK forms and OpenG2P Systems, facilitating the integration and efficient management of data collected through ODK in the OpenG2P platform.

Based on the business scenario, a program administrator must create an ODK MTS Connector for each individual /group to map the ODK forms available in the ODK Central to the OpenG2P registry.

A program administrator must create an ODK MTS Connector to map the ODK forms in ODK Central to the OpenG2P registry. MTS Connector is the glue that holds ODK Central, MTS, and OpenG2P Registry together.

No Verification	Verification
A program administrator creates an ODK MTS Connector for individual/group to map the ODK forms available in the ODK Central.	A program administrator creates an ODK MTS Connector for individual/group to map the ODK forms available in the ODK Central.
The ODK MTS Connector regularly queries the ODK Central for the submitted forms. Whenever forms are available, the MTS Connector maps the individual/group KYC data from them.	The ODK MTS Connector regularly queries the ODK Central for the submitted forms. Whenever forms are available, the MTS Connector maps the individual/group KYC data from them and sends to MTS (MOSIP Token Seeder).
	MTS outputs an authentication token for each individual/ group's KYC data after performing ID verification. The authentication token is the proof of the registrant's authentication by the MOSIP ID Authentication system.
The ODK MTS Connector then calls OpenG2P Rest APIs to populate the OpenG2P registry with the individual/group KYC data.	Post-authentication, the MTS Connector maps the registrant information from the submitted form and the authentication token in the JSON format accepted by OpenG2P. The ODK MTS connector then calls OpenG2P Rest APIs to populate the OpenG2P registry with the registrant’s information in JSON object.

No Verification

Verification

A program administrator creates an ODK MTS Connector for individual/group to map the ODK forms available in the ODK Central.

The ODK MTS Connector regularly queries the ODK Central for the submitted forms. Whenever forms are available, the MTS Connector maps the individual/group KYC data from them.

The ODK MTS Connector regularly queries the ODK Central for the submitted forms. Whenever forms are available, the MTS Connector maps the individual/group KYC data from them and sends to MTS (MOSIP Token Seeder).

MTS outputs an authentication token for each individual/ group's KYC data after performing ID verification. The authentication token is the proof of the registrant's authentication by the MOSIP ID Authentication system.

The ODK MTS Connector then calls OpenG2P Rest APIs to populate the OpenG2P registry with the individual/group KYC data.

Post-authentication, the MTS Connector maps the registrant information from the submitted form and the authentication token in the JSON format accepted by OpenG2P. The ODK MTS connector then calls OpenG2P Rest APIs to populate the OpenG2P registry with the registrant’s information in JSON object.

Note: The OpenG2P registry accepts the individual or group KYC data only in JSON format.

To learn the steps to create an ODK MTS Connector, click here.