Differentiate "Organic" and non-organic

It may make sense to create a new module for USDA Organic certification, which provides the necessary fields for recordkeeping, and ties into the core FarmOS log types.

Yea it might be necessary to have different add-on modules for different organic system requirements, with common stuff provided by farmOS itself. Areas and assets already have a Files field which can be used to attach specific documents, if necessary. There is also already a feature request for adding the concept of an "Asset Group" for grouping assets in various ways: #2469109: [META] Discussion: Asset Groups/Hierarchy

All farmOS repositories have been merged into the farmOS distribution (see #2876992: Merge farmOS repositories into drupal.org/project/farm). I'm going through and moving all open issues from the various project issue queues to the central queue now...

I'll be picking this one up again soon.

My current plan is to add an "Organic" checkbox to areas, assets, and logs, that let's you flag the entity as "organic" (or not). Additionally, a config form will be provided that allows a farm to set the default state of the checkbox globally. This will allow farms that are partially organic to differentiate records that are organic vs non-organic. Farms that are mostly organic can default the checkbox to checked, while farms that are mostly non-organic can default it to unchecked.

Ideally this will all be packaged into a new farm_organic module, which is optional.

The tricky part will be altering the checkbox (which I'm assuming will be a Field API field) into all the entities, and altering a new exposed filter into all relevant Views (because I'm expecting that will be really necessary in practice for finding records based on that flag.

It may also be worth considering just adding generalized flagging mechanism (like "Log Categories" that exist now), of which "Organic" (and maybe "Non-Organic") could be an available flag. In which case, the farm_organic module would just auto-enable that category. We already have similar functionality in the farm_log_category module - so maybe that can just be generalized to other entity types.

That's what I'll be working through...

@BruceDawson - I'm going to build the flagging system approach. It's the most flexible, and will allow for other cool things too.

I like the idea of tracking flag history too. Technically, once we have entity revision tracking, we'll get that for free, since the flags field will be revisioned with any entity it is attached to - so all the change history will be recorded. For now, I'm going to start by simply adding it as a field like the others - so it won't have tracking right now, but neither do a lot of other fields. Revisions will fix that.

This is done!

I added a new module to farmOS core called Farm Flags, which adds a general-purpose Flags field. The field is on areas, and all asset and log types. It provides a hook that allows other module to add flags.

Then, I created a new contrib module called Farm Organic, which you can download and install separately: https://github.com/farmOS/farm_organic

All this module does is provide two flags: "Organic" and "Not Organic".

The idea is that if you are a mostly-organic operation, you can just assume that everything is organic, and use the "Not Organic" flag occasionally to designate certain areas/assets/logs as not-organic. And vice versa if you are mostly not-organic.

This "Organic" module can also serve as the foundation for additional organic certification features moving forward.

@Permakai - I've already gone ahead and implemented the flags approach. But to your point regarding "the certification number/status of the input in question" there is a "Lot number" field on inputs. So maybe that would be useful to you. You could enter information about the input you applied, with the lot number, and add the "Not Organic" flag, so it's easy to find during certification review/inspection.