Add ''other'' measurements

[celineaubert]

Maybe reused the form developed for RTB or add a ‘’my trait is missing’’ button

[celineaubert]

@omarbenites For the first release, we can develop something simple for us and the users.
When they click on ''create a new measurement'', a new line appears in the table with text boxes. It's easy for them to create the measurement they want.
Pro: No frustration on their side, easy and quick to develop
Cons: Less harmonization, no link with the ontology, no link with GitHub

Later, we can develop a way to add a GitHub issue for each '' new measurement'' created.

Edit: This solution needs to be adapted to be KDSmart compliant: TraitName, TraitDataType, TraitValiadation and are required

[celineaubert]

@omarbenites To be KDSmart compliant we could try to have the following info for a new measurement:

TraitValidation: -100.00 <= x <= 10000.00
TraitDataType: DECIMAL
TraitName: Crop_Parametermeasured(subgroup)_Measurement_unit
TraitAlias: Crop_measurement

[omarbenites]

Might we move this issue for the second release? Just in case we run out time...

[celineaubert]

Hi @omarbenites ,
below is an update for this issue, compatible with Angular.

• In Crop measurements drop down menu ''Other'' could be the first choice.

• Once users select ''Other'', the following line is added to the crop measurements list:
  

• Only the name of the measurement should be editable. The parameter measured and the unit will come from from Crop-measurement file, line 755 : https://docs.google.com/spreadsheets/d/1Hl3-u11cHkrVDM6pdADkUCMzuauz7fud7RH7PIWKSX8/edit#gid=1134960487

• To be compliant with KDSmart, a TraitName and a TraitAlias need to be created and be different for each ''other'' measurement.
  My suggestion would be to concatenate the following information:
  TraitName: Crop_Parametermeasured(subgroup)_Measurement_unit
  TraitAlias: Crop_measurement

Let me know if you have suggestions. A similar feature needs to be build for Phenology, Soil and Weather