This project is not covered by Drupal’s security advisory policy.

Provides an upgrade path for DKAN sites moving to Drupal 9+.

  • Allows DKAN sites to maintain operation after Drupal 7 reaches End-Of-Life.
  • Maintains a consistent user experience for content maintainers already familiar with managing content within DKAN.
  • Integrates data library (e.g. datasets and resources ) and content management (e.g. basic page, story, dashboard) features into a single system, providing an integrated data portal + website platform.
  • Maintainable and extensible by website developers familiar with Drupal.

Project Homepage

https://www.ekan-data.org

Project documentation and roadmap

https://docs.google.com/document/d/1sPGp49Y09i67LjKqM-qYlj-gZ8Nkgh9PmeWC...

Installation (D9)

composer create-project eightyoptions/ekan_distribution:^1.1

Installation (>=D10)

composer create-project eightyoptions/ekan_distribution:^2.0

Upgrading (migrating) from DKAN

* Copy (or mount, or symlink) public and private files from your legacy DKAN site into the paths '/mnt/files/legacy_files/public' and 'mnt/files/legacy_files/private' respectively.

* Add a secondary database connection (called 'migrate') to the settings.php file in EKAN so that it can access the legacy DKAN database.
e.g.

$databases['migrate']['default'] = array(
  'driver' => 'mysql',
  'database' => 'drupal',
  'username' => 'drupal',
  'password' => 'drupal',
  'host' => '192.168.1.1',
  'port' => 43333
);

* Run the migration

drush en ekan_migrate
drush migrate:import --group=ekan

* Remove the secondary database connection and remove legacy files from /mnt/files/legacy_files.

Upgrade from 1.x to 2.x

There is basic support for updating from Drupal 9 to 10, the main change is the groups module has moved from 1.x to 2.x which comes with quite a few changes. see https://www.drupal.org/project/group/releases/2.0.0

Supporting organizations: 

Project information

  • Created by thtas on , updated
  • shield alertThis project is not covered by the security advisory policy.
    Use at your own risk! It may have publicly disclosed vulnerabilities.

Releases