[ckan-dev] questions on resources import / export

[Adrià Mercader]

Hi,

I agree with Emanuele, CKAN and GeoNetwork, although sharing some
functionality, are different tools with different audiences.
A good project will choose the right tool or integrate different tools
to provide the best solution to its use case.

On 21 October 2013 10:26, Emanuele Tajariol <etj at geo-solutions.it> wrote:
>> GN was also among the candidates for the geographical metadata, but some
>> partners reported some issues so we're actually discarding it.
>
> What's great about open source products is the fact you have communities to
> discuss (and solve problems) with ;)
Big +1. Any feedback that you can report to the project will be
useful, even negative.


Adrià



>
>    Cheers,
>    Emanuele
>
>
> PS: I guess this thread would fit better in ckan-discuss that -dev.
>
>
> Alle 10:16:47 di Monday 21 October 2013, Elena Camossi ha scritto:
>> Dear Emanuele,
>>
>> thanks a lot for your opinion, very much appreciated.
>> We're defining the architecture of our system that will encompass CSW and
>> non CSW harvesting from several geographical sources, and from
>> non-geographical catalogues  as well. Our Idea is to test both CKAN  and
>> DKAN and their geographical extensions for our catalogue, but we are also
>> interested to understand the possible interactions among the two solutions.
>> GN was also among the candidates for the geographical metadata, but some
>> partners reported some issues so we're actually discarding it.
>>
>> What was you're experience with using GN? Did you have the opportunity to
>> compare it with CKAN and it's geographical extension for example?
>>
>> Kind regards,
>> -Elena
>>
>> > -----Original Message-----
>> > From: Emanuele Tajariol [mailto:etj.mlist at gmail.com]
>> > Sent: mercoledì 16 ottobre 2013 18:02
>> > To: Elena Camossi
>> > Cc: ckan-dev at lists.okfn.org
>> > Subject: Re: [ckan-dev] questions on resources import / export
>> >
>> > Hi Elena,
>> >
>> > in a couple of deploy we did, we used CKAN and GeoNetwork in the same
>> > node.
>> > CKAN is used as user frontend, and publishes both geo and non-geo
>> > datasets.
>> > GeoNetwork is used for CSW access.
>> > CKAN harvests the geographic metadata from GN using CSW, while the non-
>> > geo dataset are edited directly on CKAN. Geographic metadata are of
>> > course edited on GeoNetwork.
>> >
>> > If you have different catalogues that should interact, it's usually a
>> > good
>>
>> idea
>>
>> > to use existing standards (CSW for geographic datasets, for instance).
>> > Using internal formats (such as querying Solr) may be more efficient, but
>> > then you would be tied to a specific version of the application and its
>>
>> internal
>>
>> > model; some more work would be needed every time internal formats
>> > change.
>> > Just my 2¢ :)
>> >
>> >    Cheers,
>> >    Emanuele
>> >
>> > Alle 16:03:03 di Tuesday 15 October 2013, Elena Camossi ha scritto:
>> > > Dear all,
>> > >
>> > > I'm a newbie to CKAN and I'm trying to understand how to define a
>> > > possible architecture for a platform for data sharing we're going to
>>
>> develop.
>>
>> > > Both geographical and traditional (non-geographical) resources will be
>> > > included, and these will be harvested from different providers.
>> > >
>> > > For what concern the consumption of resources by other internal
>> > > catalogue platforms (different from CKAN, e.g., DKAN, GeoNetwork),
>> > > what can be the most EFFICIENT solution?
>> > > Exposing CKAN (for non-geographical) and CSW (for geographical
>> > > resource) services and let these other catalogues harvest the resources
>> >
>> > from CKAN?
>> >
>> > > Is it possible to make another catalogue interact with the CKAN
>> > > instance directly at Solr level, avoiding the catalogue services? Or
>> > > is it necessary to pass through the Datastore API?
>> > >
>> > > I hope this is not too confusing...
>> > > Thanks a lot for any suggestion.
>> > > Regards,
>> > > -Elena
>> >
>> > --
>
>
> --
> ==
> Our support, Your Success!
> Visit http://opensdi.geo-solutions.it for more information.
> ==
>
> Ing. Emanuele Tajariol
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax:    +39 0584 1660272
> mob:   +39 380 2116282
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev