International Journal of Negative Results

International Journal of Negative Results

International Journal of Negative Results – Data Archiving Permissions

Open Access & Peer-Reviewed

Submit Manuscript

Data Archiving Permissions

Support transparent, responsible data sharing for negative results.

FAIR DataFindable, accessible, interoperable data.
PrivacyProtect sensitive records.
Code TransparencyShare pipelines and scripts.
Long Term PreservationStable repositories and metadata.

Journal at a Glance

ISSN: 2641-9181
DOI Prefix: 10.14302/issn.2641-9181
License: CC BY 4.0
Peer reviewed open access journal

Scope Alignment

Negative results, null findings, replication studies, methodological transparency, and reproducibility across disciplines. We prioritize rigorous reporting and complete outcomes.

Publishing Model

Open access, single blind peer review, and rapid publication after acceptance and production checks. Metadata validation and DOI registration are included.

Data Archiving Permissions

IJNR supports open, responsible data sharing for negative results and replication studies. Authors should deposit data and code in trusted repositories when possible, with clear access instructions.

We recognize that some datasets require controlled access due to privacy, consent, or regulatory constraints. Authors should document restrictions and access pathways.

Recommended Repositories
  • General data repositories such as Zenodo, Figshare, or Dryad
  • Clinical and cohort datasets with controlled access and data use agreements
  • Genomics and transcriptomics repositories such as GEO or ArrayExpress
  • Proteomics repositories such as ProteomeXchange
  • Code repositories such as GitHub or GitLab with release tags
Sensitive Data and Privacy

Patient identifiers must be removed and data should be deidentified in line with applicable 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, access review procedures, and consent limits.

Data and Code Availability Statements
  • 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
Preferred File Formats
Data TypePreferred FormatsNotes
Clinical datasetsCSV, TSVInclude data dictionaries
Imaging dataDICOM, NIfTIProvide acquisition protocols
Genomics/omicsFASTQ, BAM, VCFInclude pipeline details
Code and scriptsTXT, R, PYProvide version notes
Archiving Checklist
  • Dataset metadata complete and consistent
  • Repository accession numbers included
  • Code and pipelines documented
  • Ethics approvals and permits referenced
  • Access restrictions clearly stated
  • State whether datasets are deidentified and compliant with privacy regulations.
  • Provide repository DOIs or accession numbers for deposited datasets.
  • Describe metadata standards used to enable reuse and interoperability.
  • Clarify access controls for sensitive records and biospecimens.
  • Include code repository links for analysis scripts or statistical models.
  • List any embargo periods required by funders or collaborators.
  • Explain data sharing exceptions and provide justification when data are restricted.
  • Provide data dictionaries or variable definitions for key outcomes.
  • Describe data versioning and update procedures for longitudinal cohorts.
  • State whether datasets are available upon request or repository only.
  • Provide linkage between datasets and manuscript tables or figures.
  • Describe quality control thresholds for laboratory assays.
  • Document consent limitations for sharing sensitive records.
  • Provide anonymization techniques used for protected data.
  • Specify whether data use agreements are required for access.
  • Document repository metadata such as schema or variable labels.
  • Describe secure storage procedures for protected information.
  • Provide details on data retention timelines and preservation plans.
  • Clarify whether code is archived with a DOI or release tag.
  • Explain how negative results data support future replication.
  • Describe access request workflow and expected response time.
  • Report any restrictions tied to institutional policies.
  • Include documentation for data dictionaries and variables.
  • Clarify whether raw data or processed data are shared.
  • Provide checksum or version tags for large datasets.
  • Describe file formats and software needed to open datasets.
Data Archiving FAQ

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.

IJNR Commitment

IJNR is committed to rigorous, transparent publishing of negative, null, and inconclusive results. We emphasize reproducible methods, full outcome reporting, 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 complete reporting, data availability, and candid discussion of limitations to strengthen the research record.

Need Data Sharing Guidance?

Contact the editorial office for questions about repositories or permissions.