mrbotcr / py3ClimMob

ClimMob is software for agricultural citizen science
https://climmob.net/
GNU Affero General Public License v3.0
5 stars 2 forks source link

Curation of technologies/varieties/accessions #269

Open qlands opened 4 months ago

qlands commented 4 months ago

Related to #141.

Starting with crops. Then the typology can add attributes for each option.

qlands commented 4 months ago

Genotypes Forage mixtures Crop management regimes Product concepts Others

qlands commented 4 months ago

OK. I started a user story around this issue: https://docs.google.com/document/d/1_ooQfodxDY4gj8NsKExfh0nX1Z5Dzwzy8WFZ1guygY4/edit?usp=sharing

@jacobvanetten and @kauedesousa please work on the user story. Please describe it and work on how you see this working. Use screenshots to describe how you see it working.

Based on that description I will check what is needed to change or add in terms of architecture and coordinate with Brandon its implementation.

kauedesousa commented 4 months ago

I also add @marieALaporte to follow this issue

marieALaporte commented 4 months ago

I think that's a great idea to have these typologies, as a first step to allow the standardization of the metadata. I added a comment in the document regarding the genotypes metadata

MarManrow commented 1 month ago

@marieALaporte

Curated list of technologies/accessions/varieties linked to a unique taxonomy and metadata.

Open question: what “source of truth” to use? How to store the curated information (curated variety name, synonyms, date of release, cross reference to external IDs, ….)? Tasks:

Assign a crop taxonomy Identify mandatory metadata for technologies by types Identify mandatory metadata for the varieties/accessions. Implement the metadata fields on the interface (UI) Have an interface for enriching missing information on technologies Curate the variety names for Cassava (1000FARMS) using CassavaBase Curate the variety names for Amaranth (BOLDER) using Genesys

Related issues : https://github.com/mrbotcr/py3ClimMob/issues/141 https://github.com/mrbotcr/py3ClimMob/issues/117 https://github.com/mrbotcr/py3ClimMob/issues/243 https://github.com/mrbotcr/py3ClimMob/issues/264 https://github.com/mrbotcr/py3ClimMob/issues/269 https://github.com/mrbotcr/py3ClimMob/issues/271

MarManrow commented 1 month ago

@BrandonMrBot

Assign a crop taxonomy

At this moment, having identified the crop taxonomy to which the technologies created by users belong is the starting point that will allow us to have a clear overview at the reporting level.

This function has been developed so that users must complete it as a priority, meaning they cannot perform any other action until they meet this requirement, which is assigning the correct crop taxonomy to each of their technologies.

The functionality is very simple: each technology created by the user has a drop-down menu where the user will search for the corresponding crop taxonomy. Once they have selected all of them, they will click the save button and can continue with the normal use of ClimMob.

At this point, we only need to write help texts and explanations about why this is necessary by the ClimMob team.

Image

marieALaporte commented 1 month ago

quick comment: for technologies that are not crop, we also need to come up with some taxonomies