Research Data, Code & AI Policy

Supporting transparency and reproducibility in AI and data-science research.

Because Intelligence, Informatics and Infrastructure publishes research at the intersection of artificial intelligence, data science, and civil engineering, the integrity and reproducibility of data and software are central to the value of the work we publish. The following policies apply to all manuscripts.

Research Data Availability

Authors are encouraged to make the data underlying their results openly available in a trusted repository (for example, J-STAGE Data, Zenodo, figshare, or a recognised domain repository), and to cite the dataset with a persistent identifier (DOI) where possible. Every manuscript must include a Data Availability Statement describing where the data can be found and under what conditions they can be accessed.

Example statements:

“The data that support the findings of this study are openly available in [repository] at https://doi.org/[DOI].”

“The data are available from the corresponding author upon reasonable request.”

“Data sharing is not applicable to this article, as no new data were created or analysed.”

Where data cannot be shared (e.g., privacy, security, or contractual restrictions), authors should state this and explain why.

Shared data should follow the FAIR principles (Findable, Accessible, Interoperable, and Reusable): deposit them with a persistent identifier, descriptive metadata, and a clear licence. Where data concern Indigenous peoples or communities, the CARE principles for Indigenous data governance should also be respected. Authors should follow the reporting guidelines recognised for their study design where these exist — for example, PRISMA for systematic reviews and meta-analyses.

Software & Code Availability

For studies whose conclusions depend on custom software, models, or analysis pipelines, authors are encouraged to share their code to enable reproduction. Code may be deposited in a public repository (e.g., GitHub) and archived with a persistent DOI (e.g., via Zenodo). A Code Availability Statement should specify where the code resides, the licence under which it is released, and the computational environment required to run it.

Authors should report key details — framework and version, random seeds, hyper-parameters, and hardware — sufficient to reproduce the reported results.

Use of AI Tools

This policy covers generative and non-generative artificial-intelligence (AI) tools, including large language models (LLMs). Its guiding principles are transparency — everyone involved discloses how AI tools were used — and human responsibility: authors remain responsible for their manuscripts, reviewers for their reviews, and editors for their decisions. It follows COPE's position on authorship and AI tools and will be reviewed as practice develops.

Authors

Reviewers

Editors and the editorial office

Persistent Identifiers & Metadata

Related: For Authors · Open Access & Copyright · Indexing & Archiving