Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Recording link: https://ubc.zoom.us/rec/share/HCcSpWuBtskLc5VPyf9XCyNjDoricsWhF0zIayhKMuB6bF_jjLkGG2dizeQ4b4bGbgRWrYhI0f74o1pdjRgzLCkn2IvlosauTZiRF1qnXO7IITLNxl7TfL9Sn6x2LM.btL10NrWexWE2VqDztLSmp7uv-O5ExN5

Passcode: ?@HMnz9Z7G*&nfBq

Agenda

  • Soil V2

    • Soil sampling task

      • needed to fill gap between soil amendment task

    • Product table

      • setting aside for now

Discussion points

  • Soil sample location points

    • Details

      • name (auto name eg sample #8)

        • editable?:

          • not yet, only available on task

          • not useful since soil samples are mixed together

      • location (Lat Lng)

        • editability

          • remove

          • is edit possible?

        • number

          • (count) soft-linked to next part of screen

          • what happens if you remove count when you go back to the pin screen?

          • maybe a warning?

          • why not hard link?

            • very similar to how when you create an area on map but user can edit the total area afterwards

          • swap the form screens? Why location needs to be first?

            • will explore but:

            • doesn't match litefarm task pattern

          • where can a point be added?

            • in one location to be linked to the field

            • on multiple locations

            • select multiple areas

            • outside of areas

            • is soil analysis accurate for area if selected outside area?

            • Got to let the farmer use some common sense if linking to an area they shouldn't locate outside it unless they know what they are doing - restricting it would be condescending

          • allow user to input coordinates?

            • no: coordinates are approximate

            • other apps do it better

            • it would be a lot of work to do it better

  • Multiple depths per soil analysis?

    • No: its an important fact they should all be at the same depth

  • Complete flow

  • Should you be able to create a follow up analysis task?

    • should we force create it – it seems valuable?

      • maybe not: For example a test - you might practice a test and not complete it

  • The person who creates the sample task would be better to understand when the results might come back?

    not the worker in complete flow?

    Movement task – overview + scoping

Discussion points

  • Movement scoping

    • We can switch the order of soil v2 and animals (to continue work on animals), but in order to do so we will have to deliver manure management

    • Justification for this switch

      • Animals is a more user-desired feature than soil version 2 (and one we have been promising for fall 2024 for a while)

      • To continue working on animals will also mean less context-switching for the development team

  • Looking at the movement task (again (smile))

    • Time is optional for movement task

    • Table “See detail list of animals to move” is a nice to have – but a higher priority than Initial locations if we had to pick just one of two

    • [Long discussion; see video]

    • Divya’s recap:

      • Move animal from point A to point B

        Option-1: We’re okay not knowing point A. Build as is. 

        Option-2: We assign location using the move task flow. Figure out terminology

        Option-3: Build a flow for assigning location for animal when it is created. Movement task is separate
        Option-4: Possibility of having point A editable? And not having location at all?

        • David brings up option 4 for those who don’t want to track every movement in LiteFarm but need to know the starting location of their animals for carrying out the task

      • Of these options, team has decided on Option 1 for now

TO DO

Task

Owner

Due date

Notes

...