Rothamsted-Ecoinformatics / farm_rothamsted

Custom farmOS features for Rothamsted Research.
GNU General Public License v2.0
5 stars 1 forks source link

Ontology Integration: Test new FarmOS Module #642

Open aislinnpearson opened 3 months ago

aislinnpearson commented 3 months ago

Hi @mstenta, @paul121

Once the Ontology module is ready to go, I was thinking it would be great to test it in our .dev account (so maybe an excuse to set that up as well - issue #611). Excited about showing it to Richard.

Our linked issue for the taxonomy is here: https://github.com/Rothamsted-Ecoinformatics/farm_rothamsted/issues/157

mstenta commented 3 months ago

@aislinnpearson Actually it will be part of core farmOS! Not a separate module. So assuming we settle on the details in the pull request and merge it before farmOS v3.2.0 is released, you'll get it on all your instances at the same time when we deploy that update. :-)

mstenta commented 3 months ago

(Oh but worth noting, the "Convention" module is a separate module, if you were interested in that too: https://github.com/mstenta/farm_convention)

aislinnpearson commented 1 month ago

@mstenta I've done all the testing for this and I love it. If I had one more request it would be to give names to links or to be able to tag them somehow. For example we may want to link them to Hestia as well as the pesticides database and an ontology term, in which case it would be nice to tag a link with that specific 'schema' (to use the word very loosely).

E.g. Triple superphosphate:

"Hestia": https://www.hestia.earth/term/tripleSuperPhosphateKgP2O5 "Agronomy ontology": http://purl.obolibrary.org/obo/AGRO_00002065

mstenta commented 1 month ago

@aislinnpearson This came up during the core discussions when we were adding this field. It makes sense! Now that the field was added to core, however, we are a bit constrained in making changes to it, because we have to assume that it is being used in the wild now, and we can't make "breaking changes" per our semantic versioning policy. So unfortunately we wouldn't be able to consider changing the field's data structure again until farmOS 4.x. :-/

I will add this to the "4.x wishlist" though! In the meantime, we could also consider adding additional Rothamsted-specific fields which have a more explicit meaning. But if it's not a high priority then maybe we can start planning the specifics for farmOS 4.x to be sure that it happens.