...
A: Perhaps not, but it doesn’t seem like too much of a burden given the user can bypass the historical planting method and just enter an estimated yield instead.
Q: Should we display estimated seed required and estimated yield for historical planting methods (e.g. where the crop is already in the ground and the user is documenting it after the fact)?
A:
Answered questions
Q: For seedlings or planting stock can we estimate any of the above dates from seeding date offsets?
...
A: Everything except broadcast.
Q: When should estimated yield be a required field?
A: Estimated yield should be required for all final locations (e.g. those that are planted and will not be transplanted, or those that will be transplanted to a second location for that second location). For initial locations (e.g. those that will be transplanted, but haven’t been yet) the estimated yield is optional. The reason estimated yield is required for final locations is because this number gives us the estimated revenues for the farm for the season. Farmers will use these estimates to make their purchasing and staffing decisions.
Q: When should estimated seed required be a required input?
A: Estimated seed should always be optional. This is a “helpful” calculation we can provide to the farmer, but isn’t used anywhere else in the system at present.
Q: Should we display estimated seed required and estimated yield for historical planting methods (e.g. where the crop is already in the ground and the user is documenting it after the fact)?
A: Yes, these will be automatically populated by the data set so it shouldn’t be additional effort for the user. Estimated seed required is optional and estimated yield is required.