[ckan-dev] Recent CKAN development

Matthew Fullerton matt.fullerton at gmail.com
Mon Sep 26 13:32:26 UTC 2016


+1 for streaming; interactive hangout would be even better

--
Matt Fullerton
Software development and data science for open data and mobility
matt at crowdsalad.de
+49 89 7456 0495 / +49 176 5789 6501
http://www.crowdsalad.de

On 26 September 2016 at 13:21, Adrià Mercader <adria.mercader at okfn.org>
wrote:

> Hi all,
>
> We will be able to go through these and other new developments on the
> tech track next week at CKANCon. Hopefully we will be able to stream
> and/or record it for those not able to attend.
>
> Adrià
>
> On 24 September 2016 at 18:57, Ian Ward <ian at excess.org> wrote:
> > Yes, a blog post is a great idea. There's a small example extension of
> > a "proposed dataset" workflow included in CKAN now
> > https://github.com/ckan/ckan/blob/master/ckanext/example_
> ipermissionlabels/plugin.py
> >
> > Much more complicated workflows can be built in the same way.
> > Permission labels are really flexible.
> >
> > Ian
> >
> > On Sat, Sep 24, 2016 at 4:54 AM, David Miller
> > <david at openhealthcare.org.uk> wrote:
> >> Hi Ian,
> >>
> >> If I understand these properly, then 1 & 2 are really great news !
> >>
> >> With a previous project we had to find non-CKAN processes to cope with
> >> several data flows within institutions because users found the
> permissions /
> >> search / list behaviour too limited / confusing and we didn't have
> enough
> >> project capacity to dive into CKAN and fix/patch the internals.
> >>
> >> Keep up the great work !
> >>
> >> (P.S. I'm sure others on our team would appreciate a blog post
> outlining how
> >> these new permissions can be used to enable alternative data flows from
> a
> >> user perspective.)
> >>
> >> Best
> >>
> >> David Miller
> >> Open Health Care
> >>
> >> On Fri, 23 Sep 2016 at 16:37 Ian Ward <ian at excess.org> wrote:
> >>>
> >>> Hello everyone,
> >>>
> >>> I'd like to draw attention to a few features recently added to ckan
> >>> master.
> >>>
> >>> 1. Private datasets are now included on main /dataset/ search page.
> >>>
> >>> We used to have to go to the organization pages to see private
> datasets,
> >>> but
> >>> now they are included in the normal search page. The package_search
> >>> API is more complete now too, if you want private datasets returned
> >>> just pass include_private=True. This change will be available in the
> >>> upcoming CKAN 2.6 release. Full details are in
> >>> https://github.com/ckan/ckan/pull/3191
> >>>
> >>> 2. New interface for fine-grained permissions
> >>>
> >>> It used to be very difficult to enforce custom dataset permission
> >>> rules by overriding the package_show auth and overriding the
> >>> package_search controller. Now we have a single simple interface that
> >>> lets us set which users can see which datasets: IPermissionLabels.
> >>> This change will be available in the upcoming CKAN 2.7 release. Full
> >>> details are in https://github.com/ckan/ckan/pull/3192
> >>>
> >>> 3. New standard for background jobs
> >>>
> >>> CKAN 2.7 will come with a standard way to schedule, query and cancel
> >>> background jobs based on python-rq. This will greatly simplify all
> >>> sorts of extensions that operate on uploaded data or call out to
> >>> external services. Full details are in
> >>> https://github.com/ckan/ckan/pull/3165
> >>>
> >>> There's lots more coming in the next few months, including our first
> >>> controller fully migrated to Flask; extending and improving
> >>> activities; per-plugin extras for users, datasets, groups and orgs.
> >>>
> >>> A big thanks to everyone involved, and if you're coming to CKANCon
> >>> I'll see you in about 10 days!
> >>>
> >>> Ian
> >>> _______________________________________________
> >>> 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
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20160926/0750bf1e/attachment-0003.html>


More information about the ckan-dev mailing list