Currently there is no documentation of how to store for example the standard deviation.
It’s always better having the raw data, but it’s not always available and sometimes the data provider wants to store such calculations.
I propose adding three terms instead of having SD terms:
measurementStatisticalQualifierValue, measurementStatisticalQualifier, measurementStatisticalQualifierID.
User would be able to use any of the (currently) 43 S07 (BODC parameter semantic model parameter statistic) terms, and not only SD, e.g.
Replicates values can be reported in multiple lines using measurementValue. Each set relates to the same eventId.
Eventually we should see what GBIF thinks about it, and if IPT could be changed: Instead of having measurementValue not null, the requirement would be that one should fill either measurementValue or measurementStatisticalQualifierValue. Otherwise, we can tell user to put the same value both in measurementStatisticalQualifierValue and measurementValue.
Currently there is no documentation of how to store for example the standard deviation. It’s always better having the raw data, but it’s not always available and sometimes the data provider wants to store such calculations.
I propose adding three terms instead of having SD terms: measurementStatisticalQualifierValue, measurementStatisticalQualifier, measurementStatisticalQualifierID. User would be able to use any of the (currently) 43 S07 (BODC parameter semantic model parameter statistic) terms, and not only SD, e.g.
measurementStatisticalQualifierValue | measurementStatisticalQualifier | measurementStatisticalQualifierID
5 | mean | http://vocab.nerc.ac.uk/collection/S07/current/S0700003/ 1.1 | standard deviation | http://vocab.nerc.ac.uk/collection/S07/current/S0700007/ 3 | minimum | http://vocab.nerc.ac.uk/collection/S07/current/S0700005/ 7 | maximum | http://vocab.nerc.ac.uk/collection/S07/current/S0700002/
Replicates values can be reported in multiple lines using measurementValue. Each set relates to the same eventId. Eventually we should see what GBIF thinks about it, and if IPT could be changed: Instead of having measurementValue not null, the requirement would be that one should fill either measurementValue or measurementStatisticalQualifierValue. Otherwise, we can tell user to put the same value both in measurementStatisticalQualifierValue and measurementValue.
Thank you, Menashè