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
- ▪ AI as the subject or method of the research. Many papers in this journal develop or apply AI models. Where AI models are part of the research design (for example, models that are trained and evaluated, or generative models used to synthesise data or images), they must be described in the Methods in enough detail to reproduce the work: the model and version, settings, training and evaluation data, and how outputs were validated.
- ▪ AI as an assistant in preparing the manuscript. Any other use of AI tools — for example, to search or summarise the literature, design the study, analyse data, write or debug code, generate or edit text, produce or edit figures and tables, or format references — must be disclosed in a “Use of Generative AI” section placed before the Acknowledgments. Name each tool (and version), state what it was used for, and explain how its output was checked. Routine spelling and grammar checking does not need to be declared.
- ▪ Images and results. Generative AI must not be used to create or alter images, figures, or data that are presented as results, except where this is itself part of the research design and is described in the Methods.
- ▪ References. Authors must check every reference against the original source. References that do not exist or do not support the statement they are cited for are treated as a serious error.
- ▪ Authorship and responsibility. AI tools cannot meet the requirements for authorship, because they cannot take responsibility for the work, and so cannot be listed as authors. Authors are fully responsible for all content, including any part produced with AI assistance, and must ensure that AI-generated material does not infringe copyright (see Third-Party Material & Permissions).
- ▪ Undisclosed use. If undisclosed use of AI tools comes to light, the editors will ask the authors to explain and will act in line with COPE guidance; this may lead to rejection or, after publication, to a correction or retraction.
Reviewers
- ▪ Reviewers must not upload a manuscript, or any part of it (text, figures, data, or code), to AI tools or other external services, and must not use AI tools to evaluate the manuscript or to generate the content of their review. Doing so would breach the confidentiality of peer review.
- ▪ The only permitted use is translation. Reviewers may use machine-translation or AI tools solely to translate review comments that they have written themselves into English. Only the reviewer's own comments may be entered, never text or material from the manuscript. The reviewer remains responsible for the accuracy of the translation, must state in the confidential comments to the editor that a translation tool was used (and which one), and the handling editor checks the translated review before it is sent to the authors.
Editors and the editorial office
- ▪ Editorial decisions (desk rejection, revision, acceptance, or rejection) are made by the editors. AI tools are not used to make editorial decisions, to assess scientific merit, or to write peer-review reports.
- ▪ Reviewers are selected and invited by the handling editor. The journal does not use automated or AI-based tools to suggest or invite reviewers.
- ▪ All submissions are screened for textual similarity with iThenticate (Crossref Similarity Check); its reports are interpreted by the editors.
- ▪ Technical checks. The editorial office may use AI tools to help with technical checks of submitted and revised manuscripts — for example, to verify that cited references exist and are described correctly, and to check consistency between the title, abstract, text, tables, and figures. Any problem found is confirmed by an editor before it is raised with the authors. These checks support, and do not replace, peer review: AI tools are not used to judge the novelty or significance of the work or to recommend a decision.
- ▪ After acceptance, the editorial office uses AI tools to assist with copy-editing and proofreading the final manuscript — for example, to detect typographical errors, inconsistencies between the text, tables, and figures, and errors in the reference list. Every change suggested by these tools is checked by the editorial office, and the corresponding author approves the final proof before publication.
- ▪ The editorial office uses AI tools only under terms that do not allow manuscript content to be used to train AI models, and manuscripts remain confidential to the editorial process.
Persistent Identifiers & Metadata
- ▪ An ORCID iD is required for the corresponding author from Volume 8, No. 1 (2027) and strongly encouraged for all co-authors. ORCID iDs are included in article metadata.
- ▪ All articles receive a DOI (prefix 10.11532) and are delivered in full-text JATS XML / HTML and PDF.
- ▪ Reference lists are openly available under the Initiative for Open Citations (I4OC), and, from Volume 8 (2027), machine-readable licence information is embedded in each article.
Related: For Authors · Open Access & Copyright · Indexing & Archiving