Crops Tab Functionality

[dallascrichmond]

As a farmer I want to add my crops to individual fields So That I can see the different nutrients needed

Additional Context

• Part of Fields and Soil Section
• Using Temp Data for now
• Final Styling and Validation will be in a separate ticket

Acceptance Criteria

• Crops tab appears when next is pressed on Farm Information page
• Add Crops, Prev Button, Next Button, and a list of added fields are present
• Add Crops Button brings up Modal with varying fields to fill in depending on which crop type is chosen (Refer to old NMP for Fields)
• Calculate Button calculates the Crop Requirement and Nutrient removal
• Save Button saves all form data to local storage and displays crop info next to associated field
• Prev Button Takes the user back to Farm Information Page
• Next Button changes section to Manure and Compost section (Empty)

[raarielgrace]

So... we've run into issues again. None of the database tables have a proper primary key (a column that is non-null and unique). Because the database tables store every version of the table together, only the combination of the id and version_id are unique. In SQL speak, this would be a composite primary key. The Django admin portal requires the presence of a primary key. The newest alpha of Django includes support for composite primary keys, but they still aren't supported in the admin portal. These are the options:

1. Add another column to each table that contains a unique id. We'll then have 3 different id columns.
2. Trim down each table to its most recent version, version 14. Track the previous versions and changes in a different manner. This will make the id column a proper primary key. It might, however, make previous versions inaccessible or more complex to access for the SO.
3. Keep using Django, but build our own admin portal instead of using Django's admin portal.
4. Move away from Django entirely, trying to find something else that will generate an admin view for us without requiring primary keys.

[jakemorr]

@raarielgrace I'm in favor of either option 1 or 2, so long as we keep that information available to the service owner in some way i think option 2 makes the most sense.

[dallascrichmond]

Move to blocked for now. Most of the functionality if there and in a PR ready to be reviewed. I just would like to sync up with Josh to figure out the calculation side of things

[Keegnan]

We are still waiting on the calculations from SO.

[Keegnan]

Waiting on 2 more calculations from SO