Open gabroko opened 6 months ago
I like the idea of allowing for Other1
, Other2
etc. to give room for custom information, and allow to set custom boundary checks in the config
object.
I've tried one approach which turned out to be very tricky, but have a second idea. What we could do is the following:
Other1
, Other2
, ... up to Other20
(@gabroko or how many you think are realistically needed).$lower
, $upper
in the config
if, and only if, the variable name is Other*
.annex_validation
, no changes needed there and the boundaries are stored in the XLSX stats file, so one can check what the statistics are based on.We could do the same for $unit
(for Other*
variables only) and also write it into the stats XLSX file. What will not be possible is "automatic unit conversion" as this requires a specific set of rules (functions).
Have not thought that trough yet, but when we can carry along $unit
we can also carry along the additional information in the same way; that should work.
Would that work for you @gabroko ?
Yes, that sounds perfect! I would think max 10 Other are enough. But no rush on that...