[ckan-dev] ckanext-dgu loaders depend on ckan

Rufus Pollock rufus.pollock at okfn.org
Mon Mar 7 15:22:07 UTC 2011


On 7 March 2011 12:25, Stefano Costa <stefano.costa at okfn.org> wrote:
> Hi all,
> I'm trying to build a loader script for a few Italian datasets. Start at
> http://packages.python.org/ckan/loader_scripts.html
>
> I cloned ckanext-dgu, installed the pip-requirements just to find out
> that I need to do a full install of ckan.

You really *don't* want to do that :) (i.e. use ckanext-dgu).

As David Read says, the much better place to start is the loaders
based on ckanclient which can be found here:

<https://bitbucket.org/okfn/ckanext/src/e7411da05865/bin/>

E.g. here's the loader I wrote last summer for it.ckan.net stuff (not
sure if it is up to date so YMMV!):

<https://bitbucket.org/okfn/ckanext/src/e7411da05865/bin/ckanload-italy-nexa>

[...]

> I think a simpler setup for loaders would help a lot in getting more
> people involved in the creation of new package. I'm wondering if it

Big +1. We should definitely document the results of this discussion
on http://wiki.ckan.net -- perhaps on
http://wiki.ckan.net/Using_the_API or a dedicated page.

> wouldn't be easier to automate around datapkg for the simple case of
> creating new packages?

I'd recommend using ckanclient (you could hook directly into datapkg
but it is just wrapping ckanclient in this regard).

Rufus




More information about the ckan-dev mailing list