feature request #4499: Implement fields for typical StatisticalMeasurementValues - EDIT - EDIT Project Management

Custom queries

5.33
cdm-dataportal (open)
last 7 days tickets
mine in current release
phycobank
phycobank-index-closed
phycobank-registration-closed
potentially missed issues
recently updated
Release3.7
Release3.8
Release4.0
Release4.1
Release4.10
Release4.11
Release4.12
Release4.13
Release4.14
Release4.16
Release4.2
Release4.3
Release4.4
Release4.5
Release4.6
Release4.7
Release4.8
Release4.9
Release4.9
Release5.0
Release5.1
Release5.10
Release5.11
Release5.12
Release5.13
Release5.14
Release5.15
Release5.16
Release5.17
Release5.18
Release5.19
Release5.2
Release5.20
Release5.21
Release5.22
Release5.23
Release5.24
Release5.25
Release5.26
Release5.27
Release5.28
Release5.29
Release5.3
Release5.30
Release5.31
Release5.32
Release5.33
Release5.34
Release5.35
Release5.36
Release5.37
Release5.38
Release5.39
Release5.4
Release5.40
Release5.41
Release5.5
Release5.6
Release5.7
Release5.8
Release5.9
Remoting-Versions
Taxeditor-UX (Platform Etablierung)

Actions

Copy link

feature request #4499

open

Implement fields for typical StatisticalMeasurementValues

Added by Andreas Müller over 9 years ago. Updated almost 4 years ago.

Status:

New

Priority:

Priority12

Assignee:

Andreas Müller

Category:

cdm

Target version:

CDM UML 5.43

Start date:

Due date:

% Done:

Estimated time:

Severity:

normal

Tags:

additivity

Description

To simplify the handling of quantitative data we may want to add concrete fields for min, max, average, sampleSize, typicalLowerBoundary, typicalUpperBoundary, variance, standardDeviation.

Maybe we also want singleValue (instead of average and sampleSize = 1

Only modifiers will not be available anymore. Are they needed? If yes, do we need them for each field or for

Updated by Andreas Müller over 9 years ago

One problem that arises is the correct use of numbers in Java, Hibernate + DB. For correct rounding etc. we should better use BigDecimal rather than Double.

However, BigDecimal is stored as Numeric(PRECISION,SCALE) with a fixed SCALE value. To allow different Scaling per record we may want to implement a BigDecimalUserType. This can be found at https://bitbucket.org/ratkins/bigdecimalusertype/.

http://stackoverflow.com/questions/6544232/how-do-i-map-a-bigdecimal-in-hibernate-so-i-get-back-the-same-scale-i-put-in

Alternatively we may use UserType with String representation !! But this may not allow Database computations on values.

https://docs.oracle.com/javase/7/docs/api/java/math/BigDecimal.html

Actions

Copy link