New CKAN patch releases: 2.12.1 and 2.11.7 bring seven security fixes
New patch releases are now available for CKAN 2.12.x and 2.11.x, fixing seven security vulnerabilities and several bugs. Upgrade as soon as possible.
November’s CKAN Site of the Month is the City of Toronto’s Open Data Portal. Toronto launched its first open data website in 2009, adopted CKAN as the portal’s backend in 2018, and documents its work in public, from a yearly roadmap to quarterly updates.
What makes Toronto worth studying isn’t the software. It’s how the team treats the portal: as a public service that keeps improving, with decisions based on evidence and problems reported openly. Here are five lessons other portal teams can borrow.
Toronto realised that counting datasets encouraged publishing more, rather than making existing data more useful. The risk was a catalogue full of outdated or poorly documented data. So the team now scores the quality of its datasets and shows the grade on each dataset page.
How the score works. In Toronto’s own model (2023 update), each dataset is scored on five dimensions: freshness (35%), metadata (35%), accessibility (15%), completeness (10%) and usability (5%). Datasets scoring 80 or more are graded Gold, 60 to 79 Silver, and below 60 Bronze.
Why it matters. Freshness and metadata together make up 70% of the score, which puts the emphasis on whether data is current and understandable. Data stored in the portal’s database, rather than as a file, scores higher on accessibility, because the portal can then offer a preview and several download formats. The scores themselves are published as an open dataset, updated weekly. Toronto’s roadmap includes an upgrade to the score in Q4 2026. The scoring model is Toronto’s own work, built on top of CKAN, not a built-in CKAN feature.
A bigger catalogue isn’t a better one. Quality is what people can use.
When Toronto redesigned its dataset pages in 2025, the team didn’t rely on assumptions. It researched how people actually use open data: it reviewed 13 other data portals, collected 53 survey responses and ran 16 usability interviews.
What changed. Before, field definitions, the quality score and the data preview were only available for a dataset’s first resource. The redesigned pages, launched in July 2025, show that information for every resource, with less clutter and less scrolling.
Research first, then redesign. Users show you what to fix.
Toronto combines WordPress for its public-facing website, data stories and blog with CKAN for data management and APIs. Toronto chose this combination to make it easier to keep developing the portal together with its open data community, and separating the experience people see from the engine that stores and serves the data lets the team shape each one around its needs.
Open by default. Toronto publishes its portal customisations and CKAN extensions on GitHub, so other portal teams can read the code and learn from the implementation. One example is ckanext-iotrans, which converts large datasets into different file formats and map projections, packaged so other organisations using CKAN can reuse it.
A flexible front end, a solid data engine. Both open source.
In 2023, Toronto moved to centralise open data publishing through its portal. City divisions get guidance on preparing, publishing and maintaining datasets, and by 2024, 43 of the City’s 44 divisions were represented in the catalogue.
Requests in the open. Anyone can request a dataset and follow requests on the portal’s public request page, including the ones the team can’t take on.
Software publishes data. Processes keep it useful.
Beyond the portal, Toronto runs the Toronto Open Data Awards, hands-on Open Data Jams and demo nights, a gallery of projects built with City data, and data stories on its blog, including community contributions.
Not without challenges. Toronto openly reports its operational challenges, including a growing backlog of dataset requests and technical debt, in its quarterly updates, and even publishes its API usage as open data. The team has also been working on a new Open Data Policy, with clearer roles and responsibilities.
Treating the portal as a product shows in what the team ships. A few recent examples, all documented in Toronto’s quarterly updates:
Know a CKAN portal that deserves the spotlight? Nominate it for Site of the Month. Built something with Toronto’s open data? The Toronto Open Data Awards are open for submissions until 4 December 2026.
Have questions or ideas to share with other portal teams? Join the conversation on Gitter / Matrix or open a discussion on GitHub.
New patch releases are now available for CKAN 2.12.x and 2.11.x, fixing seven security vulnerabilities and several bugs. Upgrade as soon as possible.
data.gov.gr now holds 22,000+ datasets from 510+ public bodies, with DCAT-AP metadata, quality scores and harvesting into data.europa.eu