You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user was searching for 'biochemical trait' using the 'Trait descriptor list' field and got no results. Then they attempted to create it from scratch. When writing in the 'Trait' field to define the new trait descriptor, 'biochemical trait' appeared as already present in the database.
I can understand some technical reasons for this, but I think it's clear that it's counter-intuitive and it suggests some bad behaviour in the search field of the 'Trait descriptor list'.
Could search for existing traits in the database rather than in the dictionary solve this problem. In addition I suggest to minor GUI changes to avoid confusion
Change Trait to New Trait Name
Add text: "Please contact us if you propose new traits that are not present in the trait ontology"
The text was updated successfully, but these errors were encountered:
There is no "technical" reason behind it. It is actually the way we have (together with you and Annemarie) designed it. Trait is just a name of a trait, a dictionary field. While Trait Descriptor is the entire description of the way a trait is measured in a trial. The name might be misleading but we have it from the CropStore schema, so we've kept it.
In order to be able to submit a scoring, a Trait Descriptor has to be defined (there are certain fields we require from a user regarding how she measures it) - that's why we have this two-step creator.
I know, I wasn't suspecting any issue behind it, just marking that we need to perhaps add some clarification in the text below boxes and in the documentation pdf.
A user was searching for 'biochemical trait' using the 'Trait descriptor list' field and got no results. Then they attempted to create it from scratch. When writing in the 'Trait' field to define the new trait descriptor, 'biochemical trait' appeared as already present in the database.
I can understand some technical reasons for this, but I think it's clear that it's counter-intuitive and it suggests some bad behaviour in the search field of the 'Trait descriptor list'.
Could search for existing traits in the database rather than in the dictionary solve this problem. In addition I suggest to minor GUI changes to avoid confusion
The text was updated successfully, but these errors were encountered: