Description
The planting task describes the details of putting a crop into the ground. It describes whether the crop is being put in the ground as a “seed” or as a “seedling or planting stock”. It also describes the details of how it should be planted - collectively the “planting method”. The valid planting methods are:
Broadcast
Row
Bed
Individual
Container
Planting tasks cannot be made by themselves, rather, they are a byproduct of creating a new crop management plan.
Creation restrictions
May not be created outside of the crop management plan creation flow.
Creation attributes
None, clicking to create a planting task will display this redirect (see below) and require the user create a new crop management plan.
Completion attributes
The following attributes are new when marking a seeding task as completed.
Attribute | Data type | Required? | Example data | Notes |
|---|---|---|---|---|
Actual seed required | Integer (w/ unit) | No | 4500 | 0 - 9999. Ideally allows the user to choose either mass or volume Unit displays. Must be pre-populated with the value entered in “Estimated seed required” during crop management plan creation. The actual value must not overwrite the estimated. Both should be saved to the database. |
Did you have to make any changes to this task? | Enum: {“Yes”, “No”} | Yes; defaulted to no | All other fields are read-only unless “Yes” is selected. “Continue” becomes enabled after “Yes” or “No” is selected. |
All attributes related to the planting method chosen during crop management plan creation should be displayed. Depending on the method, the attributes that should be modifiable are outlined in the stories below:
Method | Stories |
|---|---|
Broadcast | |
Row | |
Bed | |
Individual | |
Container |
The assignee should not be able to modify the method itself, but can modify the attributes within the method such as “Planting depth” or “Seeding rate”. For row and bed methods, the “Additional” guidance sections should also be shown on the same page.
Migration guidance
“Seeding” logs with the following type values should be migrated as shown.
Previous value | New value | Notes |
|---|---|---|
Date | Date | |
Locations | Location | For each location, a separate completed seeding task should be created. |
Method: “Legacy seeding” | Migrated seeding logs should have the type “Legacy seeding”. | |
Status: “Completed” | ||
Seeding depth | Seeding depth | Must be converted from cm to user’s designated unit system |
Seed spacing | Plant spacing | Must be converted from cm to user’s designated unit system |
Space width | Space between beds | Must be converted from cm to user’s designated unit system |
Rate | Planting rate | Must be converted from seeds / m^2 to the users designated unit system |
Notes | Completion notes |