[ckan-dev] A couple of new extensions

[Steven De Costa]

Thanks Denis! I really appreciate this notification and outline of the
extensions. Both look very helpful.

Are you happy for this to be posted up on ckan.org?

Anyone else happy to write a short outline of extensions they would like to
share? This could even be on extensions you rely on but may not have
developed. I'm sure those contributing would love to see how their work is
adding value to people using CKAN.

Cheers,
Steven

On Friday, August 14, 2015, Denis Zgonjanin <deniszgonjanin at gmail.com>
wrote:

> A couple of CKAN extensions which I've been working on are good enough to
> share now, so I thought I'd let people know about them in case anybody
> finds them useful:
>
> 1. Webhooks: https://github.com/datacats/ckanext-webhooks
> A problem I've had personally is having my open data apps know when a
> dataset they've been using has been updated. You can of course poll CKAN
> periodically, but then you need cron jobs or a queue, and when you're using
> a cheap PaaS like heroku for your apps, integrating queues and cron is just
> an extra hassle.
>
> This extension lets people register a URL with CKAN, which CKAN will call
> when a certain event happens - for example, a dataset update. The extension
> uses the built-in CKAN celery queue, so as to be non-blocking.
>
> If you do end up using it, there are still a bunch of nice features to be
> built, including a simple web interface through which users can register
> webhooks (right now they can only be created through the action API)
>
> 2. Geopusher: https://github.com/datacats/ckanext-geopusher
> So you know how you have a lot of Shapefiles and KML files in your CKANs
> (because government), but your users prefer GeoJSON? This extension will
> automatically convert shapefiles and KML into GeoJSON, and create a new
> GeoJSON resource within that dataset. There are some cases where this won't
> work depending on complexity of SHP or KML file, but it works well in
> general.
>
> This extension also uses the built-in celery queue to do its work, so for
> both of these extensions you will need to start the celery daemon in order
> to use them:
>
> `paster --plugin=ckan celeryd -c development.ini`
>
> Thanks,
> - Denis
>
>
>

-- 
*STEVEN DE COSTA *|
*EXECUTIVE DIRECTOR*www.linkdigital.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150814/62508060/attachment-0003.html>