Skip to Main Content

Research Data Management

This toolkit offers guidance for researchers, librarians, and administrators on managing research data

Dryad at SUNY FAQs

  1. What is Dryad?

Dryad is an open data publishing platform and a community committed to the open availability and routine re-use of all research data.  SUNY has joined Dryad as the second institutional consortia member (after founding consortia member California Digital Library) and will support data publishing for researchers at many SUNY campuses.

  1. Why Dryad?

For most researchers required to publish research data in an open access or FAIR repository, a domain-specific or other repository specified by the funder is provided. For other researchers in need of a generalist repository or who have not requirements for publishing data but a desire to share their data, Dryad is available. Dryad is for data that needs to be retained permanently.

  1. Who can use Dryad?

For campuses that have not joined the Dryad community as Institutional Members, but have data publishing and sharing needs, we have created a SUNY consortia instance of Dryad.

Researchers on the following campuses can publish their data under the SUNY consortia membership. The $140 dataset publishing cost will be covered under the current contract for 2023 and 2024. Once data is deposited in Dryad, campuses do not need a contract for Dryad to maintain and preserve the data.

  • Buffalo State College
  • College of Nanoscale Science and Engineering
  • College of Optometry
  • Maritime College
  • New York State College of Ceramics at Alfred University
  • Purchase College
  • SUNY Brockport
  • SUNY College of Environmental Science and Forestry (ESF)
  • SUNY Cortland
  • SUNY Downstate Health Sciences University
  • SUNY Fredonia
  • SUNY Geneseo
  • SUNY New Paltz
  • SUNY Old Westbury
  • SUNY Oneonta
  • SUNY Oswego
  • SUNY Plattsburgh
  • SUNY Polytechnic Institute
  • SUNY Potsdam
  • Upstate Medical University

  1. What is the advantage of using Dryad as opposed to an institutional repository?

The amount of data some researchers are creating would be costly to store in an IR. SUNY has opted to join Dryad rather that host data for campuses in the SUNY Digital Repository. Dryad is also specifically for published and accessible data. Our IR and some campus IRs would need to rethink their IR collection development and infrastructure to enable data ingest. Additionally, Dryad provides curation services that are absent in a campus-hosted IR.

  1. How do researchers publish their data?

The submission process is outlined here: Researchers must have an ORCID iD (information on ORCID) to submit data to Dryad. Each campus will build a link for their researchers to access the SUNY consortia instance. OLIS will provide information on the technical configuration for that link.

  1. What data licenses does Dryad accept?

Data published to Dryad must be under a CC0 license. Read about the license here: Software can be loaded to Zenodo within Dryad. Zenodo accepts a variety of software licenses.

  1. Are SDR and SOAR still available?

Yes, SDR and SOAR are still available. The purpose of each repository is listed below:

The SUNY Digital Repository (SDR) is a centrally managed online digital repository that stores, indexes, and makes available the following types of materials:

  • Historical and Special Collections from SUNY campuses and SUNY System Administration
  • Open Educational Resources (OER) Collections
    • SUNY OER Repository
    • OER collections at the campus level – items records for OER content in campus collections can be linked to also display in the SUNY OER Repository collection
  • Reports from the Innovative Instructional Technology Grants (IITG)

The SUNY Open Access Repository (SOAR) is a centrally managed online digital repository that stores, indexes, and makes available scholarly and creative works of SUNY faculty, students, and staff across SUNY campuses. SOAR serves as an open access platform for those SUNY campuses that do not have their own open access repository environments.