Conventions call April 10th - Documentation walkthrough

Conventions
1

Mike, Greg, Rose, Juliet, Vic

Agenda:

  • Forward-facing conventions documentation
  • Calendar clearing - the GOAT community calendar is the real one
  • Catch vic up on anything missed in Conventions world in the last 3 months :melting_face:

Bridge funding to work with Litefarm on Canadian GHG calculation tool, want to connect to CoolFarmTool - building an aggregation back-end dashboard to generate GHG estimation for their farms
  • Using CFC rather than 1-1 translations - and coming up with new conventions along the way

Possible collaboration with Dr. Pearse & Point Blue, looking for funding to preserve development of Crop-C module in farmOS → California conservation district use

  • Similar data needs as Conservation Desktop, but resource conservation districts ask the question starting from farmer needs → looking for funding that could apply rather than starting from existing funding opportunities & modifying farm plans to fit
  • Looking to decrease turnaround time & lower software costs
  • Potential for PODS team to share findings

Walk thru new documentation -

What can we bring in from PODS or other writing?

  • Need to develop “Use Common Farm Conventions" section - should have separation between new & existing projects & steps
      1. Tools for creating data dictionary & how to use
      1. Mapping & finding what doesn’t have a match
      1. Determining what needs a new convention
  • How’s Baserow going? Any mapping updates from Emily’s process?
    • Rose - as an airtable non-user/hater, really enjoying baserow.
    • Juliet - not strong scripting availability
    • Api-first rather than UI-first
    • Importing an airtable direct to baserow worked - but this table is entirely lookups so had to re-link
    • Will fail to import with any broken links - but otherwise can export & import anywhere in baserow verse

  • want to export baserow templates and make them a resource (like Juliet did for Modus lab methods library)

  • could provide flattened CSVs as a resource also

Proposal: Current documentation is available through these links in repo in .readme- collection link, flattened CSVs, etc. Greg thinks this should all be available as part of documentation - thoughts?

  • Links should autopublish to readable documentation - i.e. add a link on each page to download as data dictionary / flattened code etc

  • Rose would like descriptions under ‘asset’ - e.g. “we use assets because of farmOS’ - link to farmOS data model page - but likely not in the nav bar
    Is dev documentation going to be the blog post from Octavio?

    • Rose will find both existing posts & share to Greg, Greg will put those out there
    • Would like to describe design pattern, rationale, justification
      • Lots of good vis from pods report (which is COMING SOON FOR THE PUBLIC)

  • Needs licensing and terms of use up front

    • Anything about MODUS needs to acknowledge their terms of use

  • Landing page should have everything - from Contribute page, from Readme, in a graspable way (there in Greg’s local version)

“Every time I talk about conventions, it’s easier” TRUE! It’s working!

Examples - have the PASA SHBS, USDA - want to add images & descriptions to those

Juliet likes the size of the header on the main page - on other pages the difference between header text size and other text size are way too different (seconded & thirded)

Collapse all / expand all would be nice (juliet says critical)

Future user testing session?

  • Maybe could happen with Keren as an HCD session but is unlikely to be pushed by OT given The State of Things
1 Like