The LatEpig tool allows you to query all the inscriptions from the Epigraphic Database Clauss Slaby (www.manfredclauss.de) in a reproducible manner: it saves the search results in a TSV and a JSON file and plots them on an interactive map of the Roman Empire without any prior knowledge of programming in a matter of minutes.

• Brian Ballsun-Stanton, Macquarie University,
• Petra Heřmánková, Aarhus University,
• Ray Laurence, Macquarie University,

This programme allows to extracts the output of a search query from the Epigraphik-Datenbank Clauss / Slaby (EDCS) in a reproducible manner and saves it as a TSV file (i.e. tab separated value) that can be easily opened in your favourite spreadsheet software, or as a JSON file. The search results can be also plotted to a map of the Roman Empire, along with the system of the Roman Provinces, roads, and cities. More on the used datasets in the Data Sources section.

Ballsun-Stanton B., Heřmánková P., Laurence R. LatEpig (version 2.0). GitHub. URL: https://github.com/mqAncientHistory/Lat-Epig/ DOI: 10.5281/zenodo.5211341

If you're using this tool in your research, Star us on Github! (This way, we don't need to put tracking pixels into this notebook to get a sense of how many folks are using our tool!)

If you find a bug or have a feature request, raise an Issue!

The Epigraphik-Datenbank Clauss / Slaby (EDCS) is a digital collection of more than 500,000 Latin inscriptions, created by Prof. Manfred Clauss, Anne Kolb, Wolfgang A. Slaby, Barbara Woitas, and hosted by the Universitat Zurich and Katolische Universitat Eichstat-Ingoldstadt.

Ancient World Mapping Centre, political shading shapefiles, following the Barington Atlas of Greek Roman World, [AWMC.UNC.EDU ], under the Creative Commons Attribution-NonCommercial 4.0 International License.

1. Roman Empire 60 BC (provinces or extent)
2. Roman Empire in AD 14 (provinces or extent)
3. Roman Empire in AD 69 (provinces or extent)
4. Roman Empire in AD 117 (DEFAULT, provinces or extent)
5. Roman Empire in AD 200 (provinces or extent)

1. McCormick, M. et al. 2013. Roman Road Network (version 2008), DARMC Scholarly Data Series, Data Contribution Series #2013-5. DARMC, Center for Geographic Analysis, Harvard University, Cambridge MA 02138.

2. Ancient World Mapping Centre, road shapefiles, shapefile for roads, following the Barington Atlas of Greek Roman World, under the Creative Commons Attribution-NonCommercial 4.0 International License. Collection of shapefiles also vailable through the UCD Digital Library

1. The shapefile of the cities used in the map is based on Hanson, J. W. (2016). Cities Database (OXREP databases). Version 1.0. Accessed (date): http://oxrep.classics.ox.ac.uk/databases/cities/. DOI: https://doi.org/10.5287/bodleian:eqapevAn8. More info available through Hanson, J. W. (2016b). An Urban Geography of the Roman World, 100 B.C. to A.D. 300. Oxford: Archaeopress.

Each TSV and JSON file contains the information from EDCS separated into 22 attributes. The LatEpig Metadata description document in the Github repo describes the contents of individual attributes along with their description and original source.

Note that the file name in both formats contains the date of your search, source of the data and how it was accessed (EDCS via LatEpig) and any search parametres or their combinations you have used (Term 1, Term 2, Dating from...) and the number of inscriptions found. This way you will always remember what you have searched for and when you share the file with a colleague or students, they can always replicate your search to see if any new inscriptions were added to EDCS. The same applies for the publication quality maps (experimental feature) produced by LatEpig: they all contain the search parametres by default, alongside with the origin of information and credit - all in the spirit of the best research practice and FAIR data principles.

To launch Lat-Epig on myBinder click on the following icon

No need for powerful computer, as the tool runs on external servers with a single click. This option is ideal if you want to test the tool or do small searches (with up to 1000 results). Searches with more than 1000+ results will still run, however, the interactive map may not be created or it may take long time as the memory on the myBinder is limited. For creation of interactive maps based on large searches, we recommend using the Docker option (see below).

When the Jupyter Notebook starts, click the fast-forward button, or choose the Kernel menu from the top bar and choose Restart & Run All. Further step-by-step instructions and search examples are provided within the Jupyter Notebook.

1. Install Docker on your computer. See instructions for your OS (Windows instructions, Linux instructions + Add users to Docker inscructions, Mac instructions)
2. Start Docker
3. Open a Command Line / Terminal
4. Test if Docker runs by running docker run hello-world
5. If you see the following message, you have installed Docker succesfully: Hello from Docker! This message shows that your installation appears to be working correctly.
6. Now run the following to start the LatEpig within Docker. You will need a stable internet connection as you will download almost 2 GB. docker run -p 8888:8888 denubis/lat-epig-scraper:main
7. Go to your browser (Firefox, Chrome...) and paste in http://localhost:8888/notebooks/EpigraphyScraper.ipynb and you should see the LatEpig interface.

Note: If your computer is low on memory, we recommend using Firefox instead of Chrome. If you have troubles starting Docker, close Chrome, and all non-essential software and try again with Firefox browser.

For testing or development purposes mainly. We recommend using Ubuntu 22.04+.

Run the following code inside a virtualised environment using direnv and pyenv

sudo apt-get update && sudo apt-get install -y --no-install-recommends apt-transport-https apt-utils build-essential ca-certificates curl git libbz2-dev libffi-dev libgeos++-dev liblzma-dev libncurses5-dev libproj-dev libreadline-dev libsqlite3-dev libssl-dev libxml2-dev libxmlsec1-dev make proj-bin proj-data python3-pip wget zlib1g-dev libgeos-dev libxml2-dev libxslt-dev python-dev libc6 libgcc-s1 libgeos-c1v5 libproj15 libstdc++6 libpython3.8-dev python3.8 python3.8-tk
curl -fsSL https://deb.nodesource.com/setup_15.x | bash -
sudo apt-get install -y --no-install-recommends  nodejs
pip3 install numpy==1.20.1 cython wheel
pip3 install --no-cache-dir -r requirements.txt 
jupyter nbextension enable --py widgetsnbextension --sys-prefix &&  jupyter labextension install @jupyter-widgets/jupyterlab-manager &&   jupyter labextension install @voila-dashboards/jupyterlab-preview &&  jupyter serverextension enable voila --sys-prefix &&  jupyter contrib nbextension install --sys-prefix &&   jupyter nbextension enable init_cell/main
jupyter trust EpigraphyScraper.ipynb 
jupyter lab EpigraphyScraper.ipynb 

Next, rerun all cells of the Jupyter Notebook.

Optional Running voila --enable_nbextensions=True --VoilaConfiguration.file_whitelist="['.*']" EpigraphyScraper.ipynb may provide a cleaner UI than Jupyter Notebook.

For feedback, or to report bugs, please use the Github Issues.

Happy epigraphic explorations!