[okfn-br] Merging {br, cz, ie, it, no}.ckan.net into datahub.io and shutting them down

Quinta Novembro 13 20:49:29 UTC 2014

Hi,

migration of br.ckan.net to datahub.io is almost done.

br.ckan.net has 44 datasets visible through the API, 29 of which are
visible on the UI [1], and the rest is hidden - not deleted (why? is it
just a matter of missing reindex on solr?),

After filtering out 8 empty visible datasets, we're left with 20 on the OK
Brasil organization [2]. You may notice 29-8=21 so one is missing, which is
'cambio' [3]. I don't know why but dataset creation fails for this dataset
using the CKAN API. It has value so I might end up doing it manually. Any
ideas on how I could make it work via API?

If anyone's interested, I've been doing this using this high-level CKAN
client library [4], as I thought it would be easier to let it handle for me
the differences in metadata schema and API versions. However, it's in early
development and still have some quirks. Despite this, it's still easy to
use and do lots of things with just a few lines of code (so few I didn't
even bother commiting it to a code repository). I might write a blog post
describing the experience, if you think it would be useful.

[1] http://br.ckan.net/dataset
[2] http://datahub.io/organization/open-knowledge-brasil
[3] http://br.ckan.net/dataset/cambio
[4] https://pypi.python.org/pypi/ckan-api-client/0.1-beta5

PS: Copio a lista okfn-br pois se alguém estiver disposto a ajudar, será
bem vindo.

Best regards,
Augusto Herrmann

On Fri, Oct 3, 2014 at 4:49 PM, Augusto Herrmann <augusto em okfn.org.br>
wrote:

> Hi, Rufus,
>
> as we previously discussed, I totally agree on moving the datasets on
> br.ckan.net to datahub.io.
> I just haven't got the time to write the migration scripts yet, but I
> think that by the end of October I'll probably have been able to.
>
> Best regards,
> Augusto Herrmann
>
-------------- Próxima Parte ----------
Um anexo em HTML foi limpo...
URL: <http://lists.okfn.org/pipermail/okfn-br/attachments/20141113/132c631a/attachment-0004.html>