Data Availability Expectations

JTR encourages authors to deposit datasets in trusted repositories whenever possible. Data availability statements are required for all submissions and should describe where data can be accessed.

If data cannot be shared due to privacy, legal, or biosafety restrictions, authors must explain the limitations and provide access pathways for qualified researchers.

Statements should specify repository names, persistent identifiers, and access conditions. If data are restricted, describe the reason and provide contact details for access requests.

Data Citation

Cite datasets in the reference list using repository DOIs or accession numbers. Data citations improve transparency and support credit for data creators.

Embargo and Access Controls

If immediate release is not possible, request a limited embargo and specify duration in the data statement. Controlled access data should include a clear request pathway.

Genomic and Sequence Data

For sequence data, deposit reads and assemblies in recognized repositories and provide accession numbers. Include metadata on organism, strain, and construct identifiers to support reuse.

Metadata and Documentation

Provide readme files, data dictionaries, and protocol details. Clear documentation helps reviewers validate methods and allows other researchers to interpret and reuse datasets responsibly.

Code and Workflow Sharing

Share analysis scripts and pipelines when possible. Archive a stable release and cite the DOI to ensure your computational workflow remains accessible over time.

Sensitive or Restricted Data

If data involve privacy, biosecurity, or regulatory restrictions, explain the limitations in your statement. Provide a process for qualified access or a summary dataset when full release is not possible.

Data Licensing

Select a data license that supports reuse while protecting attribution. Consistent licensing reduces ambiguity and encourages responsible downstream use of transgenic datasets.

Data Management Plans

State how data will be stored, preserved, and updated. A clear management plan supports compliance with funder policies and improves long term availability.

Versioning and Updates

If datasets are updated after publication, describe versioning practices and provide updated accession details. Clear version control helps readers interpret results and ensures reproducibility over time.

Quality Checks

Describe any validation, quality control, or normalization steps applied to datasets. Transparent quality checks help reviewers evaluate reliability and allow other researchers to reuse data confidently.

Linking Data to the Article

Include dataset links within the manuscript and ensure references are cited properly. Consistent linking between the article and repositories improves discovery and citation tracking for both data and publication.

Choosing the Right Repository

Select repositories that align with your data type and community standards. Domain specific repositories often improve visibility and reuse by researchers who routinely search those resources.

Privacy and Consent

When data include human participant information, confirm consent for sharing and remove identifiers. If full sharing is not possible, provide a controlled access route that protects participants while supporting research integrity.

Statement Examples

Example: Data are available in Zenodo under DOI X. Example: Sequence data are deposited in GenBank under accession numbers Y. Example: Restricted data are available from the corresponding author upon reasonable request and approval. Include persistent identifiers and version numbers, and note any embargo end dates when applicable. If no data were generated, state that explicitly and explain why. For proprietary datasets, describe ownership and provide a contact for access requests. Use consistent wording across the abstract and methods sections to avoid confusion for readers globally.