Conventions Bi-weekly Call: April 25th - Farm2Data demo discussion, USDA PCSC updates

Conventions
1

Ongoing discussion of visual layout & UI changes from dev call:

  • Is there a way to make uploaded images appear better in this version of farmOS? V1 used a drupal module to have a gallery-style view
  • Limited by our budget constraints - should we put a proposal out on the forum for UI/UX specialists & fund via openCollective? Have to balance b/w ideal vs practice in terms of maintenance and updates.

Agenda items:

  • Grant’s work related to conventions / farm2data demo
  • PCSC Conventions (overview)
  • Plans for USDA

Farm2data demo

Conventions are still background for Grant, but thinking about their relationship (e.g. with Pasa data)

  • Farmdata2 module with forms (made for mobile at point in time when you’re performing it) - added UI elements for incrementing/decrementing
  • Equipment/soil disturbance (required for SHBS) - incorporated into form for seeding rather than having them as two separate entries
  • Creates all logs & assets for single operation when submitted (does not create field geometries, but if you have one associated with the plant asset you’re referencing, connects - intend for it to be predefined)
  • Good example of narrowing farmOS options based on your user type → farmer needs

Potential for prepopulating lists? Might be a good part of config setup to choose from available lists based on relevance (lists are extremely large)

  • Value of creating friction around introduction of new terms - constraining based on your known ontology list
  • Dropdown prioritizing what’s been used previously/frequently? Based on likely date? Specify external_uri ?
  • Hugely preferable for farmers / on mobile to not have a long list to navigate
  • Could be a farmOS module that could connect to external lists (aka Pasa Lists module with UI for picking which types to pull in)
  • Also potential for farmOS Setup Wizard module - could guide you through including the plant lists relevant to a user (pasa’s, fedco’s, whatever)

Philosophically interested in limiting scope to task-based elements that farmOS doesn’t provide

We need extant lists, & we need either list standardization or wrapper API in farmOS to map from lists

  • These lists need to be published, versioned, & accessible via API
  • We’re really close to getting this to where everyone sees how to get from these points to a generalizable way of managing this! :smiley:
  • Within our-sci module, have conventions module - could experiment with this for Setup module

PCSC Conventions (overview)

  • 2 outcomes from oakland convening, first is concept of Evidence to Claims engine (championed by Fibershed, IC-Foods, openTEAM thru Marketplace Working Group)
    • Good fit for conventions work related to outputs
  • Second is workbook automation for PCSC Workbook - Problem of collecting information for multiple purposes but that has to be entered in a wildly specific format for USDA reporting
    • Sam @ Qlever has been running with this to create a headless backend to generate workbook → creating minimal viable fields data model w validation, timed reporting simplification, reducing duplication of entry

Will be cool to hear from Pasa as a potential combined use case for SHBS & PCSC data entry needs (& for them, interesting because their data needs are driven primarily by SHBS and secondarily by PCSC, which is not the case for many groups doing data collection)

Next big convo - USDA conversations around Plans - using farmOS UI for interacting with farm data around potential changes

2 Likes