this short article is followed by test kinds, dataset definitions and sample information conserved in this folder.
A common use of SurveyCTO is to keep track of farmers in the agricultural sector. An average situation is where an agricultural programme officer leads an exercise for an intervention aimed at training neighborhood farmers on how best to implement a farming technique that is new. This usually involves keeping a workshop with chosen farmers in a locality. The programme officer wish to keep tabs on most of the attendees as well as in due program follow through together with them to be sure of the way they are progressing with all the classes learnt. The officer shall might like to do the immediate following:
- Join farmers.
- Record the clear presence of farmers at meetings.
- Improve farmers‘ details.
- Delete accurate documentation of the farmer.
In this specific article, we shall walk through an example workflow for handling a listing of farmer beneficiaries making use of SurveyCTO.
|This workflow is broadly applicable, illustrating simple tips to create and continue maintaining a listing of a number of other things regardless of farmers ( ag e.g. schools, latrines, medications, or clinics) in a host dataset through type submissions. When your usage case isn’t farming, you are able to nevertheless learn one thing.|
They are the files which you shall want to deploy in your host to evaluate this workflow:
|Form definition||– Farmer management, – Farmer attendance|
|industry plug-ins||– table-list.fieldplugin.zip|
|Server dataset definition||– farmer_list.xml|
The test kinds, dataset definition and test data are conserved in this folder as the table-list industry plug-in can here be downloaded from . Follow these guidelines to deploy them in your host system.
Features that permit this workflow
This usage case utilizes the next attributes of SurveyCTO:
Pre-loading utilizing pulldata()
Pre-loading option listings search( that is using
Server dataset publishing
Knowing the workflow
The workflow is made around two forms plus one host dataset. You will understand why workflow well trying it in training, when you have precisely implemented it to your SurveyCTO host. Each action that is major the workflow is described below.
Farmer management form
This type is employed to:
- Register a farmer
- Up-date farmers details
- Delete an archive of a farmer
Registering a farmer
This type will likely be filled in one or more times for every single specific farmer. Whenever completing the proper execution, find the вЂњRegister a fresh farmerвЂќ action and go into the farmers details. The info in regards to the towns and wards is pre-loaded from a connected CSV file („zambia_wards.csv“).. The search() function can be used to filter right down to the appropriate ward based in the chosen city. After the farmer details are finished, conserve and submit the proper execution. Each and every time the proper execution is submitted the farmers info is posted into the вЂњfarmer_listвЂќ server dataset („farmer_list.xml“).
Upgrading the farmer
To update the important points of the farmer on record, select the вЂњUpdate documents of a farmerвЂќ action. This lots record of farmers through the вЂњfarmer_listвЂќ dataset and shows it in a dining table utilising the table-list industry plug-in. Find the farmer and edit the fields that are required. The fields are published with the updated details upon saving and submitting the form.