-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Harvest Doctype #3
Comments
More details on the Harvest doctype can be found here. |
|
I agree Tyler, your clear thinking should prevail in this matter. Keep it simple first, then we can always complicate it later if enough people ask for it |
Convo with @Tropicalrambler |
Also discussed a Life Cycle or Life Plan document for livestock that mirrors Crop/ Crop Plan. |
I propose this structure for the Child Table:
For Livestock:
|
As I was working on the Fertilizer Application or Pesticide Application, it dawned on me that we can simplify greatly by having a SINGLE DocType which handles all the functionality for these types of work:
Work DoneEach of the above should belong to a Work Done DocType, and upon opening, the farmer selects: The selections made in these four fields, enable or disable those child tables relevant to the type of work being done. A harvest does not involve the application of pesticides. |
Problem statement
Basically this is a document bridging the quantities harvested, datetime stamp, explicit UOM conversions, and item mapping (to cover primary crops and by products)
A persistent/ stateful harvest record should exist for each harvest, so that 1) data points can be created for management over time and 2) trace-ability to crop cycle can be enforced with a submit-able doctype
Challenges
Harvest never matches expected harvest, both larger and smaller, byproducts and primary crops
Possible solution to Problem
Make a harvest doctype
Create a harvest from Crop Cycle and from the harvest task inside crop cycle
Reference screenshots / mockups (if any)
Mockup:
agritheory/erpnext@3c757e5
Checklist :
The text was updated successfully, but these errors were encountered: