Data Archiving Permissions

Clear data stewardship practices for toxicology research.

JECT encourages sharing data that support toxicology findings. Data availability statements must describe where data are stored and how they can be accessed.

If data cannot be shared openly, describe the controlled access process and any requirements.

• Zenodo or OSF for protocols and datasets
• GEO or ArrayExpress for omics data
• Figshare for supplementary files
• Institutional repositories for clinical datasets
• Regulatory data portals when required

Protect participant privacy by de identifying clinical data and documenting consent requirements.

• Remove direct identifiers and indirect re identification risk
• Document consent or waiver details
• Provide data access committee contacts
• Explain any embargo periods or approvals

Clear documentation improves reuse and interpretation. Provide data dictionaries, variable definitions, and processing details.

Use these steps to ensure your data are usable and compliant.

• Provide a data dictionary and variable descriptions
• Include quality control procedures
• Describe data cleaning or normalization steps
• State software and version information
• Provide accession numbers or persistent links
• Clarify any reuse restrictions
• Include code or scripts when possible
• Document sample storage conditions
• Describe laboratory assay calibration methods
• Include metadata for exposure timing and dose

For questions about scope, data reporting, or compliance, contact the editorial team for guidance before submission.

Clear documentation improves reuse and interpretation.

• Provide README files for datasets
• Include codebooks for surveys or questionnaires
• List analytical methods and parameters
• Describe batch correction procedures
• Include QA or QC summaries
• Provide sample identifiers and mapping files
• Clarify missing data handling
• Include metadata for chemical identifiers
• Provide references for assay protocols
• Confirm licensing terms for data reuse

Clear reuse guidance improves scientific value.

• Specify permitted reuse for datasets
• Provide licensing terms for data
• Describe any embargo periods
• List required acknowledgements
• Explain how to cite datasets
• Provide contact for data access questions
• Clarify restrictions for sensitive data
• Describe de identification procedures

Protecting privacy is essential in clinical toxicology.

• Remove direct identifiers from datasets
• Aggregate data for small sample groups
• Document consent language for sharing
• Provide access controls for restricted data
• Describe data access approval processes
• Clarify storage and security safeguards
• Note compliance with local regulations

Data in toxicology often involve sensitive exposure or clinical information. JECT encourages FAIR data practices while protecting privacy. Use repositories that support persistent identifiers and provide clear documentation for reuse.

Describe data cleaning steps, quality controls, and assay calibration so others can reproduce results. Include data dictionaries and metadata that explain variables, units, and sampling conditions.

If data cannot be shared publicly, provide a clear access pathway with contacts, approval requirements, and expected timelines. Transparency about restrictions maintains trust and supports responsible reuse.

Clear access statements support transparency.

• Describe how to request access for restricted data
• Provide expected response timelines
• List any data use agreement requirements
• Explain review criteria for access requests
• Include repository contact information
• State whether data can be reused for meta analyses
• Provide a citation format for datasets
• Note any embargo periods

Confirm these details to support responsible sharing.

• Provide clear data access instructions
• Confirm repository metadata completeness
• Add persistent identifiers for datasets
• Clarify reuse permissions and licenses
• Document data cleaning steps in README files
• Include version numbers for datasets
• Confirm sample identifiers are consistent
• Provide contact for restricted access
• Verify de identification procedures
• Confirm compliance with local regulations
• Provide documentation for code dependencies
• Include file format descriptions

These reminders help readers locate and reuse data responsibly.

• Include persistent links to repositories
• Provide accession numbers in the manuscript