-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ckanapi dump datasets --all doesn't work for catalog.data.gov #98
Comments
It's possible (and more efficient) to dump all datasets with package_search, but you have to be careful about duplicate or missing records that may appear in the results if datasets are being modified while you're dumping them. Are you interested in helping to implement this? It shouldn't be too difficult. |
I looked at the code in dump.py. It seems that it doesn't support making multiple paginated requests.
Does the current code support paginated requests somewhere? |
No, using package_search is very different than the *_list, *_show that dump.py uses, so it won't be much help. getting dataset results from package_search should be very fast though, so you don't need dump.py's multiple-worker support. How about just writing it as a separate sub-command? Also note that older versions of CKAN don't return the same data from package_search that they do from package_show, so it's useful to keep the current dump datasets implementation around for a little while. |
Okay. Since it's convenient I will ask another question here. How do I know which version of the API am I calling. Is this
the newest API or do I have to explicitly add
Using |
in ckanapi so far I've omitted the api version when calling ckan because I've always wanted the latest version of the API. |
note that we now have |
I am trying to download all metadata from catalog.data.gov. The following command returns an API error.
The error:
It looks like the
catalog.data.gov
have redirected thepackage_list
topackage_search
. Is there a way to handle this? Am I missing something?The text was updated successfully, but these errors were encountered: