Different terms for resource title in API compared to CKAN

[dataunity]

Hi,

It looks like CKAN use the term 'name' for a resource's title in the API. However DKAN users the term 'title' instead.

As an example, here's a DKAN dataset. The resource title is:

...
   "resources": [
      {
        "title": "Recycling banks"
...

http://dev-lambethdata.gotpantheon.com/api/3/action/package_show?id=f9b7f363-6a2b-426e-8306-60332aa095cd

Here's an example from a CKAN instance:

...
   "resources": [
      {
        "name": "Met Police crime figures Jan 2014"
...

http://5.101.100.119//api/3/action/package_show?id=met-police-crime-figures

I may have got things wrong and both 'title' and 'name' are acceptable properties for a resource, but I can't see the API JSON documented anywhere in CKAN to confirm.

[acouch]

Thanks. Will update this soon.

[teosibileau]

we still have some work to do to integrate Nucivic/open_data_schema_map_dkan into dkan but it'll eventually get in when we replace the dkan_dataset_api module

[acouch]

This is now configurable on a per instance basis with the Open Data Schema Map module which is included in DKAN. See https://github.com/NuCivic/open_data_schema_map#multi-value-fields for details.