Crop Cycle Doctype

[codingCoffee]

• ISO-8061 week standard (could be a choice)
• start date
• end date
• Type of cycle
  • weekly
  • monthly
  • trimester
  • semi-annually
  • annually
• Expected Yield
• Link to BOM

Agri Tasks

• Production cut
• Final cut
• Irrigation
• Fertiliser Application
• Cleaning
• Fungicide Application
• Pesticide Application

And each agri task should have the following

• start date
• end date
• yield
• expense incurred

[agritheory]

ISO-8061 week standard is common in the greenhouse and market-vegetable industries but not used in others. I recommend a choice.

[agritheory]

Type of cycle - choose matching periodicity. I recommend days or weeks. The others will not be used

[agritheory]

Format Verb tense to Frappe standard (current tense)
Tasks

Production cut
Final cut
Irrigation
Fertiliser Application
Cleaning
Harvest - how is this intended to be different from Production cut or Final cut?
Fungicide Application
Pesticide Application

[agritheory]

Expected Yeild

Yield is consistently spelled incorrectly in your issues, that could be a nasty bug to chase if it makes it into code

[agritheory]

Inputs (crops, seeds, fuel, etc.. )

What is the proposed structure for this? I would link a Cost Center instead and/or a BOM instead and leverage existing code.

[codingCoffee]

@agritheory
Having a choice is a good idea for the dates
Bananas have a crop cycle of 9-12 months, so I guess it's good to have those options

• Verb tense formatted to Frappe standard. Harvest was not required, my bad!
• 'Yield' has be fixed, thanks for mentioning!

Inputs changed to link to BOM

[vishalseshagiri]

Assign please

[codingCoffee]

• Scrap the Agriculture Task Doctype and create a Agriculture BOM Doctype which includes fields from both BOM and Tasks
• Integrate with Calendar to have an overview of all the tasks to be carried out

[Tropicalrambler]

A Crop Cycle should have a Yearly or Less than a year option.
Crops such as carrots, lettuce, etc. have discrete crop cycles lasting less than a year.
Crops such as Mango, Oranges, etc. have lengthy crop cycles of 20 years or more (some cases have been reported of 75+ year old trees still in commercial production). For these crops, user can select the Yearly crop Cycle option, at which point ERPNext can tally when the crop cycle opens and when it ends in a yearly period. This helps in proper accounting, and coincides with the accounting cycle.

[Tropicalrambler]

Add intercropping functionality, grouping crop cycles in tree fashion. (To be discussed on October 31 meeting.)