Inputs

 

What’s an input?

An input is something that is brought onto the farm and consumed in order to produce crops. Some examples include seeds, fertilizers, and pesticides.

 

Why are inputs important?

Many types of certifications, including Organic require farmers to use certain types of inputs and to document all uses and sources of inputs on their farm (see Certifications, certifiers, and LiteFarm for more information). Indeed, calling something an “organic fertilizer” is shorthand for saying “a fertilizer that can be used as an input in organic production”.

For the purposes of the Q3 2021 release, the following type of tasks may or must have an input associated with them:

  • Soil amendment (must) [includes the idea of fertilizers]

  • Cleaning (may)

  • Pest control (may)

When a user creates a task that can reference an input the most important question is whether that farm is seeking a type of certification that requires the documentation of inputs. If they are, additional fields become required.

 

Input attributes

Attribute

Data type

Required

Notes

Attribute

Data type

Required

Notes

Type of input

Enum: {“Soil amendment”, “Pest control”, “Cleaner”}

Yes; assumed from context

Will be assigned based on where the user creates the input. For example, if created while creating a soil amendment task, the type becomes “Soil amendment”.

Product name

Text

Yes

 

Supplier

Text

Organic

Required if the user is seeking an organic or PGS certification

On permitted substances list?

Enum: {“Yes”, “No”, “Not sure”}

Organic & Canada-based farm

This is only relevant to Canadian farmers seeking Organic certification. Other attributes along similar lines will likely be added in future releases.

https://www.cog.ca/wp-content/uploads/2020/12/M-Preparation-PSL-6_R55.pdf

Farm_id

Ref

No

Will be null if available to all farms. Otherwise, populated with the farm_id where it was created (and only available for use at that farm).