[ckan-discuss] Getting started with CKAN Norway (no.ckan.net)
david.read at okfn.org
Wed Feb 24 17:44:52 GMT 2010
Great to see the i18n wiki take shape - cheers for the work on this guys.
We have some docs already for the web importer here:
It's not finished, but you can get an idea of where it's at at:
Do email feedback if you have ideas where this could go and who can
contribute to the code.
As far as customizing the front-end, I assume you mean the package
read/edit pages? Currently we are customizing a package edit form for
government - you can see this in the code at ckan/forms/package_gov.py
but the read side is not customized. And I'm not convinced this is
best way to proliferate with more forms. A more easily pluggable form
schema and pluggable fields may well be valuable enough to work
On 24 February 2010 12:58, Daniel Dietrich <daniel.dietrich at okfn.org> wrote:
> Dear Jonathan,
> On 24.02.2010, at 13:41, Jonathan Gray wrote:
>> On Wed, Feb 24, 2010 at 10:54 AM, David Read <david.read at okfn.org> wrote:
>>> It sounds like it is well worth capturing the learning about
>>> translations on a wiki page as we go along.
>> Daniel, David and I started a page for this at:
>> Any additional information from those who have been involved in
>> translation would be *very* much appreciated to help make the process
>> easy and clear for others!
>>> We're also working on a web UI to a spreadsheet importer, but the
>>> disadvantage of that is that you have arrange the spreadsheet exactly
>>> as it will appear in the db - no facility for renaming columns or
>>> munging the data in them, e.g. add a date of import or to extract tags
>>> from other fields.
>> Would also be great to start a page on the wiki for this, outlining
>> options. E.g.
>> What do you think?
> Yes, that is definitely a good idea. And one for customizing / building custom front ends for CKAN, like:
> What do you think?
More information about the ckan-discuss