A source document, in this case, would, for example, be a letter. In the case of ediarum, it is the idea of generating knowledge by explicating information present in source documents. Methodology and ImplementationĤAt a high level of methodological abstraction, one can ask in what part of the scientific, in this instance, the editorial process a tool attempts to support the researcher. After being used for projects at the BBAW internally for many years, modules are released successively to the public via a GitHub repository 8, which includes all relevant contact information, licenses, and acknowledgments. 7ģIt is being developed by the TELOTA (The Electronic Life Of The Academy) initiative at the BBAW in Berlin by lead developers Stefan Dumont, Martin Fechner, and Sascha Grabsch. It should be noted that ediarum is not intended and marketed as a plug-and-play solution for any particular usecase, but rather a toolbox 6 that can be adapted for the specific uses of any one project. In addition to this, it allows the sharing of this data via a REST API or via WebDAV. These are supplemented by the ediarum.DB module, which uses the eXist-db database to provide a central repository for the XML data, and for central indexes of entities that can then be directly looked up and referenced from Oxygen. The two ‘edit’ modules of ediarum are customized to offer the most common functionality an editor of TEI XML Data would need, such as the easy generation of metadata fields, markup of structural text elements, textual phenomena and entities. The Author mode is an alternative way to display XML files that allows users to edit the documents in a way that is much closer to a WYSIWYG editor or a word processor. and are so-called ‘frameworks’ for the Author mode of Oxygen. It allows the user to work with XML data, specifically TEI, by using a graphical user interface without having to manually write XML in a text editor. These two applications are widely used by projects in the context of digital scholarly editions and ediarum aims to provide an environment optimized for working with transcriptions and the markup of these transcriptions within those tools. For the purpose of this review, I used a MacOS 10 System with Java Runtime Environment 8, Oxygen XML Editor version 21 and eXist-db version 4.4.Ģ Ediarum, at its core, is a set of extensions for two other applications, namely the Oxygen XML Editor 4 and eXist-db 5. These three tools are also what I will be referring to as ediarum in this article. ![]() for print and web publication) of ediarum have been announced and are internally already being used (Dumont and Fechner 2019) but have not yet been released publicly and will therefore not be the subject of this review which will limit itself to the three modules available at this time. As indicated by the leading version number, they can be considered as ‘ready for production’, although, as is the nature of continuously developed software, are likely to be further developed and improved in the future. Integrated into those modules is ediarum.JAR 3.1.0. ![]() The modules discussed here were released throughout 2018. The first release from the ediarum software environment was ediarum.JAR in December 2013, a module which is now integrated into the three modules reviewed. 1This review examines three tools: ediarum.DB, and, which are part of the continuously developed “work and publication environment for scholarly editing” ediarum 1 developed by the Berlin-Brandenburg Academy of Sciences and Humanities (Berlin-Brandenburgische Akademie der Wissenschaften, BBAW).
0 Comments
Leave a Reply. |