Data Archiving Permissions
The Journal of Air and Water Borne Diseases supports transparent, reproducible research. Authors are encouraged to archive data, code, and supplementary materials in trusted repositories while protecting patient privacy and regulatory obligations. This policy explains what you may share, where to share it, and how to document access.
Air and water borne disease research often includes clinical data, environmental sampling, laboratory measurements, and longitudinal outcomes. We encourage authors to archive data that supports published results so readers can verify findings and build on your work. Data sharing should balance transparency with participant privacy and legal obligations. This guidance aligns with common funder expectations for transparent data stewardship. When data cannot be fully open, authors must provide a clear access statement that explains the restriction.
Authors may archive de identified datasets, statistical code, supplementary figures, protocols, and extended methods. For outbreak studies, share data that enables reproduction of analyses without exposing patient identities or sensitive locations. Environmental and microbial datasets may require additional safeguards and must follow institutional guidelines.
De identified datasets supporting primary outcomes.
Analysis code and scripts used to generate results.
Protocols, methods, and supplementary figures.
Metadata files describing variables and units.
Use trusted repositories that provide stable identifiers and long term access. Select a repository that fits your data type and complies with institutional or funder requirements. If you are unsure, ask the editorial office before submission.
Supplementary files should be clearly labeled and referenced in the main text. Preferred formats include CSV or XLSX for data tables, PDF for extended methods, and standard image formats for figures. Large imaging or geospatial files should be compressed without loss of analytical quality. Provide a brief description for each file so readers can understand how it supports the study.
Discipline Specific
Institutional Repositories
General Repositories
Controlled Access
All submissions must include a data availability statement that explains where supporting data can be found, any access restrictions, and contact details for requests. If data cannot be shared, provide a justification and describe how results were validated.
Provide repository name, accession number, or DOI.
Explain any restrictions for patient or legal reasons.
List a contact for qualified data access requests.
Describe how results can be verified if data is closed.
When data is shared in a repository, include the citation and persistent identifier in the reference list. Proper data citation recognizes the work of data creators and helps readers locate supporting evidence. If you reuse external datasets, cite the source and describe how the data was integrated into your analysis. This practice strengthens transparency and reuse.
Patient privacy is paramount in infectious disease research. Remove identifiers, apply anonymization, and follow consent agreements. If data must be embargoed or restricted, document the reason and provide a timeline for release when possible. Editors may request additional documentation to confirm compliance with institutional policies.
When clinical or location based data cannot be shared openly, provide aggregate results and a clear description of how qualified researchers can request access. State the expected data retention period and any governance body responsible for approving access requests.
Authors retain rights to their data and may apply appropriate licenses in repositories. Use clear terms that allow reuse with attribution, but avoid licenses that conflict with patient consent or institutional agreements. If third party datasets are used, obtain permission and cite the original source.
Support Reproducible Public Health Research
Well documented data sharing increases trust and impact. Contact the editorial office if you need guidance on repository selection or access statements. We respond promptly.