Skip to content
This repository has been archived by the owner on Nov 20, 2019. It is now read-only.

CDL-Dryad/stash

 
 

Repository files navigation

🚫 stash repository deprecated

🚫 Please see dryad-app repository instead of this one

The dryad-app repository combines the former dryad and stash repositories into one repository.

All new commits, pull requests and activity should happen against the dryad-app repository instead of this repository since it consolidates what was really one application into one place and simplifies management and maintenance.

previous information below

Build Status

Introduction

Stash is an application framework for research data publication and preservation. Stash enables individual scholars to:

  1. Prepare datasets for curation by reviewing best practice guidance for the creation or acquisition of research data.
  2. Select data for curation through local file browse or drag-and-drop operation.
  3. Describe data in terms of scientifically-meaning metadata.
  4. Identify datasets for persistent citation, reference, and retrieval.
  5. Preserve, manage, and share data in an appropriate data repository.
  6. Discover, retrieve, and reuse data through faceted search and browse.

By alleviating many of the barriers that have historically precluded wider adoption of open data principles, Stash empowers individual scholars to assert active curation control over their research outputs; encourages more widespread data preservation, publication, sharing, and reuse; and promotes open scholarly inquiry and advancement.

Dash is the UC Curation Center's implementation of Stash. For the Dash source code, see the dashv2 repository.

The next generation of Dryad is being rebuilt with the Stash core. For the Dryad source code, see the dryad repository.

Architecture

Stash is intended to be applicable to any standards-compliant repository that supports the SWORD 2 protocol for deposit and OAI-PMH or ResourceSync protocols for metadata harvesting.

Stash architecture

Contributing

For individual projects, bundle exec rake will run unit tests, check test coverage, and check code style. Use bundle exec rubocop -a to identify code style problems and auto-fix any that can be auto-fixed. In general, all projects follow the top-level rubocop.yml code style configuration, with judicious exceptions.

Run travis-build.rb in the top-level stash directory to bundle, test, and style-check all projects.

About

A UC3 application framework for storing and sharing research data

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • CSS 55.7%
  • Ruby 27.8%
  • HTML 13.3%
  • JavaScript 3.2%