Recording link: https://ubc.zoom.us/rec/share/ayhKMuB6bF_f74o1pdjRgzLCkn2IvlosauTZiRF1qnXO7IITLNxl7TfL9Sn6x2LM.ztLSmp7uv-O5ExN5
Passcode: 7G*&nfBq
Agenda
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
)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 |
|---|---|---|---|