A feature request for the crop cycle section of the agriculture domain to include weekly, recurring cycles for crops.
We are a horticultural business growing microgreens and mushrooms in poly tunnels and indoor grow rooms. We have weekly, recurring, planting schedules for our microgreen varieties (currently managed with https://kanboard.org/ project management software) with a fixed Wednesday day of harvest and packing every week of the year. Start dates of planting change over the season in line with the changes in temperature and humidity and are manually changed using a gantt chart. Some crops have a Date To Maturity (DTM) of 5 days in summer which then lengthens to 10 days in winter.
It would be great to be able to able to only enter one crop cycle per variety of greens (mustard, sunflower, radish etc etc) per year and have it re generate the next cycle with the same fixed harvest date but have me able to enter the start date manually. This is a common need of market gardeners who need to change their start dates of planting during the year but keep their harvest dates the same to accommodate their markets. A simple task list for the week would then indicate the crops (including amounts, number of seedling trays etc etc) to plant on which day.
Currently I can only create one crop cycle with a given name (eg. Red Radish_001) because I can't have multiple projects with the same name. I could rename every consecutive crop cycle for Red Radish with a _002, _003 etc suffix which would then create 52 projects numbering Red Radish_001--> Red Radish_0052. This would then duplicate all the tasks for Red Radish_001 into all the subsequent projects. I would then have to manually set all the end dates to every Wednesday of the year......... and so it goes on for every variety....... So, maybe this functionality would be better implemented in the Projects domain instead, as a crop cycle seems to be just a project anyway? Recurring tasks in projects a la kanboard.org.
I know this may be low on the priority list, if on the radar at all and I appreciate the hard work you guys have done and are doing! Cheers.
A feature request for the crop cycle section of the agriculture domain to include weekly, recurring cycles for crops.
We are a horticultural business growing microgreens and mushrooms in poly tunnels and indoor grow rooms. We have weekly, recurring, planting schedules for our microgreen varieties (currently managed with https://kanboard.org/ project management software) with a fixed Wednesday day of harvest and packing every week of the year. Start dates of planting change over the season in line with the changes in temperature and humidity and are manually changed using a gantt chart. Some crops have a Date To Maturity (DTM) of 5 days in summer which then lengthens to 10 days in winter.
It would be great to be able to able to only enter one crop cycle per variety of greens (mustard, sunflower, radish etc etc) per year and have it re generate the next cycle with the same fixed harvest date but have me able to enter the start date manually. This is a common need of market gardeners who need to change their start dates of planting during the year but keep their harvest dates the same to accommodate their markets. A simple task list for the week would then indicate the crops (including amounts, number of seedling trays etc etc) to plant on which day.
Currently I can only create one crop cycle with a given name (eg. Red Radish_001) because I can't have multiple projects with the same name. I could rename every consecutive crop cycle for Red Radish with a _002, _003 etc suffix which would then create 52 projects numbering Red Radish_001--> Red Radish_0052. This would then duplicate all the tasks for Red Radish_001 into all the subsequent projects. I would then have to manually set all the end dates to every Wednesday of the year......... and so it goes on for every variety....... So, maybe this functionality would be better implemented in the Projects domain instead, as a crop cycle seems to be just a project anyway? Recurring tasks in projects a la kanboard.org.
I know this may be low on the priority list, if on the radar at all and I appreciate the hard work you guys have done and are doing! Cheers.