[ckan-discuss] CKAN integration with gridworks / refine

Tim McNamara paperless at timmcnamara.co.nz
Sat Nov 27 21:41:57 GMT 2010

On 28 November 2010 07:51, William Waites <ww at eris.okfn.org> wrote:

> Hi Rufus, I think this is a very good idea as well. One comment
> ] 4. On save (or perhaps as a separate option) they are prompted as to
> ] whether they wish  to sync the dataset back to CKAN (either as a new
> ] package or as a new resource on the existing package)
> I think this is very clearly a *new* dataset derived from the old
> one. We should even try to keep around the javascript blob that
> refine uses to express the modifications that were made so that
> it could be repeated if necessary, or checked or whatever.
> Cheers,
> -w

There's no requirement for CKAN to store the derived, clean versions of the
datasets. It makes more sense for CKAN to store the change history (which is
just a JSON object). This is how Google Refine is designed to work, and
would reduce the burden that CKAN would need to carry.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-discuss/attachments/20101128/c44b43ac/attachment.htm>

More information about the ckan-discuss mailing list