Content Comparison

Fertilizing

Date: Date (required)

Locations(s):

• All fields

• Multi-select fields

• All greenhouses

• Multi-select greenhouses

Crop(s): [independent from locations]

• All crops

• Multi-select crops

Fertilizing product: (Required)

• Single select from product list

• … or create new

Quantity: Decimal (Required - ideally populated with estimate based on the total surface area selected from areas and crops)

Notes: Text (Optional)

Due date: Datetime (Required - default value of the day created)

Locations(s):

• All fields

• Multi-select fields

• All greenhouses

• Multi-select greenhouses

• … or create new

Crop(s): [independent from locations]

• All crops

• Multi-select crops

• … or add new

Fertilizing product:

• Single select from product list

• … or create new

Quantity: Decimal

Notes: Text (Optional)

Owner: UserRef (Required - assumed to be creator until overwritten)

Assignee: UserRef (Required - assumed to be creator until overwritten)

Requires at least one location or crop. If an area is selected, need to have a way to prioritize crops in that area.

Sasha Avrutina (Unlicensed) this is the use case where we’ll need to have a searchable location with category subtext, a la Amazon.

Crystal Arsenault (Unlicensed) other locations we should think about here?

Pest Control

Date: Date (required)

Locations(s):

• All locations

• Multi-select locations

Crop(s): [independent from locations]

• All crops

• Multi-select crops

Control method: Enum (Required)

• For responses “Systemic spray”, “Foliar spray”, or “Soil fumigation”, the following fields should be made visible and required:

  • Product: ProductRef (or add new…)

  • Quantity: Decimal (or not sure)

Pests: Enum (Required)

• Multi-select pests

Notes: Text (Optional)

Requires at least one location or crop. If an area is selected, need to have a way to prioritize crops in that area.

Harvest

Date: Date (Required)

Crop: fieldCropRef (Required)

• Individual crop (must show area in case the same crop is planted in multiple areas)

Quantity: Decimal (Required - ideally populated with estimate based on the amount of the chosen crop currently in the “to be harvested” stage)

Notes: Text (Optional)

Harvest uses: Enum (required)

• Multi-select harvest uses

  • For each harvest use, quantity is required

• … or skip

Sasha Avrutina (Unlicensed) the ideal situation for harvests is that the user could choose all of the crops they harvested in a particular harvest task and easily designate the bounty, uses, and harvest time for each. This seems complicated and difficult to hold in your mind (not to mention to visualize somehow), so I’ve opted for individual crop logs. If you can think of a better approach to describe the above - by all means!

Seeding

Date: Date (required)

Seeding location: locationRef (Required)

• Individual field or greenhouse

Crops to be seeded: [independent from locations] (Required)

• Individual crop / fieldCrop / crop plan

Seeding depth: Decimal (Required) [cm for metric, in for Imperial]

Seed spacing: Decimal (Required) [cm for metric, in for Imperial]

Rate: Decimal (Required) [seeds / m2 for metric, seeds / ft2 for Imperial]

Notes: Text (Optional)

For Summer 2021, seeding tasks may reference a crop plan and in that case they will inherit many of their attributes (e.g. crop, planting method, spacing, etc.) from that plan. Sasha Avrutina (Unlicensed) + Crystal Arsenault (Unlicensed) lets talk about whether this relationship should be mandatory moving forward.

Sasha Avrutina (Unlicensed) same comment as above.

Orangel Marquez will removing “Space width” from the seeding log break anything?

Field preparation

Date: Date (required)

Notes: Text (Optional)

Crystal Arsenault (Unlicensed) is Field Work an apt term for this?

Image Added

In the “new world” does this still only apply to fields?