DSpace Configuration

Overview
Dryad uses the core features of DSpace, but many of these features have been modified, configured in a specific way, or completely replaced. For many changes, there is a corresponding document in Category:Technical_Documentation. This page collects information about changes that are not related to a major feature.

Collections and Communities
DSpace relies heavily on the concepts of collections and communities, but they are largely implicit in Dryad. We have tried to hide most traces of collections and communities from the Dryad user interface, while using them to manage content behind the scenes.

Dryad contains a single community: the Main community. From here, all collections may be accessed. There should not be a need to modify the DSpace object that represents the Main community.

To modify a collection:
 * 1) Log in as an administrator
 * 2) Navigate to the Main community
 * 3) Select the desired collection
 * 4) From the left-hand menu, select the option to edit the collection.

Minimal configuration for collections and communities
The Dryad codebase assumes that these DSpace objects will be present:
 * Community "Main", 10255/1
 * Collection "Data Files", 10255/2
 * Collection "Data Packages", 10255/3
 * Collection "KNB", 10255/dryad.2027
 * Collection "TreeBASE", 10255/dryad.2171

These collections may be empty. The Data Files and Data Packages collections receive new content via the Dryad Submission System. The KNB and TreeBASE collections are typically set to harvest content from the appropriate repositories.

Other collections and communities may be present, but will not be appear prominently in the Dryad interface.

Metadata Registry
The default set of metadata fields that are installed with DSpace do not cover all of Dryad's needs. To install Dryad's extra metadata fields, run dsrun org.dspace.administer.MetadataImporter -f config/registries/FILENAME (replace FILENAME with one of the files in the registries directory)

Database tables
Dryad relies on some custom database tables for Versioning.

The easiest way to ensure that Dryad has the proper content in the database is to copy the database from an existing Dryad instance. However, this may not be practical.

The standard DSpace installation process creates most of the needed database tables. Dryad's custom tables are stored in SQL scripts in the dspace/etc directory. Run these scripts with: psql -U dryad_app <name-of-the-script