dr-leo

This behavior is correct. If you want to see the full data structure definition, request a specific data flow or the data flow definition directly. This is described in the...

Thanks. This explanation is helpful, even if I have read through the intake docs quite a few times. So I realize that ideally each catalog entry is populated at instantiation...

While your above comment has given me a lot of food for thought, I would like to come back to your original proposal for a one-to-one meeting as being the...

I've implemented much of what we've discussed: * use a lazy dict for the dataflows catalog * populate UserParam instances with allowed codes for each dimension * instantiate a Source...

OK. The above issues seem to be solved, i.e. multiple selection of codes (eg. 'DE+FR+UK', this is properly validated; I've subclassed UserParameter. And code descriptions are stored in the UserParameter...

Wonder if you are notified of my thubs-up reaction. So here's the nudge...

Repo: https://github.com/dr-leo/intake_sdmx See the only module at top level. Tests are outdated. The following snippet should be relevant: ```python # ... list of user-params. loop not included params.append(p) return LocalCatalogEntry(name=flow_id,...

What follows is a subjective, high-level summary of the status of intake_sdmx and TODO's for intake and intake_sdmx: =intake_sdmx: working features= * catalog of data sources / SDMX services *...

In v6.4, the mlist type for UserParameter seems to be broken as a list-typed default value is silently converted to str. As a consequence, coercion fails as it expects a...

Alas, I cannot reproduce your error. Interestingly, on your side, intake_sdmx seems to request the EXR dataflow from the ECB, whereas on my side, the type error occurs when instantiating...