[ckan-dev] Middleware-components

Fri Oct 3 13:17:05 UTC 2014

In which case, do look at datapusher, as that is for automatic
transfer of data into the CKAN DataStore.
http://datapusher.readthedocs.org/en/latest/

David

On 3 October 2014 14:02, Henrik Aagaard Jørgensen <BU1G at tmf.kk.dk> wrote:
> Hello David,
>
> I'm mostly interested in exact data and not metadata.
> I want to import data into the datastore from various sources such as other PostgreSQL, Oracle, Window Shares, FTP etc.
>
>
> -----Oprindelig meddelelse-----
> Fra: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org] På vegne af David Read
> Sendt: 3. oktober 2014 14:52
> Til: CKAN Development Discussions
> Emne: Re: [ckan-dev] Middleware-components
>
> Henrik,
>
> Yes there are a number of CKAN harvesters around that cover the main metadata formats (DCAT/data.json, GEMINI/ISO19139). You can write custom harvesters for the databases you mention, and manage them using the web interface. Check out ckanext-harvest for more info.
>
> David
>
>
> On 30 September 2014 11:18, Henrik Aagaard Jørgensen <BU1G at tmf.kk.dk> wrote:
>> We’re using CKAN at the municipality of Copenhagen and are very
>> pleased with the project.
>>
>>
>>
>> I would like to know if there’s any work being done on some sort of
>> middleware clients for retrieving data from various places?
>>
>>
>>
>> Currently we are building our own small middleware components which
>> can access either other PostgreSQL-databases, Oracle and MSSQL,
>> Windows Shares etc. for retrieval of data and posting it towards a CKAN resource.
>>
>>
>>
>> Basically it’s just a number of independent Python scripts which runs
>> every X minute in a cronjob on Ubuntu.
>>
>>
>>
>> It would be very interesting to hear, know or explore more about some
>> more generic middleware clients which could keep datasets more and
>> better up-to-date.
>>
>>
>>
>> I do believe many CKAN projects could benefit from such.
>>
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> https://lists.okfn.org/mailman/listinfo/ckan-dev
>> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev