Thanks @siljelb. Timley conversation.
Our problem comes exactly because we are forced to squeeze the scores and scales into Text and Ordinal data types. While it is possible to use either data type for most scores/scales, there are always outliers.
Ordinal is not truly intended to support scoring, but rather ordering.
So when we get scoring that is sequential or unique whole numbers it works fine. But if we get duplicates we had trouble, at least until recently. And if we have scores that have 2, 2.5 and 3 we have no possible solution except to try to represent the numerical scores associated with each value/selection.
Ultimately we need a technical datatype solution that separates out the score from the ordering, so that developers know when the score is applicable for the archetype - at the moment it can be derived from the hierarchy of a DV_ORDINAL or in the name or description of a CODED_TEXT.
There is no consistency because it is not possible to be consistent when we are often forced to adapt data types for purposes they are not intended for.
We need a data type that allows:
- data element names for all
- descriptions for some, but not all
- ordering for some, but not all and not always sequential or unique
- scores associated with some, but not all
It is not just about modelling patterns…
Advice from our @Specifications experts?