Udata-ckan

- DKAN support [129](https://github.com/opendatateam/udata-ckan/pull/129)

- Always fill extras.remote_url [103](https://github.com/opendatateam/udata-ckan/pull/103)

- Max out package_search rows limit [100](https://github.com/opendatateam/udata-ckan/pull/98)

- Fix filetype (always remote) [98](https://github.com/opendatateam/udata-ckan/pull/98)

- Support both inclusion and exclusion filters [42](https://github.com/opendatateam/udata-ckan/pull/42)
- Localization support [43](https://github.com/opendatateam/udata-ckan/pull/43)
- Test the minimum accepted CKAN dataset payload and make the `extras` property optional [57](https://github.com/opendatateam/udata-ckan/pull/57)
- Improved error handling (support details in JSON responses, also handle raw quoted strings and HTML) [56](https://github.com/opendatateam/udata-ckan/pull/56)

- Only store `url` field in `remote_url` extra if this is an URL otherwise store it in `ckan:source` [30](https://github.com/opendatateam/udata-ckan/pull/30)
- Properly handle geometry errors [31](https://github.com/opendatateam/udata-ckan/pull/31)
- Improve extras parsing [32](https://github.com/opendatateam/udata-ckan/pull/32):
- Skip empty extras
- Parse update frequencies as RDF URI or udata frequency identifier
- Parse `spatial-text` matching a known zone name or slug
- Store unknown `spatial-uri`, `spatial-text` and `frequency` as `ckan:spatial-uri`, `ckan:spatial-text` and `ckan:frequency`