There are a lot of people out there who struggle to deal with JSON. We have quite a nice setup coming from the ODM project where some hierarchal data is 'flattened' on to a standard schema, whilst retaining the original metadata in an extra field. We might find more users for this data if we provide a download via CSV, tabular data package, Excel etc.
This is probably an issue for CKAN centrally. CKAN is very dataset focussed IMO and there isn't a lot of attention paid to metadata exchange. E.g. Datastore API is there for storing data for the datasets.
There are a lot of people out there who struggle to deal with JSON. We have quite a nice setup coming from the ODM project where some hierarchal data is 'flattened' on to a standard schema, whilst retaining the original metadata in an extra field. We might find more users for this data if we provide a download via CSV, tabular data package, Excel etc.
This is probably an issue for CKAN centrally. CKAN is very dataset focussed IMO and there isn't a lot of attention paid to metadata exchange. E.g. Datastore API is there for storing data for the datasets.
Relevant: https://github.com/okfn/data.okfn.org/issues/126