Ian Ward

`package_id asc` would be nice, then we can easily compare the output from `dump datasets`

yes, sorry I've been slow in merging this. I like @davidread 's command-name suggestion. dump_datasets2 is better. We should document *why* you might want to use this command too (accessing...

Or even better: let's call this command `search datasets` and allow the parameters that are allowed to the package_search call to be provided (like you can with `ckanapi action package_search...

@ekzhu no worries, I'll finish this off if you're not interested in making my suggested change.

@amercader we discussed this at a dev meeting last week. I now think it's impossible to reliably get all the datasets from package_search with the default sort="metadata_modified desc". Any datasets...

ckanapi only uses the action api and so far there has been no update to the action api version. It's not a bad idea to add a parameter to allow...

@kalxas I'd love to talk about how you're extending the dataset metadata. Dev meeting might be good. IIUC your plugin supports arbitrary nested data as well as a flat version...

@kalxas @drmalex07 yes, I'll be there.

@kalxas @tomkralidis for multilingual metadata and labels I strongly suggest an approach like https://github.com/open-data/ckanext-fluent data fields or https://github.com/open-data/ckanext-scheming/#label where you accept and produce dicts of BCP-47 language keys with string...

This would have to be configurable in the schema. Existing users of scheming won't want these fields to reappear suddenly (and users have to be careful about not using conflicting...