[ckan-dev] Help shape the CKAN roadmap

Tue Jun 25 13:33:55 UTC 2013

Thanks Irina,

I certainly don't want to take credit for my namesake's contributions! I
will add these all to the roadmap.

We work in a multilingual environment, so I appreciate how difficult it is
to get right. I think for CKAN to do this, it will mean a significant
change that goes beyond a simple feature request. I will try to describe
the requirement on the roadmap.

I will also try to get a copy of the accessibility audit we had done and
see if I can share that with the community,

Also, Ian and I talked with you some time ago about workflow in CKAN, so I
will try to document that as well.

Cheers,
Ross

On 25 June 2013 06:52, Adrià Mercader <adria.mercader at okfn.org> wrote:

> Hi Ross,
>
> Thanks a lot for your feedback.
>
> On 24 June 2013 16:58, Ross Thompson <ross.thompson.ca at gmail.com> wrote:
> > in implementing data,gc.ca with CKAN 2.0, there were three areas we had
> to
> > work around. These were:
> >
> > 1. True support for multilingualism is missing in CKAN. Multilingualism
> to
> > us means much more than string translation, it means support for separate
> > language entities such as English tags and French tags, and English and
> > French values for fields in the dataset.
> As pointed out by others this will be discussed soon to see if we can
> come up with a good plan. It is a tricky one to get right.
>
>
> > 2. Performance issues when dealing with 180000+ datasets. Loading and
> > updating larges numbers of datasets through the API can take a weekend.
> Yes, this is known issue, and I guess a testament of CKAN success as
> it is being pushed further that was originally built for :)
> We've compiled perfomace tips discussed during the development of the
> Canadian and US portals and started a wiki page:
>
> https://github.com/okfn/ckan/wiki/Performance-tips-for-large-imports
>
> Hopefully some of the approaches will find a way to core, but in these
> scenarios there is a big variation on each projects needs and designs.
>
>
> > 3. Accessibility issues were identified with the user interface and
> > especially with search. We can certainly feed some of these back to OKFN
> > that were identified by our accessibility team.
> It would be awesome to have this kind of feedback and find ways to
> incorporate them in next versions. Feel free to send them round the
> list or create GitHub issues.
>
>
> > These seem a little bigger than just feature requests, so I thought this
> > might be a better forum to raise these points than just adding them to
> the
> > road map.
> >
> > In general though, the reaction to the new implementation of our new open
> > data portal with CKAN 2.0 has been really positive, so please don't take
> > these as complaints! We're really looking forward to doing even more with
> > it.
> Great to hear it
>
>
> > Thanks,
> > Ross
> > Statistics Canada
> >
> >
> >
> >
> > On 24 June 2013 10:51, Mark Wainwright <mark.wainwright at okfn.org> wrote:
> >>
> >> Hi all,
> >>
> >> Now that CKAN 2.0 is out, what should the next direction be for CKAN?
> >> We've created a public roadmap and wiki page to help everyone shape
> >> the direction of CKAN by voting and commenting, contributing,
> >> supporting and suggesting new features.
> >>
> >> For full details, see Ira's blog post here:
> >>
> >> http://ckan.org/2013/06/24/ckan-roadmap-goes-public/
> >>
> >> Mark
> >>
> >>
> >>
> >> --
> >> Business development and user engagement manager
> >> The Open Knowledge Foundation
> >> Empowering through Open Knowledge
> >> http://okfn.org/  |  @okfn  |  http://ckan.org  |  @CKANproject
> >>
> >> _______________________________________________
> >> 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
> >
> >
> >
> > _______________________________________________
> > 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
> >
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130625/fd6860ee/attachment-0001.html>