-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Curation of technologies/varieties/accessions #269
Comments
Genotypes |
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. |
I also add @marieALaporte to follow this issue |
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 |
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, ….)? Assign a crop taxonomy |
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. |
quick comment: for technologies that are not crop, we also need to come up with some taxonomies |
Related to #141.
Starting with crops. Then the typology can add attributes for each option.
The text was updated successfully, but these errors were encountered: