About Armarium
In ancient and medieval times, book collections were often small. They could be stored in an armarium, i.e. a cabinet standing upright against a wall, or perhaps in a theca (or bibliotheca), typically a chest on the floor. The Latin word armarium must have originally applied to a store for weapons. It was more commonly used, however, to describe a cabinet or cupboard in general (cf. French armoire, etc.), including a book-case.
The image below, from the mausoleum of Galla Placidia in Ravenna (c. AD 425–450) depicts a Late Antique armarium on the left, with shelves and doors, containing the four Gospels. It is similar to the famous depiction of the scribe Ezra writing beside an armarium in the eighth-century Codex Amiatinus.
This digital Armarium is also a repository for texts. It aims to faciliate scholars who wish to publish scholarly digital editions, especially of short to medium length. Its principles of simple technical implementation, long-term preservation, citability, readability, and quality assurance are explained further below.
Design principles
1. Simple technical implementation
The primary goal of Armarium is to make it as simple as possible for researchers to publish their editions online. To that end, the technical barrier is kept as low as possible.
Content should be supplied in XML, a format that is very easy to learn. More specifically, the XML should conform to the recommendations of the Text Encoding Initiative (TEI). You do not need to study the vast TEI guidelines, however. You can just use the XML templates and short documentation provided here (to follow).
The same principle of simplicity also supports long-term preservation and readability (see below).
Simplicity does not need to be a limitation. The data behind all of editions will be freely available to be processed and analysed in more complex applications.
2. Long-term preservation
The core of this resource is the XML data underlying each edition. XML is an excellent format for long-term archiving. This data will be deposited and made publicly accessible in long-term data repositories (GitHub and Zenodo) to ensure access for future generations.
The technology running the website (HTML, CSS and some very light PHP scripts) is also chosen to be as simple as possible, in order to minimise requirements for updating and maintenance. This will support the long-term stability of the web resource.
3. Citability
Editors deserve full and clear recognition for their work. Each edition is presented with a recommended citation formula at the head of every page. This will include a unique DOI as well as a simple, human-readable URL (web address).
4. Readability
The primary function of any edition is to be read. Armarium aims to present text in a simple, uncluttered and accessible format, with attention to typographical detail (on both desktop and mobile screens). Graphical content, user-interface elements and colours are kept minimal, to support restful reading and concentration.
5. Quality assurance
Armarium will have an editorial board to review submissions and ensure the overall quality of the collection. Editors may also choose to avail of a more formal anonymous peer-review process (and claim peer-review status accordingly).
Credits and technical information
Armarium is managed and developed by Pádraic Moran, University of Galway. All of the source code and data files are fully accessible on GitHub.
For advice about publishing an edition, contact Pádraic at padraic.moran@universityofgalway.ie.