Versions Compared

Key

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

Recording link: https://ubc.zoom.us/rec/share/6h-tLPMnwBOv0oaWQBTo0-xGiYxcvO1tPBlVtTA2YQZCJ-vgdYop9U-TmXR4JKmE.VPNLgcA94RMYrFVAxsvMHnLd_7ZGLmwYMX4aUaTYW1CPFOofkNlysDd_1m6VYsasssmil_frd0qvMW8p.CbKb54qOlZq1GhSj

Passcode: gKrD9ht@.Mn?fq0L

Agenda

  • User account modification and deletion

    • Our data policy states that the user should control their own data. The lack of ability of a user to delete their own data / account goes against this policy (at the very least to get their data deleted within 24 hours upon request; ultimately to control this on their own)

      • Upon request is enough for compliance

    • How common are these requests and how much time does it take for the team to do it manually?

      • Industry standard might be to intentionally create a little bit of friction here (David: but is this a standard that we are aiming for?)

    • What about farm deletion (rather than account deletion)? Testing farms are made all the time and actually pollute our data analysis

      • Should not be restricted

      • Cleaning up test farms (even from our end) to prevent data dilution is a different situation and maybe the purview of the data team

      • Also a needed feature for correcting having set the wrong location for your farm

      • Farms are technically easier to soft-delete (not an option with users)

    • As long as we cannot trace the data back to the user that should be enough for our data policy

      • The strictest data policy only requires anonymization

      • Is farm address always personally identifiable? Yes. But latitude and longitude are okay

    • What should the process be for now?

      • We should follow what’s in the data policy right now (but this is hard-delete)

      • Our precedent has been soft-delete and ignoring the farm for the purposes of data

      • Hard-delete without a user-initiated flow with warning modal also makes it easier to get into a situation of not being able to undo

  • Changing user email

    • How are we verifying the validity of this request

    • This particular request is a bit edge-casey (request was not user-initiated at all, but is still very likely completely valid)

  • Action items Larisse Cavalcante and David Trapp , two tickets about:

    • How do we handle deleting information (farm, account)

    • How do we handle changing personal information (e.g. email id AND farm location)

    • Divya Chayanam to investigate wording of data policy

  • Issues with setting farm location – the original location cannot be changed, but is crucial for data analysis purposes (e.g. to calculate relationship between biodiversity and distance to urban centre)

    • These incorrect farm locations may still be associated with correct field/map locations

    • Action items: Larisse Cavalcante to communicate to Prof Khanh

  • Short whole-team discussion of animal sprint estimations

...

  • Smart irrigation

  • Animal movement task

Discussion points

  • Animal movement task

    • Should the user be able to create a movement task without specifying a “to location”?
      - Yes. Loïc will add a checkbox that allows the user to create a task without a “to location” if checked.
      -> It’s not possible due to the database design of the task, so movement tasks shouldn’t be created without location.

    • Add additional conditions to allow the retirement of a location?

      • Jira Legacy
        serverSystem Jira
        serverId815f41e5-e5fb-3402-8587-82eccc3ffab0
        keyLF-4484

      • Jira Legacy
        serverSystem Jira
        serverId815f41e5-e5fb-3402-8587-82eccc3ffab0
        keyLF-4485

  • Smart irrigation
    https://lite-farm.atlassian.net/wiki/x/CgB7ZQ
    https://docs.google.com/presentation/d/1E7IuSzw0_qL2423bww_S4_-25zXwQj4k/edit#slide=id.p1

    • Map

      • How should we add multiple sensors?

      • The new side-by-side layout:

        • Anto will investigate feasibility and ETA.

        • Options:

          • 1. Stick with the current layout

          • 2. Use a combination of the current and new layouts

          • 3. Migrate to the new layout

      • Are layers necessary?

        • The JSON file is not human readable.

TO DO

Task

Owner

Due date

Notes

...