Dashboard

[qlands]

We need to create an automatic way (script) to gather statistics from trials. For example, the number of farmers that finished the trial by crop. For this, we need to perform a series of tasks. For example:

• Mark / indicate in the platform that a project is not real (part of training, a test, etc). Without user interaction (not a check in the interface). There are some options that we can discuss
• Assign each technology a crop. Connected to #243 .
• Define a way to know if a trial has finished. At the moment we don't have an automatic way to know this.
• Define what statistics we would like to get and the assumptions associated with each statistic.

[jacobvanetten]

We should not extract trial statistics directly, but generate an intermediate product, a table, from which we can first curate (remove certain projects that are not proper use of the platform, etc.) and then extract different statistics, such as number of farmers per crop, number of projects per country, number of farmers per year, etc. Having this intermediate table will also allow us to do more complex analysis (farmers per year per country, for example). We may have changing needs over time.

This intermediate table could have each project as a different row, and the following columns:

• Project title
• Project collaborator
• Project collaborator email
• Whether the project is a test or not
• Country
• Crop
• Technology type (varieties, etc.)
• Start date (day, month, year) = first farmer registration
• Number of farmers targeted
• Number of farmers registered for the project
• Number of trial plots/farmers successfully completed (definition of 'completed' should be discussed)
• End date (last field data entered)
• Centroid of GPS points (are various centroids if the project is spread across a large area) or subnational units covered -- for mapping purposes

This table can then be the basis for (part of) dashboard, maps, etc.

[BrandonMrBot]

@jacobvanetten

Update

Columns already added to the table:

• Project title
• Project collaborator
• Project collaborator email
• Country
• Start date (day, month, year) = first farmer registration
• Number of farmers targeted
• Number of farmers registered for the project
• End date (last field data entered)
• Centroid of GPS points We have 2, one for registration and another one comes from the data collection moments (Depends on the project has localization questions and the minimum number of submissions to be considered is 5).

Columns to be discussed:

• Whether the project is a test or not
• Crop
• Technology type (varieties, etc.)
• Number of trial plots/farmers successfully completed (definition of 'completed' should be discussed)

Possible solutions

• Crop

  1. Currently, we have made it mandatory to assign a crop taxonomy when creating a technology.
  2. For the technologies already created, we propose to generate an interface that tells the user to assign them a crop taxonomy in order to continue using ClimMob.

• Number of trial plots/farmers successfully completed To determine whether a trial was successfully completed, we propose: On-Farm testing - Packages registered to users should be checked in each data collection moment that is open or completed, if the package appears in each of them it is complete, if not it is incomplete. Consumer/Market testing - If the package is registered it is complete.

We need more information

• Whether the project is a test or not
• Technology type (varieties, etc.)

[BrandonMrBot]

@jacobvanetten

An additional proposal is that the same table is automatically inserted into apache supertset and have a dashboard that allows to generate graphs with the data, this is an example:

[MarManrow]

MrBot generated a series of dashboards that will be published/shared as an online report. Access to the report is only open for 1000FARM leaders at the moment. The team leaders are revising the report and will provide feedback before 11/10/24.