Citing OpenEtruscan
OpenEtruscan is archived on Zenodo and minted with a persistent DOI. Every release ships a versioned snapshot of the code and the corpus, and citations resolve to a single concept DOI that always points at the most recent deposit.
Two citation modes, one DOI
The Zenodo deposit covers both the software (the Next.js frontend, the FastAPI backend, the classifiers, and the philological pipelines) and the underlying dataset (the unified inscription corpus, drawn from the Larth Dataset and CIE Vol. I, together with derived embeddings and evaluation artefacts). Citing OpenEtruscan as software or as a dataset resolves to the same Zenodo concept DOI in either case.
DOI10.5281/zenodo.20075835BibTeX
Drop this entry into your .bib file. The concept-DOI keeps the record current; bump version and year if you want to pin a specific release.
@software{openetruscan_2026,
author = {Panichi, Edoardo},
title = {{OpenEtruscan: open-source digital corpus platform for Etruscan epigraphy}},
year = {2026},
version = {1.2.0},
doi = {10.5281/zenodo.20075835},
url = {https://doi.org/10.5281/zenodo.20075835},
publisher = {Zenodo}
}RIS
EndNote, Zotero, Mendeley, and most reference managers will import the following RIS block directly.
TY - COMP
T1 - OpenEtruscan: open-source digital corpus platform for Etruscan epigraphy
AU - Panichi, Edoardo
PY - 2026
DA - 2026///
PB - Zenodo
DO - 10.5281/zenodo.20075835
UR - https://doi.org/10.5281/zenodo.20075835
ET - 1.2.0
ER - Concept DOI vs. version-specific DOIs
Zenodo mints two kinds of DOI for OpenEtruscan. The concept DOI (10.5281/zenodo.20075835) is stable across every release and always resolves to the latest archived version; this is the right DOI for a general citation. Each tagged release additionally receives its own version-specific DOI visible on the deposit page on Zenodo. Cite the version-specific DOI when reproducibility requires pinning to an exact snapshot of the code and corpus you ran against.
How to cite the dataset
The Zenodo deposit is a combined software + dataset record, so the corpus itself (the unified inscriptions, their metadata, the philological annotations, and the derived embeddings) falls under the same DOI listed above. If your journal expects a separate dataset citation, you can reuse the same BibTeX/RIS entry above and substitute the entry type (@dataset in BibTeX, TY - DATA in RIS). The DOI does not change.
Source, machine-readable metadata, and reproducibility
- Eddy1919/openEtruscan路 canonical source repository
- CITATION.cff路 machine-readable citation file (CFF 1.2)
- reproduce-rosetta-eval-v1.md路 canonical reproducibility note for the Rosetta eval
Questions about citing OpenEtruscan, or want us to add a community-specific citation template? Open an issue on the project tracker and we will be happy to help.