Proposed use cases:
...
Our Email q’s answered:
...
Hello, intros as needed
Two different ways of interacting - CIMMYT w/ some projects in Mexico, then the One CGIAR digital initiative has some additional use cases (Rwanda, India, etc) \
Andrea leads M&E at CIMMYT, ICT for Ag, info systems for data collection, cleaning, ETL processes etc
Leads the e-agrology system
Jelle leads the bi-lateral projects, hub system in Mexico, localized innovation networks, sustainable agrifood systems program
Dive into the more technical questions / clarifications from below
VNS:
Andrea share data sample and informed consent form they have
Andrea to put us in contact with the developers to work directly with
Scope out basic product, big and small picture, costs, and share
Prepare initial agreement of collaboration - CIMMYT is the owner here (step 1), in parallel we do the concept note with Dalberg
Set up recurring call to move this forward, create the requirements in a solution sketch, then come to how we will execute, baseline targets, and costs associated
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
Potentially focus on the use cases and drop the concept note
Or, if we pursue the concept note - more closely tie it with these use cases, understanding the other potential challenges this same solution can address?
We need to look at the level of effort which will be required from our team and determine if it is feasible to pursue this first phase pro-bono, on this timeline. We’ll come back with some specific options.
...
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
Around 500 variables per plot
up to 3 crops per season
What is the current approach for collecting consent? Is there a need for our support there to build in consent manager to e-Agrology
Extension agent reads a general consent to the farmer when collecting the data
In order to share that data on to donors they must go back to the farmer one by one to collect additional consent from the farmers
Their need here is that sometimes the data requested by the donor is different - like relating yield with practices used etc, which needs specific informed consent
Maybe they can do a more general high level consent to share with 3rd party individually, but tbd. trying to get back to farmers with concrete benefits for sharing that data.
Agro-tutor is interface for the farmer, this will include privacy / consent built in >>> this is kind of a wallet, could push to it
Opp to build in SDK (data wallet, consent, etc)
Right now the donor has access to the general dashboards, but the outside access to the more dynamic dashboards need some control on the data sharing
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
Collection is May - Nov, by november have sharing in place
Custom applications to be written
...
Can we discuss the engagement in blog / social media? We can include a line on this in the collab agreement if needed, but we like to share these kinds of partnerships with our community
Outline it in the collab agreement and collaborate with their comms on messaging
VNS:
Shreya to share latest version of collab agreement w/ markups and notes
Add the list of tasks outlined to the agreement and share, it will take time
Andrea to share text of the consent form
DG team to put together the story boarding based on this
Andrea to get Vineet / etc in contact with AWS partner to look at SMS integration
Andrea to bring project team into the discussion to get their input on donor needs, consent mgr flow, interface with farmers etc
Vineet to provide some days / times which work to connect with these teams
1.5 hours for overview and tech architecture
~45 minutes for the project team to understand what the farmers / beneficiaries will get out of the process, Andrea to present
...