Difference between revisions of "Architecture Overview"

From Dryad wiki
Jump to: navigation, search
(Dryad's data structure)
(Dryad's data structure)
Line 7: Line 7:
 
[[Image:DryadRepositoryArchitecture2015.png|600px]]
 
[[Image:DryadRepositoryArchitecture2015.png|600px]]
  
== Dryad's data structure ==
+
== Dryad's data model ==
  
 
[[Image:DryadDataModel2015.png|600px]]
 
[[Image:DryadDataModel2015.png|600px]]

Revision as of 08:46, 20 July 2016

Dryad servers/services

DryadServers2015.png

A repository

DryadRepositoryArchitecture2015.png

Dryad's data model

DryadDataModel2015.png

A deposit in Dryad consists of three primary parts:

  • 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. Each file is a DSpace item that contains file-specific metadata as well as the bitstreams.
  • Bitstreams: The bitstreams are downloadable files that contain data OR documentation. In DSpace, these bitstreams are always part of a Dryad Data File item. 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 format and usage of 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.

DSpace-1.8-Database-Schema.png

Workspace/Workflow

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