Ian Ward

+1 We could also have datapusher and xloader populate the data dictionaries 'labels' with the original column names. As for taking a bunch of column names and transforming them into...

I created a milestone for some important features it would be nice to have merged for 3.0 https://github.com/ckan/ckan/milestone/14

The only truth is code that's working, reviewed, and merged :sunglasses: This repo is no longer updated but some of the current important feature work has been collected under https://github.com/ckan/ckan/projects/4...

I love the idea to add a notice for sysadmins when a new ckan version is available. If we run the service that reports latest versions ourselves this would also...

It would be great to have a snapshot of the final JSON result of the activity along with some kind of diff (line based diff seems silly) of the before+after...

git repos don't let you delete old revisions, and the tools only give you line diffs (we could compute JSON diffs ourselves, of course)

We spoke about this in the dev meeting today. This change should be implemented in four steps: 1. Make revisioning optional a. change all queries (except ones for revision pages)...

Are we willing to release a version of ckan with no revisions at all and nothing in activities that replaces them? (instead of just an option to disable them) I...

@davidread item 2 in https://github.com/ckan/ideas-and-roadmap/issues/41#issuecomment-44559631 (storing complete before/after json versions of datasets within activities) is not implemented yet, but item 1 would be really useful even before that happens. We've...

I've changed my mind about extending activities but we do need something for old versions of data that would make reverting changes possible. @rgrp suggested sqlalchemy changesets as apossibility https://github.com/ckan/ideas-and-roadmap/issues/41#issuecomment-40396810