You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: use-cases/farmer-registry/README.md
+22-12Lines changed: 22 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,10 @@ A country's Department of Agriculture requires a registry of farmers to support
15
15
3. Decision Support: Empowering policymakers with real-time data for better decision-making in agricultural programs and public expenditure.
16
16
4. Data exchange: Ensuring seamless integration with other systems and data sources to enhance functionality and scalability
17
17
18
-
## OpenG2P Solution and Architecture
18
+
## OpenG2P solution and architecture
19
+
20
+
The Farmer Registry is a comprehensive solution to capture, manage, share and analyze farmer data efficiently to provide a digital-first approach to farmer identification and management. It contains:\
19
21
20
-
The Farmer Registry is a comprehensive solution to capture, manage, share and analyze farmer data efficiently. It contains:
21
22
22
23
* Implementation of an offline ODK-based data collection system integrated with OpenG2P
23
24
* Implementation of an online Registration Portal
@@ -32,11 +33,22 @@ The Farmer Registry key functions include **Data Collection, Data Validation and
32
33
33
34
OpenG2P supports the **Data Sharing** function by sharing data from the registry in a standardized manner. Analytics and Reporting includes reporting and dashboards using Apache Superset and the Reporting Framework, real-time system health monitoring, and revision history to track changes and generate reports.
34
35
35
-
## Key Processes and Features
36
+
## Solution approach
37
+
38
+
Key objectives achieved include:
39
+
40
+
***Structured registration**: A comprehensive registration system that captures essential farmer details such as personal information, land ownership, and farming activities.
41
+
***ID authentication**: The system supports biometric or OTP-based authentication to validate farmers.
42
+
***ODK-based data collection**: Offline and online data capture capabilities using ODK (Open Data Kit) for field-level data collection.
43
+
***Configurable deduplication**: Ensures unique farmer records through configurable deduplication based on IDs or biometric data.
44
+
***Registration portal:** An intuitive interface for the enrollment agents to enumerate farmer and their household data.
45
+
***Interoperability**: Designed to integrate with other systems like subsidy management, and agriculture extension services.
46
+
47
+
## Key processes and features
36
48
37
49
<details>
38
50
39
-
<summary>Data Collection</summary>
51
+
<summary>Data collection</summary>
40
52
41
53
*_Offline assisted registration_: Offline assisted enumeration enables us to reach remote farmers who may not have internet connectivity. Data is collected by a field enumerator using the ODK application on tablets and stored in ODK Central, and then imported into the farmer registry. The enumerator's login details are also stored within the registry, to monitor the data collection.
42
54
@@ -50,7 +62,7 @@ OpenG2P supports the **Data Sharing** function by sharing data from the registry
50
62
51
63
<details>
52
64
53
-
<summary>Data Validation and Enrichment</summary>
65
+
<summary>Data validation and enrichment</summary>
54
66
55
67
*_Farmer ID generation_: Unique Farmer ID is generated to ensure accurate and efficient tracking, as well as to enhance data consistency and integration with other systems. The ID is generated using MOSIP's sophisticated ID generator which applies multiple rules before assigning an ID, and the generation process is managed through a background task system that handles status updates, retries, and eventual confirmation of ID utilisation.
56
68
@@ -68,15 +80,15 @@ OpenG2P supports the **Data Sharing** function by sharing data from the registry
68
80
69
81
<details>
70
82
71
-
<summary>Data Sharing</summary>
83
+
<summary>Data sharing</summary>
72
84
73
85
_Data Sharing_: Data stored in the registry can be easily shared in a standardized manner, making the information reusable by third parties for farmer and agricultural insights.
74
86
75
87
</details>
76
88
77
89
<details>
78
90
79
-
<summary>Analytics and Reporting</summary>
91
+
<summary>Analytics and reporting</summary>
80
92
81
93
*_Reporting and Dashboards_: OpenG2P's monitoring and logging tools allow program administrators to track the progress of the registry, and keep an eye on system health. They can do this through:
82
94
1. Visual dashboards for monitoring using Apache Superset
@@ -87,16 +99,14 @@ _Data Sharing_: Data stored in the registry can be easily shared in a standardiz
87
99
88
100
</details>
89
101
90
-
## Data Model
102
+
## Data model
91
103
92
104
* Basic details of the farmer and household - name, location, ID, education, etc
93
105
* Land area, parcel ID, geo-location, ownership details  
94
106
* Data on crop, livestock, inputs, access to finance 
95
107
* Membership and role in farmer organizations
96
108
97
-
## Deployment
98
-
99
-
## Reference Design
109
+
## Reference design
100
110
101
-
Pleas click [here](farmer-registry-reference-design.md) to know more about the referece design for Farmer Registry
111
+
Please click [here](reference-design-farmer-registry.md) to know more about the reference design for Farmer Registry
The OpenG2P Farmer Registry is designed to streamline the identification, registration, and verification of farmers in a structured and scalable manner. It aligns with the use case documented in [OpenG2P Farmer Registry Use Case](https://docs.openg2p.org/use-cases/farmer-registry) and provides a reference implementation based on OpenG2P principles. This reference design can be a base to start off your farmer registry implementation and further you may modify as per your farmer registry specification. 
4
+
5
+
## Use case 
6
+
7
+
Refer [Farmer Registry](./)
8
+
9
+
## Components 
10
+
11
+
Included The Farmer Registry solution comprises the following components, as reflected in the OpenG2P Reference Designs GitHub repository: 
12
+
13
+
*`g2p_farmer`: Core farmer registry model.
14
+
*`g2p_farmer_rest_api`: REST API for accessing and managing farmer data.
15
+
*`g2p_farmer_service_provider_portal`: Portal for service providers to manage farmer and household in their respective administrative area.
16
+
*`g2p_lock_unlock`: Functionality for locking and unlocking farmer records.
17
+
*`g2p_odk_importer_farmer`: Component for importing data collected via ODK (Open Data Kit).
18
+
19
+
## Source code
20
+
21
+
The entire source code for the reference design can be found in the GitHub [repository](https://github.com/OpenG2P/openg2p-reference-designs/tree/develop/farmer-registry)
22
+
23
+
## How to setup
24
+
25
+
Follow the developer installation guide provided for setting up OpenG2P on Linux: [Developer Install Guide](https://docs.openg2p.org/social-registry/developer-zone/developer-install/developer-install-of-openg2p-package-on-linux).
26
+
27
+
Once the OpenG2P setup is completed, proceed with the following steps specific to the Farmer Registry:
0 commit comments