JPBB is committed to a more open research landscape, facilitating faster and more effective research discovery by enabling reproducibility and verification of data, methodology and reporting standards. We encourage authors of articles published in our journal to share their research data including, but not limited to: raw data, processed data, software, algorithms, protocols, methods, materials.
Refer to the table below to understand the various standardized data sharing policy categories:
|
Data availability statement is published1 |
Data has been shared2 |
Data has been peer reviewed3 |
|
|
Encourages Data Sharing |
Optional |
Optional |
Optional |
|
Expects Data Sharing |
Required |
Optional |
Optional |
|
Mandates Data Sharing |
Required |
Required |
Optional |
|
Mandates Data Sharing and Peer Reviews Data |
Required |
Required |
Required |
1 A data availability statement confirms the presence or absence of shared data.
2 Links to data in data availability statements are checked to ensure they link to the data that the authors intended. If data have been shared in a data repository, the data availability statement includes a permanent link to the data. Shared data is also cited.
3 Quality and/or replicability of linked data are peer reviewed. Depending on the journal, this may be to peer review the quality of the data by ensuring that the results in the paper and the data in the repository align (for example, sample sizes and variables match), or it may be to peer review the replicability of the data to ensure that the claims presented in the journal article are valid and can be reproduced.
Encourages Data Sharing
JPBB encourages authors to share the data and other artefacts supporting the results in the paper by archiving it in an appropriate public repository. Authors may provide a data availability statement, including a link to the repository they have used, in order that this statement can be published in their paper. Shared data should be cited.” All accepted manuscripts may elect to publish a data availability statement to confirm the presence or absence of shared data. If you have shared data, this statement will describe how the data can be accessed, and include a persistent identifier (e.g., a DOI for the data, or an accession number) from the repository where you shared the data. You may use the Standard Templates for Author Use or draft your own.
Expects Data Sharing
JPBB expects that data supporting the results in the paper will be archived in an appropriate public repository. Authors are required to provide a data availability statement to describe the availability or the absence of shared data. When data have been shared, authors are required to include in their data availability statement a link to the repository they have used, and to cite the data they have shared. Whenever possible the scripts and other artefacts used to generate the analyses presented in the paper should also be publicly archived. If sharing data compromises ethical standards or legal requirements then authors are not expected to share it.
Mandates Data Sharing
JPBB requires, as a condition for publication, that the data supporting the results in the paper will be archived in an appropriate public repository. Authors are required to provide a data availability statement, including a link to the repository they have used, and to cite the data they have shared. Whenever possible the scripts and other artefacts used to generate the analyses presented in the paper should also be publicly archived. Exceptions may be granted at the discretion of the editor, for example, if sharing data compromises privacy of human data, ethical standards or legal requirements. If authors are unable to share data (for example, if sharing data compromises ethical standards or legal requirements) then authors are not required to share it and must describe restrictions in their data availability statement.
Mandates Data Sharing and Peer Reviews Data
JPBB requires, as a condition for publication, that the data supporting the results in the paper will be peer reviewed and archived in an appropriate public repository. Authors are required to provide a data availability statement, including a link to the repository they have used, and to cite the data they have shared. Whenever possible the scripts and other artefacts used to generate the analyses presented in the paper should also be publicly archived. Exceptions may be granted at the discretion of the editor. If sharing data compromises ethical standards or legal requirements then authors are not required to share it.
And:
Peer review of empirical data will be conducted to confirm the quality of the shared data, for example, that sample sizes match, that the variables described in the article are present as fields in the data repository, that data is complete; that data is properly labelled and described; and that it has the appropriate metadata for the kind of data being shared.
Or:
Peer review of empirical data will be conducted to confirm that the data reproduce the analytic results reported in the paper.
Standard Templates for Author Use
Below is a list of standard templates for the text that will appear in the "Data Availability Statement" portion of your article. These statements adhere to guidelines set forth to comply with journal that have an "Expects Data" and "Mandates Data" policy.
|
Availability of data |
Template for data availability statement |
|
Data openly available in a public repository that issues datasets with DOIs |
The data that support the findings of this study are openly available in [repository name e.g “figshare”] at http://doi.org/[doi], reference number [reference number]. |
|
Data openly available in a public repository that does not issue DOIs |
The data that support the findings of this study are openly available in [repository name] at [URL], reference number [reference number]. |
|
Data derived from public domain resources |
The data that support the findings of this study are available in [repository name] at [URL/DOI], reference number [reference number]. These data were derived from the following resources available in the public domain: [list resources and URLs] |
|
Embargo on data due to commercial restrictions |
The data that support the findings will be available in [repository name] at [URL / DOI link] following an embargo from the date of publication to allow for commercialization of research findings. |
|
Data available on request due to privacy/ethical restrictions |
The data that support the findings of this study are available on request from the corresponding author. The data are not publicly available due to privacy or ethical restrictions. |
|
Data subject to third party restrictions |
The data that support the findings of this study are available from [third party]. Restrictions apply to the availability of these data, which were used under license for this study. Data are available [from the authors / at URL] with the permission of [third party]. |
|
Data available on request from the authors |
The data that support the findings of this study are available from the corresponding author upon reasonable request. |
|
Data sharing not applicable – no new data generated |
Data sharing is not applicable to this article as no new data were created or analyzed in this study. |
|
Author elects to not share data |
Research data are not shared. |
|
Data available in article supplementary material |
The data that supports the findings of this study are available in the supplementary material of this article |
|
Data sharing not applicable – no new data generated, or the article describes entirely theoretical research |
Data sharing not applicable to this article as no datasets were generated or analysed during the current study |
When data is available and linked, authors will need to provide a citation of the data in their reference list.
Data [dataset] citation:
Authors. Year. Dataset title; Data repository or archive, Version (if any), Persistent identifier (e.g. DOI)
To cite your dataset, the authors can use JPBB endnote file and download it from the link below
Policy on data archiving
Evolution requires, as a condition for publication, that data supporting the results in the paper should be archived in an appropriate public archive, such as GenBank, TreeBASE, Dryad, the Knowledge Network for Bio-complexity or other suitable long-term and stable public repositories. Data are important products of the scientific enterprise, and they should be preserved and usable for decades in the future. Authors may elect to have the data publicly available at time of publication, or, if the technology of the archive allows, may opt to embargo access to the data for a period of up to a year after publication. Exceptions may be granted at the discretion of the editor, especially for sensitive information such as a human subject data or the location of endangered species.
Data Accessibility Statement
Authors are required to archive their data in a publicly accessible repository such as Dryad, FigShare, GenBank, etc. (not a laboratory homepage) and clearly state in their manuscript where their data will be deposited.
• Upon submission, this statement must be included, but we are happy for authors to wait until acceptance of their paper to actually archive their data (although note that many repositories will enable authors to embargo publication of their data during the review process).
• Upon acceptance, data must be archived and the Data Accessibility statement completed including database and information such as accession numbers or DOI (as available) for all data from the manuscript.
• Note: if data, scripts, or other artefacts used to generate the analyses presented in the paper are available via a publicly available data repository, authors should include a reference to the location of the material within their paper.
Example:
"Data Accessibility:
- DNA sequences: Genbank accessions F234391-F234402; NCBI SRA: SRX0110215
- Final DNA sequence assembly uploaded as online
- Climate data and MaxEnt input files: Dryad doi:10.5521/dryad.12311
- Sampling locations, morphological data and microsatellite genotypes: Dryad doi:10.5521/dryad.12311”
Manuscripts lacking a Data Accessibility section will not be passed through to an editor.
Dryad: Note that if authors choose to use the Dryad data repository, Evolution will pay the archiving charges on their behalf if their paper is published in the journal.
GitHub: While GitHub is a very useful resource, and we are certainly happy for authors to post underlying data or code there, its lack of permanence (i.e. data/code in GitHub can be deleted or modified at a later date) means it does not strictly meet our criteria for data availability; as such we would ask authors placing data in GitHub to additionally deposit this data in a permanent repository (like Dryad) which will assign a DOI.