Open Collective
Open Collective
Loading

LiteFarm<>CFT<>FarmOS Integration

PROJECT

Use the Common Farm Convention (CFC) as a common data transfer standard to integrate LiteFarm and FarmOS with Cool Farm Tool (GHG Model)

About



Motivations


This project helps Our Sci, and the broader GOAT community, maintain key staff and core competencies through a funding drought caused by the federal government's abrupt change in policy as we shift towards more sustainable external funding sources and fully sustainable market-oriented funding strategies.

The work proposed is to use the Common Farm Convention (an open farm records standard built on FarmOS's data model) to connect Cool Farm Tool (a green house gas calculator) to LiteFarm (an FMIS) and FarmOS (an FMIS). This particular work package lays the groundwork for collaboration among key members of the Community of Organizations, who are attempting to collaboratively orient their products towards market-driven and revenue positive open source ag tech products.

Taken together, this project not only helps maintain core talent but supports the bigger collaborative play to ensure that talent produces meaningful impact.

Budget and Funding

Funding for this work is coming from a few sources. The CFT and LiteFarm Integration Work is covered by the Bridge Funding Proposal described below. The Convention Documentation work is covered by the remaining PODS Cooperative Contract.

Up to Date Budget here (PODS Cooperative work not included - $10k for documentation):

Description

This supports four key staff (Rhiddi, Rose, Brian or Will, and Pedro) to complete four key tasks:

  1. Mapping between Cool Farm Tool's (CFT, https://app.coolfarmtool.org/) API and the Common Farm Convention (CFC, https://our-sci.gitlab.io/conventions/common_farm_conventions/wiki/docs/news/), along with adding any additionally needed conventions to include data that may be needed by CFT not already present in the CFC.
  2. Mapping between LiteFarm's API and the CFC.
  3. Building a minimum implementation in LiteFarm to run and view CFT model runs.
  4. Building a minimum implementation in FarmOS (API overlaps with the CFC) to run and view CFT model runs.

Short Term Outcomes / Benefits

  • Completed data mapping between LiteFarm and CFT (using CFC as the data transfer standard), to get GHG scoring. Minimum UI implementation in LiteFarm to generate and display a CFT score for producers and researchers.
  • Completed data mapping between FarmOS and CFT (using CFC as the data transfer standard), to get GHG scoring. Minimum UI implementation in FarmOS to generate and display a CFT score for producers or those using producer-supporting organizations.

Long Term Benefits

  • We add key data to the CFC so that the next integration (with other models or services) is easier - specifically this can be used as part of a future LiteFarm <> Open Food Network integration and RegenScore integrations.
  • We increase the value of future integrations by having an important integration already complete (CFT as data transfer standard).
  • We can now clearly scope the best structure to generalize these integrations through completing one start to finish. This scoping will result in the API Switchboard libraries that can be used locally or as a backend web service.

Importance as bridge funding

Rose, Rhiddi, Brian and Will were both affected by the loss of PCSC funding through OpenTEAM and Pasa, as well as lost future contracts through AxiLab. Pedro, while located in Spain, also lost significant internationally directed funding due to the shutdown of USAID. They have long-term and high value skills that would be a significant loss to the community. This provides a bridge for their employment through April, at which point we have additional opportunities focused around this ongoing work.

Scope of Work

Background


There was previous work done on the Cool Farm Tool (CFT) Integration, primarily from Emily's efforts a few years ago. There are some existing works in progress, such as the air table data dictionary mapping of the CFT with the Common Farm Conventions (image below). Emily's data mapping provides a precise list of what data needs to be mapped and the modifications needed to do so, which will result in new child conventions to the CFC. Additionally, we scoped the completion of this work through the now defunded OpenTEAM PCSC with Hannah at UBC in Spring 2025.

Visual Project Plan


Big picture map of the work with questions and stopping points. We'll keep this up to date and use it to make sure we're sticking to the plan!

2025 Cool Farm Tool Integration Scoping:


Given the existing scope, the desire to complete the work with LiteFarm and offer of Riddhi and student support, a long-term interest in collaboration through the Community of Organizations, and the prospect of bridge funding, we felt that moving forward with this integration would be the best use of our funds and time. As such, this is an initial scoping of what needs to be done and prioritized to move forward.

Project Management


The project is actively managed and updated using Gitlab here

Our team

Contribute


Become a financial contributor.

Financial Contributions

Custom contribution
Donation
Make a custom one-time or recurring contribution.