Proposed use cases:
Our Email q’s answered:
What is the current state (how is data collected, stored, transformed, shared) and what are the gaps which FarmStack will help address
Data is collected on a seasonal basis (twice a year) using an in-house customized system called e-Agrology (see short video here). The main gap Farmsatck will help address is sharing these data with donors (private companies such as Kellogg, Bimbo, Nestle, Heineken and others) including personal identifiable information from which we have proper informed consents.
What kinds of data controls are required
We require matching the informed consents with individual data flows to be able to share only those lines that have consent.
We're keen to learn about the farming communities the projects work with - are there clear livelihood, climate, and / or gender considerations
Small and medium farmers (between 0.5 – 15 Has) depending on agriculture as main economic activity, located in the Bajio region where water is scarce. We work with them to put in place sustainability plans that can help them produce more with less impact (water-use efficiency, soil quality, air quality, etc)
Are there timeline constraints / requirements we'd need to commit to
Ideally, we would start the pilot this season starting from June-july to be able to share seasonal data by the end of the year with the donors.
Could we establish CIMMYT as an FS steward and eventually build internal capacity within CIMMYT to utilize FarmStack for X more use cases reaching Y more farmers and Z more partners, etc.
Yes. Absolutely. We have the team in place to be trained. Actually I heard from my colleague Steve Kemp within the Digital Initiative in the ONECgiar where I am Co-lead, that they are also having conversations obaout this so we coud put a set of global use cases togeher for this.
Is this a good opportunity for a sort of "showcase" collaboration that could lead to a beneficial communications and brand awareness campaign to support our advocacy work in this space
Yes
Call plan for May 18:
Hello, intros as needed
Dive into the more technical questions / clarifications from below
VNS:
Identify focal people from both sides, including who can address tech q’s for CIMMYT
What to do about the concept note with Dalberg? Focus on the use cases for now, or work on that concept note in parallel
Our detailed q’s (from Vineet’s mail, May 16, 2022 plus some from Andrew in red):
What data sets and who are providers/ consumers? - Sample if available would be good.
Providers = farmers, consumers = private companies and researchers (in the future?)
Ask for sample data
What is the current approach for collecting consent? Is there a need for our support there to build in consent manager to e-Agrology
Where do the data sets reside?
If servers then:
logistics of installing the FS instance
It is better that someone in our team is given access
They will need to maintain the access control and firewall setting
There are always surprises here - so if in the initial case this can be avoided then better
If public cloud like AWS/ Azure/ GCP then:
We create an test instance and give them the image
Data access:
If APIs - any documentation or swagger hub link
If DB query - then access to the DB test instance
If file - then who will be uploading
Data pipeline view:
What are the triggers for data sharing to start? - push vs pull
When is data collected – you said twice per year, when exactly so we can understand the timeline better
Custom applications to be written
0 Comments