For SysAdmins

This is the section for technical administration of the ReSeeD system.

Architecture

The research data management system (RDM system) is jointly developed with researchers to support their research workflow. The implementation of complex data models allows low barrier adoption for the researches in the lab where data is being generated, early data sharing and reuse with collaborating research groups, data curation, archival (ARK) and publication (DOI) workflows. The system interfaces with native S3 compliant storage to store data and metadata.

The system is a self-service tool for researchers to store, describe, share, archive (bit-stream) and publish their data. It supports FAIR data principles and promotes the implementation of RDM and open science policy requirements. The system also supports IT, library and RDM services provisioning RDM resources, curation and publication of data, and consultancy with the system providing large of RDM demands by design.

Main Features are (any customized features or additions to base gems):

  • Work types: Dataset (Datacite), CRC1280 Dataset (discipline specific supporting neuroscience, custom very complex and hierarchical)
  • three-step review workflow mapping research group, research cluster, and repository data curation/publication levels.
  • Shibboleth (saml2) and ORCID authentication,
  • Native S3 storage
  • Bulkrax (import complex folder structure with hierarchical metadata)
  • matomo anlytics

Samvera solutions/gems:

  • Hyrax 3.5
  • bulkrax

Storage Layer:

  • S3 (carrierwave) data and metadata,
  • Postgres (Application data)
  • Fedora 4.7.5 (Graph metadata store only, link to data in S3)

Data storage

The S3 bucket file structure is documented here

Docker

ReSeeD is deployed as a set of Docker containers and volumes. The Docker images, containers and volumes are documented.

Deployment

The process to deploy ReSeeD system is described in detail in the main README file which is kept with the code-base.

This note about rebooting explains the configuration used to initiate container reboots when the host system is rebooted from under the containers (could not find this page about rebooting?)

Backup / restore

All volatile data in ReSeeD system is persisted in Docker volumes. Some notes about best practice for backing up and restoring Docker volumes.

Other useful documentation