Open pmackay opened 10 years ago
Looks like the root of this is that I assumed CKAN would be consistent in using the same property for titles on different items. It doesn't appear this way though - they use 'title' for the dataset, and 'name' for the resource.
Thing is DKAN have made the same assumption - they use 'title' for both (which I think is where I got the idea from originally - it's quite hard to find people using the resource name on data.gov.uk).
I've opened an issue on DKAN which goes into more detail:
https://github.com/NuCivic/dkan/issues/195
I've put a workaround in the DU code but not posted it yet. I'd like to see what DKAN come back with.
But if we're just using CKAN for now, do we need an issue raised on that project?
It depends - maybe they know something that we don't, like maybe a resource can have a 'title' and 'name'. Pretty unlikely, but I can't see any documentation that specifies what the CKAN JSON results should contain.
(Partly raised the issue out of politeness too - help out another Open Source project!)
If I check http://lambeth.dataunityapp.com/api/beta/datatables/bdb1fc70-e1e6-4518-a693-a9a862c1c07a/sources-datasets which is info about http://5.101.100.119/dataset/met-police-crime-figures/resource/875faf46-d993-4f94-bfb2-92234b224827, the distribution.title JSON is "Met police crime figures" which is the title of the dataset. I would have thought it should be the title of the resource, e.g. "Met Police crime figures 2014-02" ?