Curation of technologies/varieties/accessions

[MarManrow]

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 of BioversityCostaRica repository:

• https://github.com/BioversityCostaRica/py3ClimMob/issues/141
• https://github.com/BioversityCostaRica/py3ClimMob/issues/117
• https://github.com/BioversityCostaRica/py3ClimMob/issues/243
• https://github.com/BioversityCostaRica/py3ClimMob/issues/264
• https://github.com/BioversityCostaRica/py3ClimMob/issues/269
• https://github.com/BioversityCostaRica/py3ClimMob/issues/271

[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.