DKAN Open Data Portal
Switch branches/tags
Clone or download
Permalink
Failed to load latest commit information.
.ahoy Pull in missing script changes (#2546) Jun 5, 2018
.circleci Restore circleci behat testing Jul 3, 2018
.github Remove changelog checkbox from PR template (#2563) Jun 14, 2018
docs Add UI to change allowed extensions (#2664) Oct 9, 2018
import Redo http to https updates (#2468) Apr 25, 2018
modules/dkan Add UI to change allowed extensions (#2664) Oct 9, 2018
patches Patch radix to pull bootstrap.min.js from nuboot_radix (#2692) Oct 11, 2018
test Update phpunit/dkan_dataset/getRemoteFileInfoTest.php test (#2673) Sep 25, 2018
themes/nuboot_radix Patch radix to pull bootstrap.min.js from nuboot_radix (#2692) Oct 11, 2018
.gitattributes Add .gitattributes file to avoid merge conflicts on CHANGELOG (#2028) Sep 14, 2017
.gitignore Ahoy/Docker/Proxy/Docker-sync/XDebug Updates (#2148) Nov 20, 2017
.probo.yml Move QA user creation function to ahoy dkan commands Jun 30, 2016
CHANGELOG.txt Update docs release notes (#2638) Aug 28, 2018
LICENSE.txt Adding LICENSE.txt Jul 1, 2014
README.md Fix typo (#2567) Jun 18, 2018
dkan-init.sh Move to GetDkan org (#2188) Nov 1, 2017
dkan.info Fixing linting issues with .info files. Jan 16, 2018
dkan.install Change default harvest source modified date to blank (#2526) May 31, 2018
dkan.profile Integration of changes from 1.13.5 into 7.x-1.x Jul 17, 2017
drupal-org-core.make Upgrade Drupal to 7.59 and Media to 2.9 (#2473) Apr 25, 2018
drupal-org.make Patch radix to pull bootstrap.min.js from nuboot_radix (#2692) Oct 11, 2018

README.md

DKAN Open Data Platform

DKAN is an open source open data platform with a full suite of cataloging, publishing and visualization features that allow organizations to easily publish data to the public.

Community

Join the DKAN Slack community.

Connect

Help

Features

For data publishers

  • Publish data through a guided process or import via API/harvesting from other catalogs
  • Customize your own metadata fields, themes and branding
  • Store data within DKAN or on external (e.g. departmental) sites
  • Manage access control, version history with rollback, RDF support, user analytics

For data users

  • Explore, search, add, describe, tag, group datasets via web front-end or API
  • Collaborate with user profiles, groups, dashboard, social network integration, comments
  • Use metadata and data APIs, data previews and visualizations
  • Manage access control, version history with rollback, INSPIRE/RDF support, user analytics
  • Extend and leverage the full universe of more than 18,000 freely available Drupal modules

Installation

Please see the Installation section of the DKAN Documentation.

Upgrading DKAN

Please see the Updating and Maintaining DKAN section of the DKAN Documentation for general upgrade information.

Releases

Check the releases page for latest DKAN Version. 7.x-1.x is the development branch.

Releases and release candidates

DKAN follows a modified semantic versioning convention, and has major, point (also known as minor), and patch releases.

The only major release of DKAN has been 7.x-1.0. It is unlikely there will be a 7.x-2.x version of DKAN but in the case of a major architecture change, this is possible. More likely is a 8.x-2.x release if and when DKAN is ported to Drupal 8. At the moment there is no work being done on a Drupal 8 version.

Point releases occur approximately every 1-2 months and include new functionality and architectural changes. For instance, DKAN 7.x-1.1 was the first point release, and 7.x-1.2 was the second. While we try to make updating as seamless as possible, point release updates often involve some work, especially if the website uses a custom theme or modules outside of what is included in the distro.

Patch releases, introduced after the release of DKAN 7.x-1.12, occur much more frequently, and include bug fixes, core and contrib module updates, and minor enhancements. The first patch release was version 7.x-1.12.1, the second was 7.x-1.12.2, and so on. Updating to a new patch release should be very straightforward and cause little to no distruption to a website.

Tags and branches

After a point release comes out, we create a release branch, on which we do any work intended for future patch releases on that version of DKAN. The release branch for version 7.x-1.12 development, for instance, is release-1-12. New features and other work destined for the next point release continues on the main development branch, 7.x-1.x.

We keep the DKAN profile (this project), DKAN Dataset, DKAN Datastore, DKAN Workflow and Recline versioning in sync. Other depdendencies that we maintain, incuding Open Data Schema Map and Visualization Entity follow their own, separate release cycle.

License

DKAN and related modules are freely-available under the GPLv2 (or later) license.

Contributing

Please file all tickets for DKAN in this issue queue. We have several labels in place for you to tag the issue with and identify it with the proper component.

Please follow the Ticket Template when creating new tickets.

Also, please remember to reference the issue across repositories in order for maintainers to pick up commits and pull requests looking at the issue. You can do that for commits like this:

git commit -m "Issue GetDKAN/dkan#<issue_number>: ..."

Just replace <issue_number> with the actual issue number. You can reference pull requests exactly like that if you add the same text "GetDKAN/dkan#<issue_number>" in a comment.

This helps us with detecting changes and pulling them in faster.