by Sarah Williams (University of London)
(Note: to see my EpiDoc files and EFES customisation, and for local links in this post to work, you will need to download my fork of EFES from https://github.com/Minna-Loushe/EFES-Pollentia, install and run from the command line, as per the instructions at https://github.com/EpiDoc/EFES/wiki/Installation, and discussed below.)
I. Project Outline and Aim
This project was inspired by the EpiDoc/EFES week of SunoikisisDC 2024-25 and by I. Vagionakis’ 2021 article about her Cretan EpiDoc/EFES database. EpiDoc is an international, collaborative effort that provides guidelines and tools for encoding scholarly and educational editions of ancient documents (described in detail at https://epidoc.stoa.org/). EFES (EpiDoc Front End Services) is a custom and readily customizable platform for publication and search/indexing of EpiDoc files (see https://github.com/EpiDoc/EFES).
The EFES user guide states that a student with a working knowledge of EpiDoc should be able to use EFES without prior experience of computer programming or software development, criteria I fulfil. My aim was to explore the feasibility of getting EFES up and running ‘out-of-the-box’ for the inscriptions of the Roman town of Pollentia on Mallorca; I aimed to utilise any existing open access digital resources together with a hard copy of the CIBalear corpus as published in 1965 (CIBalear = Veny, C. Corpus de las Inscripciones Balearicas Hasta la Dominacion Arabe). The corpus of inscriptions from Pollentia numbers around 80, of which Veny knew 44 in 1965; Pollentia remains an active archaeological dig site with discoveries subsequent to 1965 regularly published, making it ideal in size and scope for this project.
[Since 12 May 2025 CIBalear has become freely downloadable online, a wonderful work of scholarship, full of stories of antiquarian discovery, forgery, thefts, the Spanish civil war and Castilian/Catalan politics.]
II. Methodology
There are two Roman Pollentias—one in Mallorca and one in Liguria, Italy. My first task was to discover any existing digital editions of the relevant inscriptions. To find the Mallorcan results in the Epigraphik-Datenbank Clauss/Slaby (EDCS) you must first search by “Pollentia”, scrape your results, and then by “Inca”; the inscriptions are quirkily categorised to these different towns for no apparent reason. Starting with the EDCS results and using the direct links on that site to the Epigraphic Database Heidelberg (EDH) is the only successful way of finding the inscriptions in EDH (for reasons explained below). EDH contains only inscriptions published in Veny 1965 (why?) although CIBalear54 is missing—despite being neither more fragmentary nor more likely a fake than any other. EDCS contains the entire corpus, but only EDH provides downloadable EpiDoc files.
To begin my project I forked EFES to my GitHub account with GitHub Desktop running (following instructions at https://github.com/EpiDoc/EFES/wiki/Installation) and watched M. Filosa et al’s completely indispensable 2021 Epidoc/EFES online training week. I then imported EpiDoc files from EDH into EFES and named them by their CIBalear** references. Extremely naively, I expected EFES functionality would work off the mark-up (which I knew existed in my imported files), and that I could move on to updating my EFES corpus with new EpiDoc files for inscriptions discovered since 1965. I now realise how hopelessly unrealistic this was and, in my next section, will document my problem-solving for all the functions that EFES offers one by one. My aim in showing the (sometimes minute) details of my trials and errors is to attempt to be of use to anyone else beginning an EFES project for the first time.
I note in passing that there is a simpler way to get EFES running (especially in the absence of a Github account) by downloading a ZIP file. Full instructions are also included on the Installation page.
III. Exploring EFES out-of-the-box
III.1. Indexing
The onomastics and prosopography of Pollentia are particularly fascinating so I decided to try and get the indexing of ‘persons’ or ‘personal names’ working using EFES’ authority lists. It turned out to be my most challenging task—here is what I learned:
EFES ‘out-of-the-box’ has no authority list for ‘persons’ or ‘personal names’ but I understood how to make one (see M. Filosa et al 2021—especially Day 4/Part 1). I followed the instructions and spent a long day completely failing to index a single person or name. Eventually I worked out why; EDH EpiDoc files are marked up for persons in an unexpected way. For example, in CIBalear30 the edition is as follows:

Cornelius Atticus is then also marked up as a person in a separate section in the .xml (an equivalent function to the use of authority lists in EFES, designed to remove the need for such tagging in the text itself), as follows:

This appears on the EDH website as follows:

But in EFES epidoc-persons-index-to-solr.xsl only looks within the edition:

I can see that there are solutions. One could change the template matching in the .xsl file—beyond my capability. Or one could change the mark-up within the editions, which is within my capability but was not possible in my available timeframe.
In my quest to get an index working I moved on to a feature where I knew that the mark-up was as I expected. EFES comes with an index for ‘places’ which then appear as ‘toponyms’ and an authority list for ‘mentionedplace’. I marked up mentioned places and updated the authority list—it worked.

These are all the instances of mentioned places within my mini corpus. And I was able to solve the problem that out-of-the-box EFES does this…:

… due to having watched the online training (M. Filosa et al 2021, specifically Day 4/Part 2, approx. mins 19-23). I have mentioned that these sessions are indispensable.
III.2. Facets and Searching
A satisfying side effect of sorting out the indexing for mentioned places is that the faceted search function works with no further intervention:

This is the correct information and you can click on each item and it returns the correct list of inscriptions.
I knew from the User Guide that only ‘some’ of the pre-existing facets require the use of authority lists so I worked my way through. For example, without my doing anything the search for ‘found provenance’ returned this….

…but these are not clickable and you cannot discover which 11 or 43 inscriptions belong to each category. Unfortunately, almost all (all?) the ‘place’ related information in these EDH files is incorrect. geonames.org/2512432 is modern Pollença, a town in Mallorca, but not particularly near Pollentia, which is in modern Alcúdia. geonames.org/2510769 is, simply, Spain and should therefore apply to all these inscriptions. Pleiades:383745 (found throughout) is, unfortunately, the site of Pollentia in Liguria, Italy. (The ‘current repository’ data is also incorrect as the Mallorcan authorities have moved the inscriptions around.) Searching the pre-existing facets does therefore have the side benefit of being a fast method to check the validity of any imported mark-up.
I moved on to ‘origin place’, filled in the authority list and got it working:

This ‘Pollentia’ is now clickable and will return CIBalear20, which is the only one I marked up. All the rest would be the same as we have little granularity beyond simply the site name for the largely antiquarian discoveries.
Similarly with ‘support material’:

The first two items are not yet clickable but for the third, ivory, I have marked up the authority list (retaining the eagle-network.eu information in the authority list).
I do not fully understand why some facets are picking up data directly from the EpiDoc files and returning partial (although not useful) results, but neither does one need to understand this to get the functionality working. I note that once I have removed any informational URL into the authority list the output no longer appears in blue in the inscription .html (words in blue are clickable). The word search box worked nicely without my doing anything. The editions are not lemmatised but that is not in the scope of this project.
III.3. Date Slider
Initially the Date Slider was not working. I found that all the dates are marked up:
- <origDate notBefore-custom=”0001” notAfter-custom=”0051” datingMethod=”http://en.wikipedia.org/wiki/Julian_calendar“>1 AD – 51 AD</origDate>
One gets faster in EFES with practice so I knew (without resorting to tutorials!) that it would not like the ‘-custom’—with it removed the Date Slider worked perfectly.
III.4. Adding Images
This is straightforward once one has been intensely frustrated and then noticed that .jpg is very different to .jpeg in EFES.
III.5. Multilingualism
It is self-evident that EFES-Pollentia should at least be fully bilingual. Although the first language of Mallorca is Mallorquin Catalan, Veny published in Castilian, as do many other scholars of Pollentia. Perhaps therefore it should be fully trilingual and I explored the EFES functionality for this.
The EDH files contain no Translation or Commentary (or Apparatus Criticus). However, I had Veny’s so, using CIBalear20 as my test case, I marked up the translation as follows (the Castilian is Veny and the English is my translation of Veny):

This appears in the .html as follows:

I followed the same process for the Commentary. Only the English then appears in the .html but to see the Castilian you can change ‘en’ to ‘es’ at http://127.0.0.1:9999/en/inscriptions/CIBalear20.html. (Note that links to pages within my project will only work if you have EFES running locally.) To fully customise the languages of a project in EFES, as the User Guide points out, one would need to know how to write .xsl and .xmap files.
III.6. Bibliographic Concordance
I had underestimated the ‘concordance’ element of this function. Examining it earlier would have helped me to think about how to name files and organise this project. I proved the concept of using this function by adding EDH to my CIBalear20 file but it would be a lengthy task to complete the full concordance.

The first <listBibl> is as entered by the EDH editor and the second by me using the authority list. The output is as below:

III.7. EFES-Pollentia Homepage
To create a homepage I imitated examples I had of existing EFES projects along with some trial and error. To innovate one would need to learn CSS for this (not covered in the EFES online training).
Note that the homepage for Vagionakis’ wonderful Cretan project (available at https://github.com/IreneVagionakis/CretanInscriptions, with Github or ZIP instructions for access) looks different depending which browser you use—the first screenshot is Safari and the second Firefox:
(1)
(2) 
IV. Discussion/Conclusion
My results can be found at: https://github.com/Minna-Loushe/EFES-Pollentia (as for all EFES projects one needs EFES running, as detailed in the Installation pages, to explore this in detail).

I was able to get this EFES project up and running ‘out-of-the-box’; all the functionality works with my sample of files.
I certainly learned the importance of an appropriate ‘edition structure template’; I wonder how best to create this since one knows the most about a corpus when quite a long way through a project? Although I imported EpiDoc files from EDH I wondered if it would have been easier to start from scratch and, for my project, this may remain an open question due to the inaccuracies throughout the imported files. Other project authors may not encounter the same difficulties, and the EDH files are there to be re-used, as discussed by F. Grieshaber in 2019.
EFES’s own suggested uses are both the publication and management of a student’s own workflow, either individually or collaboratively, and I notice that other projects use the functionality to help with this. For example, Dobias-Lalou et al.’s igcyr2 uses a search facet as follows:

I. Polinskaya, A. Ivantchik et al at IOSPE more than meticulously track their changes:

By ‘commenting out’ one can write notes within an EpiDoc file to evidence which areas still need work, or which have been checked. One might want to index/search by the last date a file was changed, for example, or know it is considered finalised—to use the functionality to manage the workflow.
EFES is more than useful for a student working on a corpus: the iterative process creates immediate feedback and the problem solving itself teaches invaluable lessons about one’s work (and EFES somehow starts teaching about itself). In the ‘real world’ one would soon want to innovate and seek to learn XSLT, CSS and Cocoon Sitemaps, hardly a bad thing.











