Data Archiving Permissions
Support transparent, responsible data sharing for diabetes bioinformatics research.
Journal at a Glance
ISSN: 2374-9431
DOI Prefix: 10.14302/issn.2374-9431
License: CC BY 4.0
Peer reviewed open access journal
Scope Alignment
Bioinformatics, computational genomics, multi-omics integration, systems biology, clinical informatics, and data driven insights for diabetes and metabolic disease. We prioritize reproducible analytics.
Publishing Model
Open access, single blind peer review, and rapid publication after acceptance and production checks. Metadata validation and DOI registration are included.
JBD supports open, responsible data sharing for diabetes bioinformatics research. Authors should deposit data and code in trusted repositories when possible, with clear access instructions.
We recognize that some clinical datasets require controlled access. Authors should document restrictions and access pathways.
- Sequence and omics data repositories such as GEO, SRA, or EGA
- Proteomics and metabolomics repositories such as PRIDE or MetaboLights
- General data repositories such as Zenodo, Figshare, or Dryad
- Code repositories such as GitHub or GitLab with release tags
- Clinical datasets with controlled access through approved data use agreements
Clinical or patient level data must comply with ethical approvals, consent requirements, and privacy regulations. When full sharing is not possible, provide deidentified summaries and clear instructions for requesting access.
Authors should document data governance, including data custodians and access review procedures.
- Include repository links or accession numbers in the manuscript
- State licensing terms for data and code when applicable
- Provide documentation for custom scripts or pipelines
- Describe any access restrictions and approval requirements
| Data Type | Preferred Formats | Notes |
|---|---|---|
| Genomics | FASTQ, BAM, VCF | Include reference build information |
| Transcriptomics | FASTQ, count matrices | Provide normalization details |
| Proteomics | mzML, RAW | Include search parameters |
| Clinical data | CSV, TSV | Deidentify patient data |
- Dataset metadata complete and consistent
- Repository accession numbers included
- Code and pipelines documented
- Ethics approvals referenced
- Access restrictions clearly stated
Can I embargo data?
Yes. Provide embargo details and expected release dates.
What if data are proprietary?
Explain restrictions and provide access request steps.
Is code sharing required?
We strongly encourage code sharing or detailed documentation.
- Include README files that describe variables, cohorts, and file structures.
- Provide data dictionaries for clinical variables and outcome measures.
- Specify repository version and update schedules for evolving datasets.
- Document deidentification steps for patient data.
- Provide checksum or hash values for large data downloads.
- Ensure code dependencies are listed with version numbers.
- Describe how access requests are reviewed and approved.
- Include contact details for data access queries.
- Provide sample metadata templates used for repository submissions.
- Clarify licensing terms for data and code reuse.
- Mention embargo periods and expected release dates if applicable.
- Provide guidance for citing datasets in related publications.
- Share workflow diagrams for data processing pipelines.
- Ensure file names are descriptive and consistent.
- Document storage formats for long term preservation.
- Describe any limitations on data reuse or redistribution.
- Provide metadata about sequencing platforms or assay kits used.
- Include sample consent restrictions for secondary use.
- Document file compression formats and extraction instructions.
- State whether updates to datasets will be versioned or replaced.
- Provide contact for data use agreements when applicable.
- Include minimal metadata for each sample such as age and sex.
- Document any anonymization tools or pipelines used.
- Provide persistent identifiers for datasets such as DOIs.
- Explain how raw and processed files are linked.
- Clarify retention periods for data stored in institutional repositories.
- Indicate whether data were generated under specific consent categories.
JBD is committed to rigorous, transparent publishing in bioinformatics and diabetes research. We emphasize reproducible computational methods, clear data provenance, and ethical compliance across all article types.
The editorial office supports authors, editors, and reviewers with clear guidance and responsive communication. For questions about scope or workflow, contact [email protected].
We encourage continuous improvement in reporting practices and share updates that help the community maintain high standards in computational and translational diabetes research.
Need Data Sharing Guidance?
Contact the editorial office for questions about repositories or permissions.