ckanext-doi

A CKAN extension for assigning a digital object identifier (DOI) to datasets, using the DataCite DOI service.

Overview

This extension assigns a digital object identifier (DOI) to datasets, using the DataCite DOI service.

When a new dataset is created it is assigned a new DOI. This DOI will be in the format:

https://doi.org/[prefix]/[8 random alphanumeric characters]

If the new dataset is active and public, the DOI and metadata will be registered with DataCite.

If the dataset is draft or private, the DOI will not be registered with DataCite. When the dataset is made active & public, the DOI will be submitted. This allows datasets to be embargoed, but still provides a DOI to be referenced in publications.

You will need an account with a DataCite DOI service provider to use this extension.

DOI Metadata

Uses DataCite Metadata Schema v4.2.

Dataset package fields and CKAN config settings are mapped to the DataCite Schema with default values, but these can be overwritten by implementing IDoi interface methods.

Required fields

See metadata.py for full mapping details.

Installation

Path variables used below:

• $INSTALL_FOLDER (i.e. where CKAN is installed), e.g. /usr/lib/ckan/default
• $CONFIG_FILE, e.g. /etc/ckan/default/development.ini

1. Clone the repository into the src folder:

cd $INSTALL_FOLDER/src
git clone https://github.com/NaturalHistoryMuseum/ckanext-doi.git

1. Activate the virtual env:

. $INSTALL_FOLDER/bin/activate

1. Install the requirements from requirements.txt:

cd $INSTALL_FOLDER/src/ckanext-doi
pip install -r requirements.txt

1. Run setup.py:

cd $INSTALL_FOLDER/src/ckanext-doi
python setup.py develop

1. Add ‘doi’ to the list of plugins in your $CONFIG_FILE:

ckan.plugins = ... doi

Configuration

There are a number of options that can be specified in your .ini config file.

DateCite Credentials [REQUIRED]

These will be given to you by your DataCite provider.

ckanext.doi.account_name = DATACITE-ACCOUNT-NAME
ckanext.doi.account_password = DATACITE-ACCOUNT-PASSWORD
ckanext.doi.prefix = DATACITE-PREFIX

Institution Name [REQUIRED]

You also need to provide the name of the institution publishing the DOIs (e.g. Natural History Museum).

ckanext.doi.publisher = PUBLISHING-INSTITUTION

Test/Debug Mode [REQUIRED]

If test mode is set to true, the DOIs will use the DataCite test prefix 10.5072.

ckanext.doi.test_mode = True or False

Other options

Further Setup

This extension will only work if you have signed up for an account with DataCite.

You will need a development/test account to use this plugin in test mode, and a live account to mint active DOIs.

Usage

Commands

doi

1. delete-dois: delete all DOIs from the database (not datacite). bash paster --plugin=ckanext-doi doi delete-dois -c $CONFIG_FILE

2. update-doi: update the datacite metadata for one or all packages. bash paster --plugin=ckanext-doi doi update-doi [PACKAGE_ID] -c $CONFIG_FILE

Interfaces

The IDoi interface allows plugins to extend the build_metadata_dict and build_xml_dict methods.

build_metadata_dict(pkg_dict, metadata_dict, errors)

Breaking changes from v1:

1. previously called build_metadata
2. new parameter: errors
3. new return value: tuple of metadata_dict, errors

Extracts metadata from a pkg_dict for use in generating datacite DOIs. The base method from this extension is run first, then the metadata dict is passed through all the implementations of this method. After running these, if any of the required values (see above) are still in the errors dict (i.e. they still could not be handled by any other extension), a DOIMetadataException will be thrown.

build_xml_dict(metadata_dict, xml_dict)

Breaking changes from v1:

1. previously called metadata_to_xml
2. parameters rearranged (previously xml_dict, metadata)

Converts the metadata_dict into an xml_dict that can be passed to the datacite library’s schema42.tostring() and schema42.validate() methods. The base method from this extension is run first, then the xml dict is passed through all the implementations of this method.

Templates

Package citation snippet

{% snippet "doi/snippets/package_citation.html", pkg_dict=g.pkg_dict %}

Resource citation snippet

{% snippet "doi/snippets/resource_citation.html", pkg_dict=g.pkg_dict, res=res %}

Testing

Test coverage is currently extremely limited.

To run the tests in this extension, there is a Docker compose configuration available in this repository to make it easy.

To run the tests against ckan 2.9.x on Python3:

1. Build the required images

# first build the containers
docker-compose build

1. Then run the tests. The root of the repository is mounted into the ckan container as a volume by the Docker compose configuration, so you should only need to rebuild the ckan image if you change the extension’s dependencies.

docker-compose run ckan

The ckan image uses the Dockerfile in the docker/ folder which is based on openknowledge/ckan-dev:2.9.

Note that currently the tests mock the Datacite API and therefore don’t require an internet connection nor your Datacite credentials to run.