Make requests schema agnostic

[amercader]

As you very well state on the README the results returned by different instances will depend on their own custom schemas.

I'm not sure what API calls you use internally but you can force calls to package_show to always return the default internal CKAN schema passing the use_default_schema=True parameter.

So instead of this:

http://ckan.data.ktn.gv.at/api/3/action/package_show?id=abflusswerte-karnten

you get this:

http://ckan.data.ktn.gv.at/api/3/action/package_show?id=abflusswerte-karnten&use_default_schema=True

Note that custom fields like lineage or update_frequency are now located in extras which is the way CKAN stores them internally. You will get the same behaviour across all CKAN sites and versions (starting from CKAN 2.2, which is when support for this parameter was introduced)

The same behaviour should be available to package_search, but sadly there's a bug that raises an exception when passing the use_default_schema parameter. I've submitted a patch for it that will be backported to older versions: ckan/ckan#2848

Hope this helps

[wilhelmberg]

you can force calls to package_show to always return the default internal CKAN schema passing the use_default_schema=True parameter.

Nice! Good to know.
Must have missed this in the API docs.