Ensure dimensions values in series codes match dimensions_codes_order
This only makes sense when dataset use dotted notation for series codes (ex: "M.MIO_M3.AL.4100.AT"). Either:
- a field in
dataset.json
files could also been added to indicate datasets that doesn't follow this naming rule - an option to validation script could be added to deactivate this check (for providers that we know that doesn't use this naming)
Details
A validation should be added to validation script: dimensions in series codes match defined dimensions_codes_order.
Example
Considering this code order given in dataset.json:
"dimensions_codes_order": [
"unit",
"FREQ",
],
"dimensions_values_labels": {
"FREQ": {
"M": "Monthly"
"unit": {
"MIO_M3": "Million cubic metres",
"TJ_GCV": "Terajoules (gross calorific value = GCV)"
},
]
- the series
MIO_M3.M
is valid (the dimensions order is unit, then freq) - the series
M.MIO_M3
is not valid
For now the validation script doesn't alert about this problem
Edited by Christophe Benz