{"word_count": 1590, "character_count": 9600}
I am now at the second part of the trinity previously mentioned in this article: the encoding. This portion of the work has already been partly explained in some of the first posts (there and there) but it was mainly about the content of the XML tree that will be used for each letter of the corpus. This post will address the means used to transform the text transcription that I obtain, according to the method described in the previous post, in an XML-TEI encoded text, that will then be used in the final post.In order to do so, I have created a three-step workflow that allows an easy and quick encoding of the letters, one by one. The first step consists of creating the XML file, with the right template and with almost all the files’ metadata. Next, I encode the text that I exported from eScriptorium. Finally, I insert the encoded text in the template, then correct some mistakes and add the manual tags to the encoding.First step: Creating the XML fileFor a given corpus, two XML files containing each a document from the corpus will not really differ in terms of the content of the metadata (&#60;teiHeader&#62;). As I mentioned it in this post, I made a XML tree template for my corpus, where only a few metadata will have to be filled to give each file its corresponding data (the template with no characteristic data can be found at the end of this document).Instead of having to fill the specific information manually, I developed a script, combined with a CSV file, that allows me to create all the files from the corpus (right now, this amounts to 520 letters) while filling some specific data in each document.The CSV is a key element for the creation of the XML file. It consists of the number of pages and two other elements, repeated multiple times but in different ways: the letter’s date and number. For each letter, I have three figures: the number of the current letter, the preceding letter and the following letter. For the date, I have it in four formats: YYYY-MM-DD, French, English and French with no spaces, which I use to name my files. Then, in this same last format, I have the preceding and following letter.[caption id="attachment_3887" align="aligncenter" width="500"] CSV file for the letters[/caption]With the help of a script that extracts the rows' content of the CSV, line by line and uses variables and combinations in a given XML tree (the template), I am able to create a file with the number and the date of the letter (format = LettreN_DDmonthYYYY). Then, I can already encode the following information in the &#60;teiHeader&#62;:The title of the letter with its number and its date, both in English and FrenchThe date of the letter in &#60;docDate&#62;, &#60;origDate&#62; and &#60;date&#62; from &#60;correspDesc&#62;The preceding and following letter in &#60;correspContext&#62;[caption id="attachment_3890" align="aligncenter" width="500"] XML Tree created[/caption]Moreover, the quickness and easiness of this process (approximately 30 seconds to create the 520 files) give me the opportunity to do it multiples times, without encountering any issue, which is practical because there is one more important information added to the tree. Every time an action is taken on in an XML file, it is good practice to encode a &#60;change&#62; tag in the &#60;revisionDesc&#62; to keep track of the process. In the XML tree proposed in the script, I wrote a &#60;change&#62; tag with the following form:&#60;change when-iso="" who="#floriane.chiffoleau"&#62;Creation of the file&#60;/change&#62;Since I don’t encode every letter in one session but rather few letters at a time, it is important to stay consistent and to have a date for the creation of the file, corresponding to the day where I start working on the letter. So, every time I start working on some letters, I generate new templates with the current date in order to be thorough.Once this is done, I have a proper XML file with mostly filled metadata fields and I now need to work on the body part of the file.Second step: Encoding the textTo encode my text, I need a document in a text format. To have that, as I previously said, I export from eScriptorium the result of the process described in the previous article about transcribing the corpus.It can be necessary to check the text for errors missed during the previous task: for incorrect line numbering, which is an error sometimes made by eScriptorium (in that case, I’ll just have to invert the lines to follow the correct numbering and have a coherent text); and mostly for instance where one word or phrase have been added above a line and it needs to be included in its attributed line in order not to mess up the encoding.After that, I can use the text tagging script I created to encode my corpus. It is a pretty simple script that works mostly with regular expressions and with find/replace commands to encode the text. As I mentioned it multiple times about my corpus, it contains numerous recurring elements, present in every letter (with some exceptions). The main problem is that those recurrent elements do not always have the same writing.For example, Paul d’Estournelles de Constant addresses every letter in the corpus to Nicholas Murray Butler. In every one of them, he addresses directly the letter to him with “à Monsieur le Président Nicholas Murray BUTLER”. However, while this set phrase is always to be found, it sometimes has other wordings:“à Monsieur le Président N. Murray BUTLER”“à Monsieur le Président N.Murray BUTLER.”“à Monsieur le Président Nicholas Murray BUTLER,”The surname is not consistently written fully and sometimes, nothing but the initial is present; the set phrase can end up with a comma or a point or nothing. This is why the regular expression is useful because I wrote it in order for the script to find it in every text, no matter how it is written. This is also the case for the date or the page numbering, which changes every time but does have the same structure. Then, with those regular expressions, I apply a find/replace command so that the script will find the exact expression in the text and will encode it with the corresponding tags. Finally, the script also tags the paragraphs by finding end-of-lines with a punctuation sign that indicates a sentence ending and suppresses all the newline to create line break (&#60;lb/&#62;) with specification if the word had been cut off by d’Estournelles.[caption id="attachment_3889" align="aligncenter" width="478"] Text format of the letter 120[/caption][caption id="attachment_3888" align="aligncenter" width="500"] Letter 120 after application of the text tagging script[/caption]Third step: Correcting the encodingLastly, the final step will consist of corrections and additions to what has been encoded. Firstly, I use the result of step one and two by inserting the tagged text in its corresponding XML file. I then have one script that corrects the errors made by the preceding script and that closes open tags; however, there is one element that has to be tagged manually beforehand, because I did not find a way to do it automatically: the letter title, situated in the opener. Once this is done, I can apply my new script to the XML file.This script combines find/replace commands in a text in order to correct the mistakes made previously and BeautifulSoup commands in an XML file to add new encoding information. Among the mistakes made by the preceding script, there are improper paragraph tags added before the &#60;salute&#62; or the &#60;closer&#62; that need to be removed or it will mess up the encoding and line break placed just before page beginning tags, which is redundant and out of place.Then, with BeautifulSoup, I can automatically attribute the page’s number to the &#60;pb&#62; tag, if it is given, search for the letter’s writing place and then add it in the &#60;origPlace&#62; tag and in &#60;correspDesc&#62; and while doing so, I add a new &#60;change&#62; tag to the &#60;revisionDesc&#62;, with information about what is done (“First encoding of the transcription and some specific metadata”) and the current date (added in the terminal when I apply the script). If after that, there are still some errors that were not corrected and that make the file non conform, they need to be manually rectified.I now have a fully formed XML file, with adequate encoding and a complete tree. The last task consists in an image-to-text comparison. Some tags sometimes need to be changed if they have not been placed correctly, like when a line beginning has been considered a new paragraph and it is in fact not one. Peculiarities from the letter also need manual tagging, whether they are deleted and/or added words, underlined word(s) or sentence(s), or elements added afterwards by d’Estournelles, like characters handwritten to correct words or hand notes. Lastly, I fill the metadata that need precision and after a final proofreading, I can consider that the encoding of the transcription is complete.With this, I now have a defined process to encode the letters swiftly and easily, with numerous automatic procedures that leave me mostly with a correction job, since every transformation of files is done with one or several script(s). All I have to do is check that the files are correct and are XML-TEI compliant. Once the transcription is encoded accordingly to how the text is written in the letter, it reaches the first level of finalization of the transcription: “proposed”. The next level will be related to what I will explain in the next and last part of this blog post series: the annotation.