Use of TimeRange for Time dimensions.

[lmorandini]

Some of the cubes in the new ABS ReST 2.1 endpoints have the dimension TIME_PERIOD with no codes, but an XML TImeRange element instead.

@amattioc : any idea on how to tackle this?

[amattioc]

Hi Luca, does the use of Time Range create problems to the connectors? It seems to work fine for me:

[lmorandini]

Could you please point me to a Java code fragment that retrieves the time period (as separate values, such as a list of years) of a cube?

[amattioc]

This is the section of the structure parser that handles the TimeDimension.

The codelists are processed in this section but, since the time dimension is not coded, there is not match for it.

The dsd parsing is successful for the new ABS endpoint, but maybe you are referring to the constraints section?

[amattioc]

Hi @lmorandini, any news on this? I was looking at the dataflow message of the new ABS provider and I think that you were probably referring to the constraints section that it contains. Though not specifically needed for the connectors as they are today, thse information could be useful to improve the user experience in building valid queries with the sdmx helper. Unfortunately not many providers send these information yet...

[lmorandini]

My issue is more mundane: how to extract the allowed time periods from the GenericSDMXClient/Dataflow/DataFlowStructure classes? I can easily get the code list with getCodeList from DataFlowStructure, but not the time periods: any ideas?

[amattioc]

Currently you can not get the time period constraint because it is in a section of the dataflow message that we don't process (because dataflow constraints are not tipically filled by the providers). Nevertheless I think it could be useful to start processing it, when present, for the reason that I explained. I'll keep this issue open, tagging it as an enhancement, and I'll notify you when it is fixed...