NOTE: Check the specific requirements of the sponsor's data management and sharing policy
This page reviews data management template language for a variety of Ohio State resources. Each box below begins with "quick facts" about the OSU resource, followed by multiple tabs to explore template language on different themes.
Public Sharing
Computing
Active Storage
Instrumentation
Contact datamanagement@osu.edu and we'll help coordinate with the product owner.
See Ohio State Resources for Data Sharing for more information.
Appropriate for use in sections labeled: Data Format; Data Type; Data Collection; Data Volume
Suggested Language:
N/A - template language on this theme is not appropriate for this resource. Check other tabs!
Other Recommendations:
See DMPTool's guidance on Types of Data for more information.
Appropriate for use in sections labeled: Metadata; Documentation; Standards
Suggested Language:
Project-level metadata will be provided at the time of data deposit using Dryad’s web-based deposit form, which conforms to the DataCite metadata schema, a general standard for describing scientific data.
Other Recommendations:
See Documentation / Metadata for more information.
Appropriate for use in sections labeled: Security; Ethics; Privacy; Access Controls; Reuse Considerations; Intellectual Property; Licenses
Suggested Language:
Data shared through Dryad will be publicly available by unrestricted download under a CC0 (“No rights reserved”) license to reduce any legal or technical impediments to reuse.
IMPORTANT: These terms are required for use of Dryad. If you are working with data that requires access controls, you must select another repository.
Other Recommendations:
See Sharing Human Subjects Data for more information.
Appropriate for use in sections labeled: Preservation; Retention; Timelines; Archiving; Back-up; Recovery
Suggested Language:
Data deposited in Dryad are permanently archived and preserved through the services of California Digital Library's Merritt Repository. Data files in Merritt are replicated with multiple copies in multiple geographic locations. All files undergo regular fixity checks through the use of cryptographically-secure checksums and can be restored from a replicate copy if bit-level corruption is detected.
Other Recommendations:
See Back-up / Versioning for more information.
Appropriate for use in sections labeled: Access; Distribution; Dissemination; Data Sharing; Repository; Findable; Discoverable
Suggested Language:
Data will be publicly shared through the Dryad Data Repository. A DOI will be assigned to each data deposit to ensure it is identifiable and findable in accordance with FAIR principles. In addition to repository search features, datasets in Dryad are indexed by the Clarivate Data Citation Index and include schema.org mark-up to make them discoverable in Google Dataset Search. Dryad also integrates with any SWORD/OAI-PMH compliant repository, allowing its records to be discoverable through additional third-party aggregators.
Other Recommendations:
See How Do I Share? for more information.
See Ohio State Resources for Data Sharing for more information.
Appropriate for use in sections labeled: Data Format; Data Type; Data Collection; Data Volume
Suggested Language:
N/A - template language on this theme is not appropriate for this resource. Check other tabs!
Other Recommendations:
See DMPTool's guidance on Types of Data for more information.
Appropriate for use in sections labeled: Metadata; Documentation; Standards
Suggested Language:
Data published on QDR will be accompanied by extensive documentation, including standardized metadata that conforms to the schema of both the Data Documentation Initative (DDI) and DataCite. DDI is a disciplinary standard for describing social sciences survey data and DataCite is a general standard for describing scientific data at the project-level.
Other Recommendations:
See Documentation / Metadata for more information.
Appropriate for use in sections labeled: Security; Ethics; Privacy; Access Controls; Reuse Considerations; Intellectual Property; Licenses
Suggested Language:
Data will be made available under QDR’s Standard Download Agreement, which allows free re-use for research and pedagogy.
Note: This language refers to QDR's most permissive option for data access. Additional options are available and should be discussed in consultation with QDR repository staff.
Other Recommendations:
See Sharing Human Subjects Data for more information.
Appropriate for use in sections labeled: Preservation; Retention; Timelines; Archiving; Back-up; Recovery
Suggested Language:
QDR guarantees data availability for at least 25 years and aims to preserve access in perpetuity. QDR has been certified as a "trustworthy data repository" by CoreTrustSeal and its trained staff ensures that data are stored in formats appropriate for long-term archiving.
Other Recommendations:
See Back-up / Versioning for more information.
Appropriate for use in sections labeled: Access; Distribution; Dissemination; Data Sharing; Repository; Findable; Discoverable
Suggested Language:
Data will be publicly shared through the Qualitative Data Repository (QDR). QDR is a domain repository that stores, publishes, and preserves digital materials (data and documentation) generated through qualitative and multi-method research. In tandem with the researchers who deposit data with QDR, its trained staff fully curates data to make them Findable, Accessible, Interoperable, and Re-usable (FAIR). As part of its curation process, QDR ensures that data are stored in formats appropriate for long-term archiving, assists in the creation of detailed documentation, publishes data with metadata in Data Documentation Initiative (DDI) format, and attaches a Digital Object Identifier (DOI) to data to facilitate findability and allow stable citations to the data.
Other Recommendations:
See How Do I Share? for more information.
See OSC Services for more information.
Appropriate for use in sections labeled: Data Format; Data Type; Data Collection; Data Volume
Suggested Language:
Data will be transferred to the Ohio Supercomputer Center (OSC) for computation using [SELECT: Globus, SCP/SFTP, http/s via Open OnDemand] protocols. OSC is available to all Ohio researchers with home directory storage that can support up to 1.9 PB, project space up to 15 PB, and temporary scratch space up to 4 PB.
[IF APPLICABLE:] Git is installed on OSC and will be used for version control of scripts and applications.
Other Recommendations:
See DMPTool's guidance on Types of Data for more information.
Appropriate for use in sections labeled: Metadata; Documentation; Standards
Suggested Language:
N/A - template language on this theme is not appropriate for this resource. Check other tabs!
Other Recommendations:
See Documentation / Metadata for more information.
Appropriate for use in sections labeled: Security; Ethics; Privacy; Access Controls; Reuse Considerations; Intellectual Property; Licenses
Suggested Language:
Access to data stored in OSC will be limited to the project team and is password-protected. OSC home directory data is encrypted at the disk level and project data is encrypted at the file system level. The OSC cybersecurity program is based upon the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, Revision 4 requirements for security, and reflects the additional requirements of established Information Technology (IT) security practices.
[IF APPLICABLE:] OSC supports additional security requirements for storage of [SELECT: Personal Health Information, Resarch Health Information, Export Control data, Personally Identifiable Information, proprietary data] through its Protected Data Services program. Precise requirements will be arranged in consultation with OSC experts and will include multi-factor authentication.
[IF APPLICABLE:] Project file systems have file-level audit logging for both access and updates to data, ensuring provenance of all discoveries and protection against allegations of misconduct.
Other Recommendations:
See Sharing Human Subjects Data for more information.
Appropriate for use in sections labeled: Preservation; Retention; Timelines; Archiving; Back-up; Recovery
Suggested Language:
All OSC file systems are backed up daily with snapshots that are retained for a minumum of 7 days for project directories and 3 days for home directories. Deleted files and up to 14 versions of files modified on disk are retained in back-up for at least 90 days. Backup data is replicated daily to an offsite data center in Cleveland, Ohio. Data stored on the OSC project file systems are also protected by end-to-end checksums to identify and correct errors introduced by the network or storage media.
[IF APPLICABLE:] All data not publicly shared will be preserved at OSC for as long as OSC accounts and project budgets are maintained. OSC will maintain three copies of data, including an offsite copy, with end-to-end checksums to ensure the consistency of the backups. OSC also periodically refreshes storage hardware and software and performs data migration.
Other Recommendations:
See Back-up / Versioning for more information.
Appropriate for use in sections labeled: Access; Distribution; Dissemination; Data Sharing; Repository; Findable; Discoverable
Suggested Language:
N/A - template language on this theme is not appropriate for this resource. Check other tabs!
Other Recommendations:
See How Do I Share? for more information.
See Unity Documentation for more information.
Appropriate for use in sections labeled: Data Format; Data Type; Data Collection; Data Volume
Suggested Language:
Unity is available to all researchers in the Ohio State College of Arts and Sciences with a default home directory up to 100GB.
[IF APPLICABLE:] An additional [##] TB of project space will be leased as described in the application budget.
[IF APPLICABLE:] Git is installed on Unity and will be used for version control of scripts and applications.
Other Recommendations:
See DMPTool's guidance on Types of Data for more information.
Appropriate for use in sections labeled: Metadata; Documentation; Standards
Suggested Language:
N/A - template language on this theme is not appropriate for this resource. Check other tabs!
Other Recommendations:
See Documentation / Metadata for more information.
Appropriate for use in sections labeled: Security; Ethics; Privacy; Access Controls; Reuse Considerations; Intellectual Property; Licenses
Suggested Language:
Access to data on local network storage will be limited to the project team and is password-protected. Additionally, two-factor authentication is required for SSH and web access from off-campus locations. The ASCTech cybersecurity program is based upon the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, Revision 4 requirements for security, and reflects the additional requirements of established Information Technology (IT) security practices.
Other Recommendations:
See Sharing Human Subjects Data for more information.
Appropriate for use in sections labeled: Preservation; Retention; Timelines; Archiving; Back-up; Recovery
Suggested Language:
Unity project space storage is served by the college project fileserver and backed-up daily with snapshots that are retained for a minimum of 7 days. A remote disaster recovery site keeps 30 days of snapshots. The standard storage purchase period is for 5 years and will be renewed as needed during the project. Data needed for longer-term preservation will be separately archived through [ARCHIVAL STORAGE SOLUTION].
Other Recommendations:
See Back-up / Versioning for more information.
Appropriate for use in sections labeled: Access; Distribution; Dissemination; Data Sharing; Repository; Findable; Discoverable
Suggested Language:
N/A - template language on this theme is not appropriate for this resource. Check other tabs!
Other Recommendations:
See How Do I Share? for more information.
See ASCTech Research Storage for more information.
Appropriate for use in sections labeled: Data Format; Data Type; Data Collection; Data Volume
Suggested Language:
Data will be stored through on-premises network storage. The ASC Research Storage Service is available to all researchers in the Ohio State College of Arts and Sciences with a default allocation of 2 TB.
[IF APPLICABLE:] An additional [##] TB of storage space will be leased as described in the application budget.
Other Recommendations:
See DMPTool's guidance on Types of Data for more information.
Appropriate for use in sections labeled: Metadata; Documentation; Standards
Suggested Language:
N/A - template language on this theme is not appropriate for this resource. Check other tabs!
Other Recommendations:
See Documentation / Metadata for more information.
Appropriate for use in sections labeled: Security; Ethics; Privacy; Access Controls; Reuse Considerations; Intellectual Property; Licenses
Suggested Language:
Access to data on local network storage will be limited to the project team and is password-protected. Additionally, two-factor authentication is required for SSH and web access from off-campus locations. The ASCTech cybersecurity program is based upon the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, Revision 4 requirements for security, and reflects the additional requirements of established Information Technology (IT) security practices.
Other Recommendations:
See Sharing Human Subjects Data for more information.
Appropriate for use in sections labeled: Preservation; Retention; Timelines; Archiving; Back-up; Recovery
Suggested Language:
The local network storage is backed-up daily with snapshots that are retained for a minumum of 7 days. A remote disaster recovery site keeps 30 days of snapshots. The standard storage purchase period is for 5 years and will be renewed as needed during the project. Data needed for longer-term preservation will be separately archived through [ARCHIVAL STORAGE SOLUTION].
Other Recommendations:
See Back-up / Versioning for more information.
Appropriate for use in sections labeled: Access; Distribution; Dissemination; Data Sharing; Repository; Findable; Discoverable
Suggested Language:
N/A - template language on this theme is not appropriate for this resource. Check other tabs!
Other Recommendations:
See How Do I Share? for more information.