...
Maintain or expand the ability to document a crop sale
Several common categories of incomes / revenuesCrop salesEvent hostingTourismConsultationsCrafts
A standard flow for adding a new instance of revenue that covers at least the following attributes:
Description Customer (optionalRequired)
Date of income (required) [default to day of creation and shown]
Category Type (required) [selected via tile on previous screen and not shown on creation]
“Is the revenue associated with agriculture
“Was this revenue generated on the farm?” (required)“Yes” (default), “No”
“Associated with crop(s)“Would you like to associate this revenue with any crops?” (optional) [dependent on “Is the revenue associated with agriculture?” being “Yes”multi-select]
User should be able to select any number of active of crop plans
Notes (optional)
Ability to easily add several revenues back to back (but not within the same flow)
Saved revenues must correctly attribute revenue categories and crop types
...
Ability to add several revenues in the same flow
Ability to mark a revenue as repeating
Filters to be able to view ag related and non related revenues (Nice to have)
Filters to be able to view crop and non crop related revenues (Nice to have)
Non-functional Requirements:
...
Question | Answer | Date Answered |
---|---|---|
Should we call money coming into the farm “Revenues” or “Income”? | Revenues |
|
Are there other revenue types we’re not tackling now? Why? | Yes! Per user meeting on . Then there were several that they mentioned, but I think we'll handle them once we add the relevant functionality:
Processed goods: As discussed in the past, we might want to wait on this as there is additional complexity to this. Probably need to add a "processing" task |
|
Should the attributes of revenues be defined at the “template” level or the “instance” level? If defined at the “template”, can users overwrite at the instance? Are there some of each? Current expected implementation is at the template level we ask if the revenue should be associated with crops or not. If the answer was yes then at the instance level we ask, “which crops?” | Kevin’s proposal (to be debated) Defined by revenue type:
* Custom revenue types are uneditable once created. Defined at creation of instance:
Refactors to be undertaken:
|
|
What attributes should be shown for each revenue type? (e.g. Event hosting, Tourism, Consultations, Crafts) | None! We decided to:
|
|
Should we guide users not to create livestock related revenue types? | No! We should review what types users create after 3 months and use this to guy the types we create for livestock. |
|
Out of scope
Documenting “CSA boxes” as a revenue source; reasoning is the complexity of documenting new CSA boxes each period. Should likely be implemented as a “template”.
...