CKAN 2.11: what’s new, and why it’s worth the upgrade

CKAN, the open source platform behind thousands of data portals worldwide, brought a solid set of improvements in version 2.11. Here’s what changed, explained without the jargon.

The “datastore” is the part of CKAN that holds structured, tabular data (think spreadsheets and database tables, rather than files like PDFs or images). This release brought several improvements here.

The tool used to preview and browse data tables on the page (previously called the Recline view) has been replaced with a new Datatable view. It gives a cleaner, more dependable way to look through a dataset’s contents before downloading it.

The front end of CKAN now uses Bootstrap 5, a widely used design framework. In practice, this means a cleaner, more modern interface that’s also more accessible for users with different needs.

CKAN 2.11 also introduces initial, partial support for a technology called HTMX. This allows certain parts of a page to update instantly, without reloading the whole page, making everyday actions on the site feel quicker and smoother.

The underlying software components CKAN depends on have all been updated to their latest versions. This isn’t something users will notice directly, but it keeps the platform more secure, more stable, and easier to maintain over time.

CKAN 2.11 also brings the newer version of CKAN’s DCAT support needed to work with DCAT-AP HVD, the EU metadata standard for “high-value datasets”, public data the EU has identified as especially useful and wants published in a consistent, easy-to-find way across member states.

The upgrade itself doesn’t switch this on automatically, some configuration is still needed, but it’s the groundwork that makes it possible: proper fields for marking a dataset as high-value, with validation built in, rather than relying on manual workarounds. For any organisation that needs to meet these EU reporting requirements, this puts the pieces in place to do it properly.

Individually, these might sound like small technical tweaks. Together, they add up to a platform that’s faster, easier to manage, friendlier to work with, and better equipped to keep data organised and trustworthy. For anyone publishing open data, or relying on it, that’s a welcome step forward.

Beyond the features themselves, there’s a timing question worth addressing. 2.9 remains the most widely used version across the CKAN ecosystem, and it stopped receiving support some time ago, leaving portals exposed to unpatched vulnerabilities. CKAN 2.12 is also out, bringing a reworked theme and a new file handling process, but the changes from 2.11 to 2.12 are relatively contained. For a portal still on 2.9, the priority is getting to 2.11 first: that’s what restores a supported, secure footing, with 2.12 a smaller step to take from there.

You can read the official CKAN 2.11 announcement or dig into the full technical changelog if you’d like more detail.