[ckan-dev] CKAN new install

[Guillaume Sueur]

Hi Adrià,

I'll check that out.

By the way, I'm trying to add the dataset_extent_map to the dataset 
template, but the doc doesn't fit my templates content :

I don't even have a primary_content block in the read.html template, 
when the doc says to put it there :

{% block primary_content %}

   <!-- ... -->

   <article class="module prose">

     <!-- ... -->

     {% set dataset_extent = h.get_pkg_dict_extra(c.pkg_dict, 'spatial', 
'') %}
     {% if dataset_extent %}
       {% snippet "spatial/snippets/dataset_map.html", 
extent=dataset_extent %}
     {% endif %}

   </article>
{% endblock %}

Any clue ?

thanks

Le 12/12/13 10:56, Adrià Mercader a écrit :
> Hi Guillaume,
> All the merge activitiy is caused by us preparing the next stable
> release, 2.2 which should be out some time in January.
>
> We still haven't tested ckanext-spatial and harvest against it in depth,
> although this will be done as part of the release process.
> We always recommend using the latest stable release of CKAN core and the
> "stable" branch of spatial and harvest, which is kept backwards
> compatible. If you want to use master core, assume that some stuff might
> be buggy
>
> Cheers,
>
> Adrià
>
> On 12 Dec 2013 09:34, "Guillaume Sueur" <no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>> wrote:
>
>     Hi Tom,
>
>     It's indeed difficult to guess if master branches will fit together,
>     and which ones to use if not.
>     I've installed Ckan Master (2.2a) and I'm going to try to use
>     ckanext-spatial master branch with it. I will give feedback about it.
>
>     best regards
>
>     Le 11/12/13 13:30, Tom Kralidis a écrit :
>
>         On Tue, Dec 10, 2013 at 5:04 AM, Guillaume Sueur
>         <no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>>
>         wrote:
>
>
>             Hi list,
>
>             I've been testing CKAN 2.0 few months ago, and I would like
>             to setup a fresh
>             new install. It seems a lot of things happened on the github
>             repository
>             meanwhile, and it's still moving a bit (merges).
>             What can you advise me as a choice of branch for my new
>             install, knowing
>             that I'm particulary interested in CSW/Spatial extensions.
>
>
>         I'm not exactly sure about CKAN release patterns, but if I look
>         at the
>         ckanext-spatial branches, the are loosely mirrored after core ckan.
>         So release-v2.0 of ckanext-spatial looks like a safe option against
>         CKAN 2.0.*, which supports pycsw integration, as well as other
>         features.
>         _________________________________________________
>         ckan-dev mailing list
>         ckan-dev at lists.okfn.org <mailto:ckan-dev at lists.okfn.org>
>         http://lists.okfn.org/mailman/__listinfo/ckan-dev
>         <http://lists.okfn.org/mailman/listinfo/ckan-dev>
>         Unsubscribe: http://lists.okfn.org/mailman/__options/ckan-dev
>         <http://lists.okfn.org/mailman/options/ckan-dev>
>
>     _________________________________________________
>     ckan-dev mailing list
>     ckan-dev at lists.okfn.org <mailto:ckan-dev at lists.okfn.org>
>     http://lists.okfn.org/mailman/__listinfo/ckan-dev
>     <http://lists.okfn.org/mailman/listinfo/ckan-dev>
>     Unsubscribe: http://lists.okfn.org/mailman/__options/ckan-dev
>     <http://lists.okfn.org/mailman/options/ckan-dev>
>
>
>
> _______________________________________________
> 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
>