Old:Architecture Overview

From Dryad wiki
Revision as of 09:59, 20 July 2016 by Ryan Scherle (talk | contribs) (Dryad's data model)

Jump to: navigation, search

Dryad servers/services


A repository


Dryad's data model


A deposit in Dryad consists of:

  • Metadata: Objects in Dryad are described with an extended version of Dublin Core metadata, which is described on the Metadata Profile page.
  • Data Package: A Dryad Data Package represents all of the data associated with a single scientific publication. This is a DSpace item that contains only metadata. The metadata contains a mix of fields that describe the data and fields that describe the associated publication. The landing page for a Dryad Data Package displays a small summary of each associated Dryad Data File. (sample landing page, sample metadata)
  • Data Files: A Dryad Data File represents a single file of downloadable data. Often, this is a standalone file such as a spreadsheet, but it may be a compressed archive containing many other files. Each file is a DSpace item that contains file-specific metadata as well as the bitstreams. (sample landing page, sample metadata)
  • Bitstreams: The bitstreams are downloadable files that contain data OR documentation. In DSpace, these bitstreams are always part of a Dryad Data File item, but some access mechanisms (such as the DataONE API) treat the bitstreams as separate objects. A single DSpace item may contain multiple bitstreams, which contain the same scientific data in different file formats. Each Dryad Data File may also contain a special bitstream with the name README, which contains documentation describing the other bitstreams in the same Dryad Data File.

For examples of atypical/extreme objects in Dryad, see Sample Dryad Content.

DSpace Database Schema

This diagram reflects the "stock" version of DSpace. It does not include Dryad customizations.



User-visible components

  • homepage
  • static pages
  • search
  • item view
  • submission
  • submission journal integration
  • payment
  • curation
  • statistics

Internal support components

  • DataONE API
  • Solr API
  • DSpace API
  • identifiers
  • versioning
  • embargo
  • reporting
  • curation tools
  • assetstore storage
  • database
  • authN (epeople)
  • authZ (access control)
  • journal settings configuration and management