Harvesting
- Lite Farm
Description
Harvesting is the act of removing the portion of a crop that is useful to humans. One example is removing a ripe apple from an apple tree. In many cases, harvests are then sold. However, there are many other harvest uses as well.
Many types of certifications, including Organic require recording all farm outputs (see Certifications, certifiers, and LiteFarm for more information). Harvests are the primary output of a farm and need to be documented.
Creation restrictions
Step | Restrictions |
|---|---|
2. Task date | None |
3. Task location(s) | Only crop enabled locations with active or planned crop management plans (on the date selected in #2) are shown. |
4. Involves crops? | Only active or planned crop management plans (on the date selected in #2) are shown. |
5. Task assignment | None |
Creation attributes
For each selected crop management plan:
Attribute | Data type | Required? | Example data | Notes |
|---|---|---|---|---|
Quantity | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Ideally allows the user to choose either mass or volume Unit displays. |
Harvest everything that is ready | Checkbox | No |
| This is like a “fill it up” at a gas station. |
Notes | Text | No | “This is the last CSA shipment with tomatoes, so just harvest as much as possible.” | Each crop management plan will have a notes field because each crop management plan selected will become its' own harvest task. |
Upon saving a harvest task, N harvest tasks will be created and assigned to the assignee where N is the number of crop management plans selected. By doing this, each task can be individually completed with its' specific harvest quantities and harvest uses. There is no multi-crop harvest completion flow in Q3 2021.
Completion attributes
The following attributes are new when marking a harvest task as completed. For the selected
Attribute | Data type | Required? | Example data | Notes |
|---|---|---|---|---|
Quantity | Decimal (w/ unit) | Yes | “15 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Not sure | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Sales | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Self-consumption | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Animal feed | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Compost | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Gift | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Exchange | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Saved for seed | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
Other | Decimal (w/ unit) | No | “3 kg” | 0 - 9999. Utilizes Unit displays for mass. |
All “harvest uses” inputs are optional, but they must sum to the Quantity input.
Migration guidance
“Harvest” logs should be migrated to be completed tasks with the attributes as shown.
Previous value | New value | Notes |
|---|---|---|
Date | Date |
|
Locations | Location | For each location, a separate completed seeding task should be created. |
Quantity (kg) | Quantity | I believe this is persisted in kg, but should double check. |
Harvest uses | Harvest uses | Custom harvest uses should be carried over as “Other” → “Custom harvest use”. Stretch goal if they’re available at the farms where they were created moving forward. |
Harvest use quantities | Harvest use quantity | Must be converted from cm to user’s designated unit system |
| Status = “Completed” |
|
Notes | Completion notes |
|
Other context