Scientific Reports · Article · 7 min read
Scientific Reports data and code availability: a manuscript checklist
Check that a Scientific Reports manuscript identifies its supporting data, repository records, access restrictions, dataset citations, and central custom code.
A Scientific Reports submission needs more than a generic sentence saying that data are “available.” The journal asks authors to place a Data Availability section in the manuscript, identify where the data supporting the results can be found, and describe any access conditions. When custom code or an algorithm is central to the conclusions, the Methods section also needs a Code availability statement. Preparing both statements from an inventory of the study’s actual materials makes it easier to keep the manuscript, repositories, references, and upload files consistent.
Separate data availability from code availability
Scientific Reports’ submission guidelines require a Data Availability Statement in submitted manuscripts. The statement belongs at the end of the main text, before the References section. The journal’s editorial policies add that the section should be titled “Data Availability” and should identify publicly archived datasets with accession codes, persistent links, or other unique identifiers where applicable. If data cannot be public, the statement should describe the access conditions rather than omit the data entirely. Scientific Reports submission guidelines Scientific Reports editorial policies
Code is handled separately. For studies in which custom code or a mathematical algorithm is central to the conclusions, the Methods section should contain a statement headed “Code availability.” That statement explains how readers can access the code or algorithm and identifies any restrictions. The journal may publish the relevant code as Supplementary Information or ask authors to maintain it in an established version-control repository.
Do not merge the two statements into a single vague paragraph. Data and code can have different owners, repositories, licenses, access rules, and versions. Keeping them separate helps editors and readers understand exactly what is available.
Build an inventory before drafting
Start with the materials that are necessary to interpret, replicate, or build on the reported findings. The journal describes this as the minimal supporting dataset, but the right inventory depends on the study. List each item and record:
- whether it was generated by the study or obtained from another source;
- the repository, accession number, DOI, or persistent URL;
- whether access is public, controlled, available by request, or restricted by a third party;
- the version or release that matches the analysis;
- whether the item is cited in the reference list;
- whether editors and reviewers can access it during peer review;
- the person or organization responsible for approving access.
Run the same inventory for custom code, scripts, software, and algorithms. Distinguish code written for the study from standard commercial or open-source software that can be identified by name and version. If code is in a repository, record the exact release, archive, commit, or DOI that corresponds to the manuscript rather than linking only to a changing project homepage.
This inventory is an author-team working document. The published statement should be concise, but it cannot be accurate unless the team first resolves missing identifiers, incomplete deposits, and unclear access ownership.
Write a public-repository statement that can be followed
For public data, name the repository and give a persistent identifier or direct dataset record. Confirm that the record points to the version used in the manuscript, not merely to a collection landing page. If the repository keeps files private during peer review, arrange anonymous reviewer access and make sure the public release is coordinated with publication.
Scientific Reports asks authors to cite datasets stored in external repositories. Previously published datasets should be cited as datasets as well as through any associated research article. Check that the creator names, year, dataset title, repository, version, and persistent identifier agree between the repository record, the manuscript statement, and the reference list. Scientific Reports editorial policies
Avoid phrases such as “data available online” or “all relevant data are included” unless the reader can tell what is included and where. If all supporting data are in the article and its Supplementary Information, say so explicitly. If figure source data are provided, identify that in the Data Availability statement.
The journal discourages “data not shown” claims. Results that support the paper should instead be included in the article, deposited, or supplied through an appropriate supporting file or access route.
Describe controlled-access and third-party data precisely
Public release is not always possible. Participant privacy, ethical approvals, legal duties, or data-use agreements may require controlled access. A useful statement explains why access is controlled, who may request the data, how to make the request, the criteria used to assess it, the expected response time, and any limits on reuse. Do not promise access that the author team lacks authority to grant.
For third-party data, name the provider when permitted and explain the restriction. If the authors obtained the data under license, confirm before submission that peer-review access and the post-publication access described in the statement are compatible with that license. The journal expects primary and referenced datasets to be accounted for, even when the authors cannot redistribute them directly.
Clinical-trial data statements require additional detail. The journal’s policy asks authors to state whether de-identified participant data will be shared, which data and related documents will be available, when and for how long they will be available, and the criteria and mechanism for access. “Undecided” is not an acceptable sharing position under the cited policy. Keep any public statement free of participant identifiers or confidential information.
Make the code statement reproducible
When custom code or an algorithm is central to the conclusions, the Code availability statement should identify the specific version used for the reported results. A strong statement names the repository or Supplementary Information file, gives a persistent link or archive identifier, and notes any necessary access restrictions.
Before citing the code location, test it from a signed-out browser and confirm that the archived version contains what the manuscript says it contains. Include the scripts needed to reproduce key processing and analysis steps, along with environment or dependency information where it is necessary to run them. Do not expose passwords, private keys, credentials, participant information, proprietary input data, or internal server paths.
If some code cannot be shared, state the reason and describe what can be provided. Do not use a public repository link to imply that restricted dependencies or proprietary components are available when they are not. The statement should let an editor understand the boundary without reading private correspondence.
Reconcile statements, files, and references
Availability language often becomes stale while a manuscript is revised. A repository may receive a DOI after the first draft, a dataset version may change, or the authors may move code from a personal repository to an archived release. Run a final reconciliation across:
- the Data Availability section;
- the Code availability statement in Methods, when required;
- repository records and reviewer-access links;
- dataset and software citations in the reference list;
- Supplementary Information filenames and descriptions;
- figure source-data notes;
- ethics, consent, and data-governance language;
- the submission portal’s data and code questions.
Every identifier should resolve to the intended record. Every restriction should match the actual agreement or approval. The manuscript should not promise a response route that no one monitors, and the portal should not claim public availability when the manuscript describes controlled access.
Complete the pre-upload check
Before submission, confirm that the Data Availability section is present in the correct location and uses the required heading. Confirm that custom code central to the conclusions has a separate Code availability statement in Methods. Give editors and reviewers the access they need during evaluation, and remove expiring internal links from the manuscript.
Open each public link, DOI, and accession record. Check that anonymous reviewer links do not expose author identities when blinded review applies. Verify that the cited versions match the analysis and that restricted routes describe realistic conditions.
Scientific Reports’ current official instructions and the live submission system control if they differ from this checklist. A careful availability package does not guarantee editorial acceptance, but it gives editors and readers a consistent account of the data, code, repositories, and restrictions behind the manuscript.
Sources used for this guide
Journal instructions can change. The journal's official guidance controls, and Articlo rechecks stored profiles on a schedule.
See how close your manuscript is to submission.
Choose the journal and upload your draft for a free readiness check. You will see what is ready and what still needs attention before you decide whether to purchase formatting.