Work in progress

Why is copying crop plans important?

...

• Filter according to the following characteristics:

  • Date range

  • Statuses (multi-select, including ‘select all’)

  • Locations (multi-select, including ‘select all’)

  • Varietals / cultivars (multi-select, including ‘select all’)

  • Rating (X stars and up)

• Indicate that a plan should be copied or not

• Set an offset or select a date for the crop plan to start

• Modify the location for copied plan

  • (Nice to have) select multiple locations for the plan

• (Nice to have) Expand the plan to view individual tasks that are part of the plan

  • (Nice to have) Select / unselect whether particular tasks should be included in copy

  • (Nice to have) Modify offset / dates for individual tasks

• (Nice to have) copy the plan more than once

  • For example: copy this lettuce plan ever 15 days for 5 iterations

Open questions

1. Should we focus on a bulk copy instead (or in addition to) to allow the modification of many existing plans at once? For example, if there’s a last minute cold spell - all plans may be pushed back by a week.

2. How should we be supporting crop rotations?

3. For crops that are transplanted, how do we support changing locations?

Kevin’s gut: The starting location isn’t as likely to change since it’ll likely be a greenhouse. However, the final destination will be more more likely to change (e.g. Field 2 instead of Field 1).m