Data, Code, Materials & Reproducibility (TOP-Aligned)

7.1 Purpose

  • Transparent sharing of data, code, and research materials enables verification, reuse, and cumulative science. This policy sets publisher-wide requirements for availability, documentation, citation, and long-term preservation, with proportional safeguards for privacy, security, and intellectual property.

7.2 Core Requirements (Applies to All Empirical Articles)

  • Data Availability Statement (DAS): Every article must include a clear statement describing what data exist, where they are stored, how they can be accessed, and any justified restrictions.
  • Code Availability Statement: For any analysis, simulation, model, or figure created with software, provide access to executable code or workflows, or give a justified restriction.
  • Materials/Protocol Availability: Reagents, instruments, questionnaires, custom hardware designs, and detailed protocols must be available or sufficiently documented for replication.
  • Persistent Identifiers: Provide DOIs or other persistent identifiers for datasets, software, materials, and protocols whenever possible.
  • Citation of Data & Software: Cite datasets and software in the reference list as first-class research objects, including creators, title, year, version, repository, and identifier.

7.3 Preferred Repositories and Persistence

  • Deposit in trusted, non-proprietary repositories that issue persistent identifiers and support long-term preservation (e.g., discipline repositories, general repositories, institutional repositories).
  • Repositories must allow public landing pages with metadata even when files are controlled-access.
  • Avoid links that can rot (temporary file shares). Mirror critical artifacts when allowed.
  • Large or complex data should include a readme and machine-readable metadata.

7.4 FAIR Principles

  • Submissions must follow FAIR (Findable, Accessible, Interoperable, Reusable):
  • Findable: Rich metadata; persistent identifiers; referenced in the article.
  • Accessible: Clear access terms, including controlled-access instructions where needed.
  • Interoperable: Use open, community formats and vocabularies when available.
  • Reusable: Include licenses and documentation that enable reuse with proper attribution.

7.5 Licensing

  • Prefer open licenses that permit reuse with attribution (for example, CC BY for data/metadata where appropriate).
  • If legal or ethical constraints prevent open licensing, state the exact restriction and provide the process for qualified access (e.g., data use agreements).
  • Software should use a recognized open-source license when possible; otherwise specify precise usage rights.

7.6 Documentation & Provenance

  • Provide a data dictionary, variable definitions, units, and coding schemes.
  • Describe provenance from raw data to final analysis, including filtering, exclusion rules, and transformations.
  • Include a workflow diagram or step list sufficient for an independent researcher to repeat the pipeline.

7.7 Computational Reproducibility

  • Name software, packages, and versions; state operating system and key dependencies.
  • Share environment files (for example, lockfiles or container manifests).
  • For randomized procedures, report seeds and initialization details.
  • Provide minimal runnable examples demonstrating that the main analyses reproduce key tables and figures.

7.8 Research Resource Identifiers (RRIDs)

  • Identify critical reagents and resources with RRIDs when available (cell lines, antibodies, organisms, software).
  • For custom materials, provide stable catalog information, fabrication files, or bill-of-materials so others can obtain or build equivalents.

7.9 Sensitive, Personal, or Restricted Data

  • When data cannot be openly shared due to privacy, safety, legal, or contractual limits, provide:
    • a) A public metadata record;
    • b) A lawful, proportionate access route (e.g., controlled-access repository or data enclave);
    • c) A clear justification for restrictions;
    • d) Any required approvals or data use agreements.
  • De-identify to accepted standards; avoid re-identification risks. Summaries or synthetic datasets may be provided to enhance transparency without exposing individuals.

7.10 Security-Sensitive and Dual-Use Content

  • For materials or code that could enable harm, provide mitigated sharing (for example, redacted methods, staged release after institutional review, or access for qualified researchers under oversight).
  • Editors may require additional safeguards or modify dissemination to reduce misuse risk while preserving the scholarly record.

7.11 Embargoes

  • Short, time-limited embargoes may be allowed to align with registration or commercialization timelines. Embargo length and rationale must be stated in the DAS and lifted automatically when the period ends.

7.12 Registered Reports and Confirmatory Analyses

  • For registered reports or preregistered studies, share time-stamped protocols and analysis plans. Deviations must be labeled and justified in the manuscript and documentation.

7.13 Quality Checks and Integrity

  • Provide original, unprocessed data files and image sources on request for verification.
  • We screen for internal consistency (for example, file hashes, row/column counts, figure-data alignment) and may request clarifications or corrections before acceptance.

7.14 Third-Party and Licensed Data

  • When using third-party data, confirm that sharing is permitted. If redistribution is prohibited, the DAS must explain how others can obtain the data independently under equivalent terms.
  • State any usage restrictions, embargoes, or attribution requirements.

7.15 Code Review and Executability

  • Code must run from clean checkout with instructions. Provide a README with setup steps, expected runtime, and how to reproduce key results.
  • Where feasible, include automated tests or checks that validate major outputs.

7.16 Large-Scale, Streaming, or Dynamic Data

  • For evolving datasets, provide a versioned snapshot used for the article with a unique identifier and date.
  • Describe how to retrieve the same snapshot in the future and how updates differ.

7.17 Negative and Null Results, Replications, and Reanalyses

  • We welcome well-powered replications, reanalyses, and negative or null results. Data and code should enable others to verify conclusions even when results are not positive.

7.18 Attribution and Credit

  • Cite data creators and software authors. Include contributor roles (for example, data curation, software) in the CRediT statement.
  • Where repositories support credit systems (such as citation tracking), ensure metadata is complete to recognize contributors.

7.19 Publisher Audits and Requests

  • Editors may request data, code, materials, or logs during review or post-publication for verification.
  • Failure to provide promised materials without compelling justification may lead to correction, expression of concern, or retraction to protect the record.

7.20 Exceptions and Justifications

  • Exceptions are limited to cases where sharing would violate law, ethics, safety, or binding contracts. Authors must provide a clear, written justification and a route for bona fide researchers to request access where feasible.

7.21 Minimal Templates (for Articles)

  • Data Availability Statement (model):
    • “The dataset generated and analyzed in this study is available in a trusted repository with persistent identifier. Access is open under an attribution license. Any personal data were removed or anonymized before sharing.”
  • Code Availability Statement (model):
    • “All analysis code and environment files required to reproduce the results are available in a trusted repository with a persistent identifier. Instructions to regenerate tables and figures are included.”
  • Materials/Protocol Availability (model):
    • “Key materials and protocols are described in detail and available through standard suppliers or repositories. Custom hardware designs and questionnaires are provided with documentation.”

7.22 Versioning and Change Logs

  • Data, code, and materials should carry version numbers and change logs. The article should reference the exact versions used for the published results.

7.23 Long-Term Preservation

  • Choose repositories and file formats that support long-term access. Critical artifacts should be preserved beyond the publication date, with redundancy to guard against loss.

7.24 Enforcement and Sanctions

  • Misrepresentation of availability, sharing of manipulated files, or failure to honor stated access routes may result in rejection, correction, expression of concern, retraction, and notification of institutions or funders when appropriate.