Support Us

You are browsing the archive for Releases.

CKAN 1.5.1

January 24, 2012 in Feature, Releases

CKAN release 1.5.1 is now available. A major new feature is supporting running background tasks, which we will be using for downloading the data for each catalogued dataset. This will allow us to more easily preview it, search within it, and provide an API too.

Also included is a security fix that affected just the CKAN 1.5 release. All known servers have now been upgraded. The nature of the issue is embargoed for two weeks, to allow any further installations of this version to be upgraded.

There are also UI improvements to the resource and group editing pages, plus CKAN’s language coverage now covers even more languages (thanks to the large international community of CKAN users).

OKF provide both an easy-to-use install package for Ubuntu 10.04 (at apt.ckan.org) as well as general source install (from Github or PyPi). For full install and upgrade instructions see: http://readthedocs.org/docs/ckan/en/ckan-1.5.1/

Here’s the full Change Log of changes since the previous release 1.5 (2011-11-07):

CKAN v1.5.1

Major:

  • Background tasks (#1363, #1371, #1408)
  • Fix for security issue affecting CKAN v1.5 (#1585)

Minor:

  • Language support now excellent for European languages: en de fr it es no sv pl ru pt cs sr ca
  • Web UI improvements:
    • Resource editing refreshed
    • Group editing refreshed
    • Indication that group creation requires logging-in (#1004)
    • Users’ pictures displayed using Gravatar (#1409)
    • ‘Welcome’ banner shown to new users (#1378)
    • Group package list now ordered alphabetically (#1502)
  • Allow managing a dataset’s groups also via package entity API (#1381)
  • Dataset listings in API standardised (#1490)
  • Search ordering by modification and creation date (#191)
  • Account creation disallowed with Open ID (create account in CKAN first) (#1386)
  • User name can be modified (#1386)
  • Email address required for registration (for password reset) (#1319)
  • Atom feeds hidden for now
  • New config options to ease CSS insertion into the template (#1380)
  • Removed ETag browser cache headers (#1422)
  • CKAN version number and admin contact in new ‘status_show’ API (#1087)
  • Upgrade SQLAlchemy to 0.7.3 (#1433)
  • SOLR schema is now versioned (#1498)

Bug fixes:

  • Group ordering on main page was alphabetical but should be by size (since 1.5) (#1487)
  • Package could get added multiple times to same Group, distorting Group size (#1484)
  • Search index corruption when multiple CKAN instances on a server all storing the same object (#1430)
  • Dataset property metadata_created had wrong value (since v1.3) (#1546)
  • Tag browsing showed tags for deleted datasets (#920)
  • User name change field validation error (#1470)
  • You couldn’t edit a user with a unicode email address (#1479)
  • Package search API results missed the extra fields (#1455)
  • OpenID registration disablement explained better (#1532)
  • Data upload (with ckanext-storage) failed if spaces in the filename (#1518)
  • Resource download count fixed (integration with ckanext-googleanalytics) (#1451)

CKAN 1.5 release

November 9, 2011 in Releases

We’re proud to announce a major new release of CKAN! 1.5 represents a big step forward since our last major release in May. Alongside our usual PyPI release, we are now also releasing regular Ubuntu 10.04 packages, for easy installation.

So now it’s (almost) as simple as “apt-get install ckan” and “ckan-create-instance” Here are the docs: http://docs.ckan.org/docs/ckan/en/ckan-1.5/install-from-package.html

Major changes since 1.4:

  • official government data stores are usually Read-Only to the public, but now we’ve added Moderated Edits, to allow the public to suggest changes and correct metadata. Once suggestions are moderated by the officials, everyone can benefit from the improvements.
  • we got rid of a form framework that was difficult to customise. Now web designers can play about with the form’s HTML/CSS/Javascript to get it exactly how they want. They can do take advantage of autocomplete and other tools in our new powerful Action API. And when the form submits, the data goes through a new schema validation system. We spent a long time planning this, evaluating all sorts of systems and now we’re really pleased with the results.
  • total visual overhaul for viewing and editing datasets
  • vastly improved informatinoa about CKAN and user documentation (ckan.org, wiki.ckan.org & docs.ckan.org)

Plus hundreds of little things like: Captcha to keep spammers at bay, calling them ‘datasets’ rather than pushing our concept of ‘packages’ and fixing the odd bug that crops up too.

We’re also really proud of the recent work in CKAN extensions, such as for handling geographic data, harvesting data from other data stores and providing APIs for data in the catalogue with Web Store.

Thank you to the amazing on-line community for their continued ideas, suggestions and support in the development of this open source data hub software.

Here’s the full changelog, listing all the changes since the most recent minor release (1.4.3.1, 30th September):

v1.5 2011-11-07

Major: * New visual theme (#1108) * Package & Resource edit overhaul (#1294/#1348/#1351/#1368/#1296) * JS and CSS reorganisation (#1282, #1349, #1380) * Apache Solr used for search in core instead of Postgres (#1275, #1361, #1365) * Authorization system now embedded in the logic layer (#1253) * Captcha added for user registration (#1307, #1431) * UI language translations refreshed (#1292, #1350, #1418) * Action API improved with docs now (#1315, #1302, #1371)

Minor: * Cross-Origin Resource Sharing (CORS) support (#1271) * Strings to translate into other languages tidied up (#1249) * Resource format autocomplete (#816) * Database disconnection gives better error message (#1290) * Log-in cookie is preserved between sessions (#78) * Extensions can access formalchemy forms (#1301) * ‘Dataset’ is the new name for ‘Package’ (#1293) * Resource standard fields added: type, format, size (#1324) * Listing users speeded up (#1268) * Basic data preview functionality moved to core from QA extension (#1357) * Admin Extension merged into core CKAN (#1264) * URLs in the Notes field are automatically linked (#1320) * Disallow OpenID for account creation (but can be linked to accounts) (#1386) * Tag name now validated for max length (#1418)

Bug fixes: * Purging of revisions didn’t work (since 1.4.3) (#1258) * Search indexing wasn’t working for SOLR (since 1.4.3) (#1256) * Configuration errors were being ignored (since always) (#1172) * Flash messages were temporarily held-back when using proxy cache (since 1.3.2) (#1321) * On login, user told ‘welcome back’ even if he’s just registered (#1194) * Various minor exceptions cropped up (mostly since 1.4.3) (#1334, #1346) * Extra field couldn’t be set to original value when key deleted (#1356) * JSONP callback parameter didn’t work for the Action API (since 1.4.3) (#1437)

CKAN release 1.4.3

September 14, 2011 in Releases, Uncategorized

Today we released a new version of CKAN (1.4.3) which covers a good number of bug fixes, speed ups and some new features. The release is on PyPI and source is at BitBucket.

For example, now you can view a dataset as it was in CKAN at a past date or revision using an @ parameter e.g. http://thedatahub.org/dataset/osm@2011-6-1. Also we’ve put in links to these old versions into the revision history view e.g. http://thedatahub.org/dataset/history/osm.

Another cool thing we’ve added is the “Action API” to try out. The existing v1 and v2 APIs are still there for main use, but we’re putting the v3 out in this release as a ‘beta’ for feedback. The key difference is that instead of being RESTful, it’s RPC style. It is more powerful than existing APIs and aims to give better help feedback when things, so good for using it in Javascript etc. The docs are here: Action API Docs and please let us know how you find it so far.

Here’s the changelog about this release:

v1.4.3 2011-09-13

Major:

  • Action API (API v3) (beta version) provides powerful RPC-style API to CKAN data (#1335)
  • Documentation overhaul (#1142, #1192)

Minor:

  • Viewing of a package at a given date (as well as revision) with improved UI (#1236)
  • Extensions can now add functions to the logic layer (#1211)
  • Refactor all remaining database code out of the controllers and into the logic layer (#1229)
  • Any OpenID log-in errors that occur are now displayed (#1228)
  • ‘url’ field added to search index (e9214)
  • Speed up tag reading (98d72)
  • Cope with new WebOb version 1 (#1267)
  • Avoid exceptions caused by bots hitting error page directly (#1176)
  • Too minor to mention: #1234,

Bug fixes:

  • Re-adding tags to a package failed (since 1.4.1 in Web UI, 1.4 in API) (#1239)
  • Modified revisions retrieved over API caused exception (since 1.4.2) (#1310)
  • Whichever language you changed to, it announced “Language set to: English” (since 1.3.1) (#1082)
  • Incompatibilities with Python 2.5 (since 1.3.4.1 and maybe earlier) (#1325)
  • You could create an authorization group without a name, causing exceptions displaying it (#1323)
  • Revision list wasn’t showing deleted packages (b21f4)
  • User editing error conditions handled badly (#1265)

Release 1.4.2

August 5, 2011 in Releases

Today we released CKAN 1.4.2 to PyPI, which includes support in the model for edit moderation (which is used by this CKAN extension) and a password reset facility. There are also a number of minor features and bugfixes we covered in the five weeks since the previous release.

CKAN v1.4.2 2011-08-05

Major:

  • Packages revisions can be marked as ‘moderated’ (#1141)
  • Password reset facility (#1186/#1198)

Minor:

  • Viewing of a package at any revision (#1236)
  • API POSTs can be of Content-Type “application/json” as alternative to existing “application/x-www-form-urlencoded” (#1206)
  • Caching of static files (#1223)

Bug fixes:

  • When you removed last row of resource table, you could’t add it again – since 1.0 (#1215)
  • Adding a tag to package that had it previously didn’t work – since 1.4.1 in UI and 1.4.0 in API (#1239)
  • Search index was not updated if you added a package to a group – since 1.1 (#1140)
  • Exception if you had any Groups and migrated between CKAN v1.0.2 to v1.2 (migration 29) – since v1.0.2 (#1205)
  • API Package edit requests returned the Package in a different format to usual – since 1.4 (#1214)
  • API error responses were not all JSON format and didn’t have correct Content-Type (#1214)
  • API package delete doesn’t require a Content-Length header (#1214)

CKAN release 1.4.1

June 27, 2011 in Feature, Releases

Today we have released version 1.4.1 of CKAN, which includes an important refactor to make it simpler to create custom package editing forms – see more about this exciting feature below. There are also a selection of minor improvements, for instance adding ‘nofollow’ to reduce link spam.

Changelog v1.4.1 2011-06-27

Major:

  • Refactor Web interface (including ‘package edit’ form) to use logic layer rather than model objects directly (#1078)

Minor:

  • Links in user-supplied text made less attractive to spammers (nofollow) (#1181)
  • Package change notifications – remove duplicates (#1149)
  • Metadata dump linked to (#1169)
  • Refactor authorization code to be common across Package, Group and Authorization Group (#1074)

Bug fixes:

  • Duplicate authorization roles were difficult to delete (#1083)

New forms

Editing packages is at the heart of CKAN, and a lot of organisations running CKAN have customised the edit form.

In the past this was done all in Python code, reusing or creating new ‘widgets’ based on FormAlchemy, and this generated the form HTML. This worked well, but you needed to know Python, and sometimes it was not clear how to tweak the resulting HTML.

Now with CKAN release 1.4.1 we have a new form infrastructure where the list of fields (and any extra validation required) is defined in a very simple schema, and the form is designed completely in an HTML template. This means that the much larger pool of web designers can tweak the drop-down combos etc. without having to touch any Python.

To give you a flavour of editing the package form, here is the default HTML template (as used on ckan.net): new_package_form.html and here are the instructions for the set-up required: Forms using Templates.

Legacy forms using FormAlchemy are deprecated, but can still be used with the current release, to ease transition. For more information, see the docs on Forms using FormAlchemy.

Follower Extension for CKAN

May 20, 2011 in Extensions, Releases

Today we’re announcing the release of Follower, a new extension for CKAN. This feature enables users to follow CKAN packages, which can be viewed as analogous to following repositories on Bitbucket or Github, or following people on Twitter.

When the extension is installed, two new buttons will appear below the title of each package page. The first shows the number of people that are currently following the package and the second allows the current user to follow and unfollow the package if they are logged in.

Package page with follow buttons

Package page with follow buttons

If there are people following the package, clicking on the follower count (first button) will bring to you a page that lists the people that are following the package.

Page listing people following a package

Page listing people that are following a package

Every user will also have a list of packages that they are following shown in their account overview (the third item in the Activity section, shown below).

Followed packages shown on user's account overview

Followed packages shown on user's account overview

Future Development

This is a beta release so there is plenty of room for improvement. Planned updates include:

  • Making a page or widget showing the most followed packages, or most recently followed packages.
  • Giving users an activity stream based on their followed packages, showing a list of recent updates to the packages for example.

Do you have any other suggestions for improvements? Please let us know.

More Information

You can see the extension in action now on CKAN.net. To get the extension or for more information, see the code repository at: http://bitbucket.org/okfn/ckanext-follower

CKAN 1.4 release

May 19, 2011 in Releases

Today we’ve released a new version of CKAN at PyPI. Version 1.4 covers updates to the core code during the last five weeks of development. As seen at ckan.net, users have improvements for viewing alternative metadata formats and changing authorization settings, whilst administrators benefit from improved tools to manage unwanted revisions. The full changelog is copied below.

Alongside with these changes to the core CKAN, arguably the more exciting features in CKAN are now being added as ‘extensions’. Examples of recent extensions include: previewing of data, storage for data, automatic link checking, data click-through counts and harvesting of metadata from other catalogues. Further information here.

Changelog – CKAN 1.4

Major:

  • Authorization forms now in grid format (#1074)
  • Links to RDF, N3 and Turtle metadata formats provided by semantic.ckan.net (#1088)
  • Refactor internal logic to all use packages in one format – a dictionary (#1046)
  • A new button for administrators to change revisions to/from a deleted state (#1076)

Minor:

  • Etags caching can now be disabled in config (#840)
  • Command-line tool to check search index covers all packages (#1073)
  • Command-line tool to load/dump postgres database (#1067)

Bug fixes:

  • Visitor can’t create packages on new CKAN install – since v1.3.3 (#1090)
  • OpenID user pages couldn’t be accessed – since v1.3.2 (#1056)
  • Default site_url configured to ckan.net, so pages obtains CSS from ckan.net- since v1.3 (#1085)

Storage Extension for CKAN

May 16, 2011 in Extensions, Releases

Today we’re announcing the release of an important new feature for CKAN: integrated upload and storage support for datasets.

Until now CKAN has been limited to being a catalog — a place to list datasets but not to store them. Now you can upload datasets directly or as part of the process of registering a data package.

From our own experience, we know it’s really useful to be able to store material in this way and users have also been telling us this. Moreover, storage and a catalog are natural complements: when storing material you usually want to have a ‘catalog’ and when registering datasets one often wants to be able to upload material.

We also think that storage will be an essential facility for other tools that wish to build on CKAN — for example tools that transform, integrate or enrich existing datasets.

That’s why, in addition to having a standard web upload facility, there’s also a rich set of APIs including the ability to get and set metadata and acquire authentication credentials — something that will allow third party tools in possession of a valid CKAN API key to do direct uploads (we’ve already got an active discussion about direct uploads from Google Refine).

Lastly we should emphasize this is a beta release and there are still improvements to be made so if you spot a bug or have an idea for an improvement please let us know.

Screenshots

More Info

You can try out uploading a file on the CKAN demo instance at (you will need to login — use tester / tester as username and password):

http://test.ckan.net/storage/upload

CKAN release 1.3.3

April 8, 2011 in Feature, Releases

We released a new version of CKAN today – 1.3.3. It provides users with another three weeks of progress – a few useful additions and bugfixes. I’ve included the full changelog below, but the most interesting features are some security added to editing Groups and Package Relationships, and a useful new API for seeing who has edited a package.

v1.3.3 2011-04-08 Major:

  • Authorization checks added to editing Groups and PackageRelationships (#1052)
  • API: Added package revision history (#1012, #1071)

Minor:

  • API can take auth credentials from cookie (#1001)
  • Theming: Ability to set custom favicon (#1051)
  • Importer code moved out into ckanext-importlib repo (#1042)
  • API: Group can be referred to by ID (in addition to name) (#1045)
  • Command line tool: rights listing can now be filtered (#1072)

Bug fixes:

  • SITE_READ role setting couldn’t be overridden by sysadmins (#1044)
  • Default ‘reader’ role too permissive (#1066)
  • Resource ordering went wrong when editing and adding at same time (#1054)
  • GET followed by PUTting a package stored an incorrect license value (#662)
  • Sibling package relationships were shown for deleted packages (#664)
  • Tags were displayed when they only apply to deleted packages (#920)
  • API: ‘Last modified’ time was localised – now UTC (#1068)

CKAN v1.3 Released

February 18, 2011 in Releases

We’ve just released CKAN 1.3 which has been shown off on ckan.net during the past week. Below is a summary changelog of the major changes since we released v1.2 three months ago.

v1.3 2011-02-18

http://trac.ckan.org/milestone/ckan-v1.3

Highlights of changes:

  • Package edit form improved:
    • field instructions (#679)
    • name autofilled from title (#778)
  • Group-based access control – Authorization Groups (#647)
  • Metadata harvest job management (#739, #884, #771)
  • CSW harvesting now uses owslib (#885)
  • Package creation authorization is configurable (#648)
  • Read-only maintenance mode (#777)
  • Stats page (#832) and importer (#950) moved out into CKAN extensions

More minor:

  • site_title and site_description config variables (#974)
  • Package creation/edit timestamps (#806)
  • Caching configuration centralised (#828)
  • Command-line tools – sysadmin management (#782)
  • Group now versioned (#231)

Please create an account to get started.

Subscribe via email

Archives

Twitter

derPaddyderPaddy: RT @OKFN: Version 2.0 of the groundbreaking @CKANproject, world's leading #OpenSource #OpenData platform, released: http://t.co/CzR01z8kEV
21 hours ago
doclorrainedoclorraine: RT @vndimitrova: The timeline of #opendata with @agentGav and @UKODI at #opentech, including @rufuspollock @jwyg @OKFN and @CKANproject
2 days ago
vndimitrovavndimitrova: The timeline of #opendata with @agentGav and @UKODI at #opentech, including @rufuspollock @jwyg @OKFN and @CKANproject
2 days ago
frankolkenfrankolken: RT @OKFN: Version 2.0 of the groundbreaking @CKANproject, world's leading #OpenSource #OpenData platform, released: http://t.co/CzR01z8kEV
2 days ago
junszhaojunszhao: RT @OKFN: Version 2.0 of the groundbreaking @CKANproject, world's leading #OpenSource #OpenData platform, released: http://t.co/CzR01z8kEV
2 days ago