Page tree
Skip to end of metadata
Go to start of metadata

The DSpace-CKAN Integration Module allows users to directly preview the dataset content deposited in a CKAN instance from DSpace via a “curation task”. The new DSpace-CKAN Integration Module offers the users the possibility to access the services provided by the CKAN data management system without leaving their DSpace installation, making their life easier and their activities more efficient. The module allows to connect the publications with the datasets and better describe the context of realization of the dataset by creating detailed records on the equipment used, the related services, the projects concerned, etc.

The DSpace-CKAN Integration Module is distributed by 4Science as an additional open source addon for the DSpace-CRIS platform but can easily adopted by basic DSpace installations (both JSPUI than XMLUI, if you do that please let us know we will be happy to support). 

One of the main advantages of the Module is that it allows the management of dataset access via DSpace, without the need of getting into a CKAN instance. The CKAN datastore API is proxied by the DSpace-CRIS module, enhancing the access conditions set on the original DSpace bitstream (e.g.: the preview function is available under the same conditions of the uploaded bitstream: open access, embargo, etc.).

A summary of the features, screenshots and demo content is available here

How to install

The addon is installed by default with DSpace-CRIS but you need to set the following properties in your file (dspace-cris 5.x) or local.cfg (dspace-cris 6.x)

ckan.datastore.url =
ckan.datastore.apikey = 
ckan.datastore.orgname =

to be able to use it.

Be sure to keep enabled the ckan profile during the mvn package phase (-P<other-profiles,addon-ckan) of the dspace-cris installation. The profile is enabled by default but if you specify a profile such as the one need for oracle support or other addons you need to include also the addon-ckan profile in your list. The addon requires the execution of a curation task that again is configured by default, see curate.cfg

Once your distribution has been packaged and installed (ant update) you will need to load in the metadata and bitstream registries additional entries

./dspace dsrun org.dspace.administer.RegistryLoader -metadata ../config/registries/bitstream-types.xml
./dspace dsrun org.dspace.administer.RegistryLoader -metadata ../config/registries/ckan-types.xml
./dspace dsrun org.dspace.administer.RegistryLoader -bitstream ../config/registries/ckan-bitstream-formats.xml
  • No labels