austin-papers-tei.xml

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model https://raw.githubusercontent.com/i-d-e/ride/master/schema/ride.rng application/xml http://relaxng.org/ns/structure/1.0?>
<?xml-model https://raw.githubusercontent.com/i-d-e/ride/master/schema/ride.rng application/xml http://purl.oclc.org/dsdl/schematron?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="ride.17.4">
   <teiHeader>
      <fileDesc>
         <titleStmt>
            <title>Digital Austin Papers</title>
            <author ref="https://orcid.org/0009-0008-3678-9070">
               <name>
                  <forename>Ruth</forename>
                  <surname>Sander</surname>
               </name>
               <affiliation>
                  <orgName>Berlin-Brandenburgische Akademie der Wissenschaften</orgName>
                  <placeName>Berlin</placeName>
               </affiliation>
               <email>ruth.sander@bbaw.de</email>
            </author>
         </titleStmt>
         <publicationStmt>
            <publisher>Institut für Dokumentologie und Editorik e.V.</publisher>
            <date when="2024-05">May 2024</date>
            <idno type="URI">http://ride.i-d-e.de/issues/issue-17/austin-papers</idno>
            <idno type="DOI">10.18716/ride.a.17.4</idno>
            <idno type="archive"
               >https://github.com/i-d-e/ride/raw/master/issues/issue17/austin-papers/austin-papers.pdf</idno>
            <availability>
               <licence target="http://creativecommons.org/licenses/by/4.0/"/>
            </availability>
         </publicationStmt>
         <seriesStmt>
            <title level="j">RIDE - A review journal for digital editions and resources</title>
            <editor ref="https://orcid.org/0000-0001-8820-5112">Tessa Gengnagel</editor>
            <editor ref="https://orcid.org/0000-0001-8279-9298">Frederike Neuber</editor>
            <editor ref="https://orcid.org/0000-0003-3167-5089">Daniela Schulz</editor>
            <editor ref="https://orcid.org/0000-0003-2852-065X" role="managing">Ulrike
               Henny-Krahmer</editor>
            <editor ref="https://orcid.org/0000-0001-8279-9298" role="managing">Frederike
               Neuber</editor>
            <editor ref="https://orcid.org/0000-0003-1438-3236" role="managing">Martina
               Scholer</editor>
            <editor ref="https://orcid.org/0000-0001-8279-9298" role="technical">Frederike
               Neuber</editor>
            <biblScope unit="issue" n="17">Digital Scholarly Editions</biblScope>
            <idno type="URI">http://ride.i-d-e.de/issues/issue-17</idno>
         </seriesStmt>
         <notesStmt>
            <relatedItem type="reviewed_resource">
               <bibl>
                  <title>Digital Austin Papers</title>
                  <editor>Andrew Torget; Debbie Liles</editor>
                  <respStmt>
                     <resp>Editor</resp>
                     <persName>Torget, Andrew J</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Editor</resp>
                     <persName>Liles, Debbie</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Programmer</resp>
                     <persName>Brumfield, Ben W.</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Programmer</resp>
                     <persName>Ellis, Jason</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Programmer</resp>
                     <persName>Brumfield, Sara Carlstead</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Programmer</resp>
                     <persName>Hicks, William</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Programmer</resp>
                     <persName>Mues, Stephen</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Programmer</resp>
                     <persName/>
                  </respStmt>
                  <respStmt>
                     <resp>Contributor</resp>
                     <persName>Dalziel, Karin</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Contributor</resp>
                     <persName>Kilgore, Deborah</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Contributor</resp>
                     <persName>Sinclair, Cameron</persName>
                  </respStmt>
                  <date type="publication">2016</date>
                  <idno type="URI">https://digitalaustinpapers.org</idno>
                  <date type="accessed">2024-03-14</date>
               </bibl>
            </relatedItem>
            <relatedItem type="reviewing_criteria">
               <bibl>
                  <ref target="http://www.i-d-e.de/criteria-version-1-1">Criteria for Reviewing
                     Scholarly Digital Editions</ref>
               </bibl>
            </relatedItem>
         </notesStmt>
         <sourceDesc>
            <p>born digital</p>
         </sourceDesc>
      </fileDesc>
      <encodingDesc>
         <classDecl>
            <taxonomy
               xml:base="http://www.i-d-e.de/publikationen/weitereschriften/criteria-version-1-1">
               <category>
                  <catDesc>Documentation</catDesc>
                  <category xml:id="se001">
                     <catDesc>Bibliographic description <ref target="#K1.2">cf. Catalogue 1.2</ref>
                     </catDesc>
                     <catDesc>Is it easily possible to describe the project bibliographically along
                        the schema "responsible editors, publishing/hosting institution, year(s) of
                        publishing"?</catDesc>
                     <category xml:id="se002">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se003">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se004">
                     <catDesc>Contributors <ref target="#K1.4">cf. Catalogue 1.4</ref>
                     </catDesc>
                     <catDesc>Are the contributors (editors, institutions, associates) of the
                        project fully documented?</catDesc>
                     <category xml:id="se005">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se006">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se007">
                     <catDesc>Contacts <ref target="#K1.5">cf. Catalogue 1.5</ref>
                     </catDesc>
                     <catDesc>Does the project list contact persons?</catDesc>
                     <category xml:id="se008">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se009">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se010">
                     <catDesc>Selection <ref target="#K2.1">cf. Catalogue 2.1</ref>
                     </catDesc>
                     <catDesc>Is the selection of materials of the project explicitly
                        documented?</catDesc>
                     <category xml:id="se011">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se012">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se013">
                     <catDesc>Reasonability of the selection <ref target="#K2.1">cf. Catalogue
                           2.1</ref>
                     </catDesc>
                     <catDesc>Is the selection by and large reasonable?</catDesc>
                     <category xml:id="se014">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se015">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se016">
                     <catDesc>Archiving of data <ref target="#K4.16">cf. Catalogue 4.16</ref>
                     </catDesc>
                     <catDesc>Does the documentation include information about the long term
                        sustainability of the basic data (archiving of the data)?</catDesc>
                     <category xml:id="se017">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se018">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se019">
                     <catDesc>Aims <ref target="#K3.1">cf. Catalogue 3.1</ref>
                     </catDesc>
                     <catDesc>Are the aims and purposes of the project explicitly
                        documented?</catDesc>
                     <category xml:id="se020">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se021">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se022">
                     <catDesc>Methods <ref target="#K3.1">cf. Catalogue 3.1</ref>
                     </catDesc>
                     <catDesc>Are the methods employed in the project explicitly
                        documented?</catDesc>
                     <category xml:id="se023">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se024">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se025">
                     <catDesc>Data model <ref target="#K3.7">cf. Catalogue 3.7</ref>
                     </catDesc>
                     <catDesc>Does the project document which data model (e.g. TEI) has been used
                        and for what reason?</catDesc>
                     <category xml:id="se026">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se027">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se028">
                     <catDesc>Help <ref target="#K4.15">cf. Catalogue 4.15</ref>
                     </catDesc>
                     <catDesc>Does the project offer help texts concerning the use of the
                        project?</catDesc>
                     <category xml:id="se029">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se030">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se031">
                     <catDesc>Citation <ref target="#K4.8">cf. Catalogue 4.8</ref>
                     </catDesc>
                     <catDesc>Does the project supply citation guidelines (i.e. how to cite the
                        project or a part of it)?</catDesc>
                     <category xml:id="se032">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se033">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se034">
                     <catDesc>Completion <ref target="#K4.16">cf. Catalogue 4.16</ref>
                     </catDesc>
                     <catDesc>Does the editon regard itself as a completed project (i.e. not promise
                        further modifications and additions)?</catDesc>
                     <category xml:id="se035">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se036">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se037">
                     <catDesc>Institutional curation <ref target="#K4.16">cf. Catalogue 4.16</ref>
                     </catDesc>
                     <catDesc>Does the project provide information about institutional support for
                        the curation and sustainability of the project?</catDesc>
                     <category xml:id="se038">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se039">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Contents</catDesc>
                  <category xml:id="se040">
                     <catDesc>Previous edition <ref target="#K2.2">cf. Catalogue 2.2</ref>
                     </catDesc>
                     <catDesc>Has the material been previously edited (in print or
                        digitally)?</catDesc>
                     <category xml:id="se041">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se042">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se043">
                     <catDesc>Materials used <ref target="#K2.2">cf. Catalogue 2.2</ref>
                     </catDesc>
                     <catDesc>Does the edition make use of these previous editions?</catDesc>
                     <category xml:id="se044">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se045">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se046">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se047">
                     <catDesc>Introduction <ref target="#K4.15">cf. Catalogue 4.15</ref>
                     </catDesc>
                     <catDesc>Does the project offer an introduction to the subject-matter (the
                        author(s), the work, its history, the theme, etc.) of the project?</catDesc>
                     <category xml:id="se048">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se049">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se050">
                     <catDesc>Bibliography <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the project offer a bibliography?</catDesc>
                     <category xml:id="se051">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se052">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se053">
                     <catDesc>Commentary <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the project offer a scholarly commentary (e.g. notes on unclear
                        passages, interpretation, etc.)?</catDesc>
                     <category xml:id="se054">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se055">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se056">
                     <catDesc>Contexts <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the project include or link to external resources with contextual
                        material?</catDesc>
                     <category xml:id="se057">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se058">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se059">
                     <catDesc>Images <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the project offer images of digitised sources?</catDesc>
                     <category xml:id="se060">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se061">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se062">
                     <catDesc>Image quality <ref target="#K4.6">cf. Catalogue 4.6</ref>
                     </catDesc>
                     <catDesc>Does the project offer images of an acceptable quality?</catDesc>
                     <category xml:id="se063">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se064">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se065">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se066">
                     <catDesc>Transcriptions <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Is the text fully transcribed?</catDesc>
                     <category xml:id="se067">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se068">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se069">
                     <catDesc>Text quality <ref target="#K4.6">cf. Catalogue 4.6</ref>
                     </catDesc>
                     <catDesc>Does the project offer texts of an acceptable quality (typos, errors,
                        etc.)?</catDesc>
                     <category xml:id="se070">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se071">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se072">
                     <catDesc>Indices <ref target="#K4.5">cf. Catalogue 4.5</ref>
                     </catDesc>
                     <catDesc>Does the project feature compilations indices, registers or
                        visualisations that offer alternative ways to access the material?</catDesc>
                     <category xml:id="se073">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se074">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se075">
                     <catDesc>Types of documents <ref target="#K1.3 #K2.1">cf. Catalogue 1.3 and
                           2.1</ref>
                     </catDesc>
                     <catDesc>Which kinds of documents are at the basis of the project?</catDesc>
                     <category xml:id="se076">
                        <catDesc>Single manuscript</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se077">
                        <catDesc>Single work</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se078">
                        <catDesc>Collection of texts</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se079">
                        <catDesc>Collected works</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se080">
                        <catDesc>Papers</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se081">
                        <catDesc>Archival holding</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se082">
                        <catDesc>Charters</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se083">
                        <catDesc>Letters</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se084">
                        <catDesc>Diary</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se085">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se086">
                     <catDesc>Document era <ref target="#K1.3 #K2.1">cf. Catalogue 1.3 and 2.1</ref>
                     </catDesc>
                     <catDesc>What era(s) do the documents belong to?</catDesc>
                     <category xml:id="se087">
                        <catDesc>Classics</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se088">
                        <catDesc>Medieval</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se089">
                        <catDesc>Early modern</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se090">
                        <catDesc>Modern</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se091">
                     <catDesc>Subject <ref target="#K1.3">cf. Catalogue 1.3</ref>
                     </catDesc>
                     <catDesc>Which perspective(s) do the editors take towards the edited material?
                        How can the edition be classified in general terms?</catDesc>
                     <category xml:id="se092">
                        <catDesc>History</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se093">
                        <catDesc>Philology / Literary Studies</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se094">
                        <catDesc>Philosophy / Theology</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se095">
                        <catDesc>History of Science</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se096">
                        <catDesc>Musicology</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se097">
                        <catDesc>Art History</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se098">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se099">
                     <catDesc>Spin-Offs <ref target="#K4.11">cf. Catalogue 4.11</ref>
                     </catDesc>
                     <catDesc>Does the project offer any spin-offs?</catDesc>
                     <category xml:id="se100">
                        <catDesc>App</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se101">
                        <catDesc>Mobile</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se102">
                        <catDesc>PDF</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se103">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se104">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Access modes</catDesc>
                  <category xml:id="se105">
                     <catDesc>Browse by <ref target="#K4.3">cf. Catalogue 4.3</ref>
                     </catDesc>
                     <catDesc>By which categories does the project offer to browse the
                        contents?</catDesc>
                     <category xml:id="se106">
                        <catDesc>Authors</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se107">
                        <catDesc>Works</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se108">
                        <catDesc>Versions</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se109">
                        <catDesc>Structure</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se110">
                        <catDesc>Pages</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se111">
                        <catDesc>Documents</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se112">
                        <catDesc>Type of material</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se113">
                        <catDesc>Images</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se114">
                        <catDesc>Dates</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se115">
                        <catDesc>Persons</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se116">
                        <catDesc>Places</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se117">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                        <catDesc>
                           <gloss>sentiment</gloss>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se118">
                     <catDesc>Simple search <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the project offer a simple search?</catDesc>
                     <category xml:id="se119">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se120">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se121">
                     <catDesc>Advanced search <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the project offer an advanced search?</catDesc>
                     <category xml:id="se122">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se123">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se124">
                     <catDesc>Wildcard search <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the search support the use of wildcards?</catDesc>
                     <category xml:id="se125">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se126">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se127">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se128">
                     <catDesc>Index <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the search offer an index of the searched field?</catDesc>
                     <category xml:id="se129">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se130">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se131">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se132">
                     <catDesc>Suggest functionalities <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the search offer autocompletion or suggest
                        functionalities?</catDesc>
                     <category xml:id="se133">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se134">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se135">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se136">
                     <catDesc>Help texts <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the project offer help texts for the search?</catDesc>
                     <category xml:id="se137">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se138">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se139">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Aims and methods</catDesc>
                  <category xml:id="se140">
                     <catDesc>Audience <ref target="#K3.3">cf. Catalogue 3.3</ref>
                     </catDesc>
                     <catDesc>Who is the intended audience of the project?</catDesc>
                     <category xml:id="se141">
                        <catDesc>Scholars</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se142">
                        <catDesc>Interested public</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se143">
                     <catDesc>Typology <ref target="#K3.3 #K5.1">cf. Catalogue 3.3 and 5.1</ref>
                     </catDesc>
                     <catDesc>Which type fits best for the reviewed project?</catDesc>
                     <category xml:id="se144">
                        <catDesc>Facsimile edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se145">
                        <catDesc>Archive edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se146">
                        <catDesc>Documentary edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se147">
                        <catDesc>Diplomatic edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se148">
                        <catDesc>Genetic edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se149">
                        <catDesc>Work critical edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se150">
                        <catDesc>Text critical edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se151">
                        <catDesc>Enriched edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se152">
                        <catDesc>Database edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se153">
                        <catDesc>Digital library</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se154">
                        <catDesc>Collection of texts</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se155">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se156">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se158">
                     <catDesc>Critical editing <ref target="#K3.6">cf. Catalogue 3.6</ref>
                     </catDesc>
                     <catDesc>In how far is the text critically edited?</catDesc>
                     <category xml:id="se159">
                        <catDesc>Transmission examined</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se160">
                        <catDesc>Palaeographic annotations</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se161">
                        <catDesc>Normalization</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se162">
                        <catDesc>Variants</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se163">
                        <catDesc>Emendation</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se164">
                        <catDesc>Commentary notes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se165">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se166">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se167">
                     <catDesc>XML <ref target="#K3.7">cf. Catalogue 3.7</ref>
                     </catDesc>
                     <catDesc>Is the data encoded in XML? </catDesc>
                     <category xml:id="se168">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se169">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se170">
                     <catDesc>Standardized data model <ref target="#K3.7">cf. Catalogue 3.7</ref>
                     </catDesc>
                     <catDesc>Is the project employing a standardized data model (e.g.
                        TEI)?</catDesc>
                     <category xml:id="se171">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se172">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se173">
                     <catDesc>Types of text <ref target="#K3.5">cf. Catalogue 3.5.</ref>
                     </catDesc>
                     <catDesc>Which kinds or forms of text are presented?</catDesc>
                     <category xml:id="se174">
                        <catDesc>Facsimiles</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se175">
                        <catDesc>Diplomatic transcription</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se176">
                        <catDesc>Edited text</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se177">
                        <catDesc>Translations</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se178">
                        <catDesc>Commentaries</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se179">
                        <catDesc>Semantic data</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Technical accessability</catDesc>
                  <category xml:id="se180">
                     <catDesc>Persistent identification <ref target="#K4.8">cf. Catalogue 4.8</ref>
                     </catDesc>
                     <catDesc>Are there persistent identifiers and an addressing system for the
                        edition and/or parts/objects of it and which mechanism is used to that
                        end?</catDesc>
                     <category xml:id="se181">
                        <catDesc>DOI</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se182">
                        <catDesc>ARK</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se183">
                        <catDesc>URN</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se184">
                        <catDesc>PURL.ORG</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se185">
                        <catDesc>Persistent URLs</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se186">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se187">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se188">
                     <catDesc>Interfaces <ref target="#K4.9">cf. Catalogue 4.9</ref>
                     </catDesc>
                     <catDesc>Are there technical interfaces like OAI-PMH, REST etc., which allow
                        the reuse of the data of the project in other contexts?</catDesc>
                     <category xml:id="se189">
                        <catDesc>OAI-PMH</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se190">
                        <catDesc>REST</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se191">
                        <catDesc>General API</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se192">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se193">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se194">
                     <catDesc>Open Access</catDesc>
                     <catDesc>Is the edition Open Access?</catDesc>
                     <category xml:id="se195">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se196">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se197">
                     <catDesc>Accessability of the basic data <ref target="#K4.12">cf. Catalogue
                           4.12</ref>
                     </catDesc>
                     <catDesc>Is the basic data (e.g. the XML) of the project accessible for each
                        part of the edition (e.g. for a page)?</catDesc>
                     <category xml:id="se198">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se199">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se200">
                     <catDesc>Download <ref target="#K4.9">cf. Catalogue 4.9</ref>
                     </catDesc>
                     <catDesc>Can the entire raw data of the project be downloaded (as a
                        whole)?</catDesc>
                     <category xml:id="se201">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se202">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se203">
                     <catDesc>Reuse <ref target="#K4.9">cf. Catalogue 4.9</ref>
                     </catDesc>
                     <catDesc>Can you use the data with other tools useful for this kind of
                        content?</catDesc>
                     <category xml:id="se204">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se205">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se206">
                     <catDesc>Declaration of rights <ref target="#K4.13">cf. Catalogue 4.13</ref>
                     </catDesc>
                     <catDesc>Are the rights to (re)use the content declared?</catDesc>
                     <category xml:id="se207">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se208">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se209">
                     <catDesc>License <ref target="#K4.13">cf. Catalogue 4.13</ref>
                     </catDesc>
                     <catDesc>Under what license are the contents released?</catDesc>
                     <category xml:id="se210">
                        <catDesc>CC0</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se211">
                        <catDesc>CC-BY</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se212">
                        <catDesc>CC-BY-ND</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se213">
                        <catDesc>CC-BY-NC</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se214">
                        <catDesc>CC-BY-SA</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se215">
                        <catDesc>CC-BY-NC-ND</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se216">
                        <catDesc>CC-BY-NC-SA</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se217">
                        <catDesc>PDM</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se218">
                        <catDesc>No license</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se219">
                        <catDesc>Multiple licenses</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se220">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
               </category>
            </taxonomy>
         </classDecl>
      </encodingDesc>
      <profileDesc>
         <langUsage>
            <language ident="en"/>
         </langUsage>
         <textClass>
            <keywords xml:lang="en">
               <term>sentiment analysis</term>
               <term>data exploration</term>
               <term>data modeling</term>
               <term>interface</term>
               <term>fair</term>
            </keywords>
         </textClass>
      </profileDesc>
   </teiHeader>
   <text>
      <front>
         <div type="abstract">
            <p>The digital edition <emph>Digital Austin Papers</emph> (DAP) collects the
               correspondence of Stephen F. Austin and a selection of key associates from the 1820s
               and 1830s. It provides valuable insight into the changes occurring in the Texas
               borderlands during the early 19th century, both politically and socially. DAP offers
               full-text views of the collection of letters and two methods to download their
               TEI/XML files. Great emphasis is placed on browsing and search functionalities,
               striving to test new ways to discover patterns within the dataset. Its incorporation
               of sentiment analysis is one of DAP’s more unique characteristics. DAP has great
               potential but requires some additional data processing (e.g. assigning authority file
               IDs) to achieve it.</p>
         </div>
      </front>
      <body>
         <div xml:id="div1">
            <head>Introduction</head>
            <p xml:id="p1">The subject of this review is the digital edition <emph>Digital Austin
                  Papers</emph> (DAP), developed at the Department of History, College of Liberal
               Arts &amp; Social Sciences at the University of North Texas<note xml:id="ftn1">
                  See <ref
                     target="https://web.archive.org/web/20230312094827/https:/history.unt.edu/"
                     >https://web.archive.org/web/20230312094827/https://history.unt.edu/</ref>.
               </note> and The Portal to Texas History<note xml:id="ftn2">
                  See <ref
                     target="https://web.archive.org/web/20230311192516/https://texashistory.unt.edu/"
                     >https://web.archive.org/web/20230311192516/https://texashistory.unt.edu/</ref>.
               </note>. The edition invites its users to “discover the Texas borderlands through the
               eyes of Stephen F. Austin” (<ref type="crossref" target="#austin2016b">Digital Austin
                  Papers 2016b</ref>), the “Father of Texas”. Specific focus is placed on the
               turbulent times of the 1820s and 1830s.</p>
            <p xml:id="p2">The early 19th century “constitutes a significant chapter in demographic
               expansion of English speakers into Spanish and Mexican territory” (<ref
                  type="crossref" target="#cummins2019">Cummins 2019</ref>, 172). Settlement
               interactions between Anglo and Spanish parties began during the era of the American
               Revolution with the arrival of the first Anglo-Americans in the Mississippi Valley.
               The situation reached its “final chapter” with the arrival of Anglo-Americans in
               Spanish Texas during the 1820s (<ref type="crossref" target="#cummins2019">Cummins
                  2019</ref>, 172–173). As a prominent land agent, Austin was in a unique position,
               working closely with all three parties. </p>
            <p xml:id="p3">On the 17th of January 1821, Moses Austin (Stephen F. Austin’s father)
               acquired permission to settle 300 families in Spanish Texas. Upon his father’s death
               in the summer of 1821, Austin took over his family’s venture. Through skilful and
               diplomatic negotiations, Austin was able to renew the official grant, and so the
               legal settlement of Anglo-Americans in Spanish (later Mexican) Texas commenced (<ref
                  type="crossref" target="#taylor2015">Taylor 2015</ref>). Austin’s efforts were
               successful. Over the next few years, he acquired three further grants to settle 900
               more families in the colony (<ref type="crossref" target="#texaslibrary2017">Texas
                  State Library and Archives Commission</ref>). During the 1820s and 1830s, Austin
               became “the most prominent land agent working with the government of Mexico to bring
               colonists from the United States into the Texas borderlands” <ref type="crossref"
                  target="#austin2016a">(Digital Austin Papers 2016a</ref>). Austin's significance
               to the region during this period is also reflected in the naming of the modern-day
               capital of Texas as “Austin” (<ref type="crossref" target="#humphrey2023">Humphrey
                  2023</ref>).</p>
            <p xml:id="p4">The numerous and well-preserved correspondence of Stephen F. Austin
               provides a deep insight into the historical circumstances in and around Texas in the
               1820s and 1830s, particularly within the social, political, and cultural fields. The
               corpus documents the climate and events affected by the shifting border boundaries of
               the time. It is an invaluable resource for researchers of the border regions,
               available and searchable in the digital edition, DAP, since 2016.</p>
            <p xml:id="p5">DAP mainly presents Austin‘s correspondence, although it also includes
               relevant correspondences belonging to family members and key associates. The content
               of the digital edition builds on Eugene C. Barker’s printed edition of the Austin
                  Papers.<note xml:id="ftn3">
                  Barker’s edition appeared in three volumes.
                  It is fully digitised and accessible online: <ref
                     target="https://web.archive.org/web/20231211095701/https:/texashistory.unt.edu/search/?fq=str_title_serial:%22The%20Austin%20Papers%22"
                     >https://web.archive.org/web/20231211095701/https:/texashistory.unt.edu/search/?fq=str_title_serial:%22The%20Austin%20Papers%22</ref>.</note>
               DAP aims to make the Austin correspondences available in digital form and to
               experiment with and provide new exploratory methods for discovering patterns within
               the corpus. One explorative method that makes DAP unique and sets it apart from its
               printed counterpart is the incorporation of sentiment analysis. Overall, the digital
               edition’s range of browsing options is arguably its biggest asset.</p>
            <p xml:id="p6">The editorial staff of the project consists of Andrew Torget and Debbie
               Liles. Ben W. Brumfield, Jason Ellis, Sara Carlstead Brumfield, William Hicks,
               Stephen Mues, Karin Dalziel, Deborah Kilgore, and Cameron Sinclair form the technical
               staff. DAP is a completed digital project, that is to say, it is an edition where the
               funding period has come to a close. However, it could still have more to offer, which
               I will point out in this review. Unfortunately, there is no saying whether future
               funding may occur.</p>
            <p xml:id="p7">Apart from that, its status as a completed project makes it possible to
               draw a proper conclusion on whether DAP achieved its objectives. This review will
               address different aspects of DAP step by step. Specific focus will be placed on the
               contents of the edition and data exploration possibilities.</p>
         </div>
         <div xml:id="div2">
            <head>Design and Usability</head>
            <p xml:id="p8">
               <figure xml:id="img1">
                  <graphic
                     url="http://ride.i-d-e.de/wp-content/uploads/issue_17/austin-papers/pictures/picture-1.png"/>
                  <head type="legend">Homepage of Digital Austin Papers.</head>
               </figure>I will begin this review with a brief description of the general
               presentation of the website, as this is the first impression one gets when visiting a
               new digital platform. The first thing that catches the eye when opening the website
               is the portrait of Stephen F. Austin<note xml:id="ftn4">
                  The portrait was painted by William Howard in
                  1833, one year before Austin was arrested on suspicion of inciting rebellion and
                  imprisoned in Mexico City. The portrait strongly resembles Chester Harding’s 1820
                  portrait of Daniel Boone (<ref type="crossref" target="#taylor2015">Taylor
                     2015</ref>). Daniel Boone himself was a known early American frontiersman (<ref
                     type="crossref" target="#britannica2023">Britannica 2023</ref>).</note>,
               effectively putting a face to the name (see <ref type="crossref" target="#abb1"
                  >figure 1</ref>). The overall design is clean, with a colour scheme based on the
               aforementioned portrait. </p>
            <p xml:id="p9">The homepage offers a short introduction, providing context to the
               subject matter and highlighting the aim of the digital edition. A box to the right
               gives an overview of the total number of letters, authors, recipients, and locations
               presented in the edition.<note xml:id="ftn5">
                  A total of 2183 letter, 668 authors, 341
                  recipients, and 223 locations.</note> This is a welcome sight, as it gives the
               user a preliminary understanding of the subject matter and scope of the project.
               Although the introduction states that the digital edition focuses on “the turbulent
               world of the Texas borderlands during the 1820s and 1830s” (<ref type="crossref"
                  target="#austin2016b">Digital Austin Papers 2016b</ref>), there are documents
               dated as early as 1789. The scope of DAP could be described in more detail on the
               homepage. As it is, users will only find this information when exploring the
               materials or reading the ‘About’ page. This observation also applies to the
               correspondents, as DAP holds letters not addressed to or composed by Stephen
               Austin.</p>
            <p xml:id="p10">Starting from the homepage, the collection is accessible through one of
               two means: The first is through the navigation bar with links to the ‘Search’,
               ‘Browse’, ‘About’, and ‘Contact’ pages respectively. The second is by clicking on the
               number of letters, authors, etc. found in the ‘counter box’. Selecting the total
               count of authors and recipients leads to the ‘Browsing’ page with the respective
               filter selected. In contrast, clicking on the total number of locations leads to the
               search. This may not seem intuitive because no specific location is selected for the
               full-text search. As a user, I expected a different destination: the browsing page
               with ‘origin’ or ‘destination’ selected, as is the case with the senders/recipients.
               For this to be plausible, the statistics would need to be adjusted to ‘origin’ and
               ‘destination’. </p>
            <p xml:id="p11">Overall, the website is easy to navigate. All relevant information is
               readily available and the navigation is relatively intuitive. This is aided by the
               fact that the website does not have many sub-sites that require users to click to the
               next page. The website itself is monolingual: all the texts and labels are in
               English.</p>
         </div>
         <div xml:id="div3">
            <head>Content of the Edition</head>
            <p xml:id="p12">
               <emph>Digital Austin Papers</emph> primarily focuses on the correspondence of Austin
               from the 1820s and 1830s. This includes a variety of document types such as letters,
               contracts, accounts, and more. The documents included in this digital edition are not
               limited to those penned by or sent to Stephen F. Austin. Several manuscripts belong
               to Austin’s family members and key associates. </p>
            <p xml:id="p13">At present, the digital edition consists of 2183<note xml:id="ftn6">
                  The statistics provided on the starting page
                  state 2183 letters; however, a quick count of the unique xml:ids found in the
                  edition’s data repository suggests the number is off by one and that there may be
                  2184 XML texts.</note> letters. The corpus covers the English-language documents
               collected in <ref target="https://tshaonline.org/handbook/online/articles/fba65"
                  >Eugene C. Barker</ref>’s printed edition of the Austin Papers, and additional
               English-language documents found in the Dolph Briscoe Center for American History
               (DB-CAH). A key factor in the decision to utilise the letters collected and
               transcribed in Barker’s edition is one universal to all edition projects: the need to
               allocate the project’s limited time and funding efficiently. As clearly stated in the
               project’s ‘About’ page, digitising the letters from the printed edition offered a
               greater return than creating new transcripts from the manuscripts. The main argument
               is the accuracy of Baker’s transcriptions of the original manuscripts.<note
                  xml:id="ftn7">
                  Some details on the review process and the
                  quality of Barker’s transcripts are provided in the project’s
                  documentation.</note> I am sure the community can appreciate this decision,
               especially since it also allowed the editors of DAP to allocate time to include
               additional papers that were previously left out of the Barker edition and were only
               partially available in various scattered collections. Scholars now have the
               opportunity to browse everything on one platform.</p>
            <p xml:id="p14">The decision to focus solely on the English texts in the preliminary
               stage of the project is not explicitly justified. Even though the majority of
               manuscripts are in English, there is also a substantial portion in Spanish and other
               languages (for example, the “<ref type="crossref" target="#moses">Moses and Stephen
                  F. Austin Papers</ref>” collection in The Portal to Texas History consists of 80%
               English and 19% Spanish texts). Taking a multilingual approach would be a great asset
               to the edition. On a positive note, further material with the same base conditions is
               available and could be used to extent the digital edition.</p>
            <p xml:id="p15">DAP covers a variety of different materials, spanning from personal
               letters to documents sent to or from political and bureaucratic bodies. A quick query
               for the distinct values found in <code>//textDesc/channel</code> of the XML files
               reveals that there are 174 channels by which their contents are categorised.<note
                  xml:id="ftn8">
                  Compare TEI entry for
                     <code>&lt;channel&gt;</code>: <ref
                     target="https://web.archive.org/web/20230312100344/https:/www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-channel.html"
                     >https://web.archive.org/web/20230312100344/https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-channel.html</ref>.</note>
               The following list provides the first ten channel modes found in the XML files.<list
                  rend="bulleted">
                  <item>"Letter"</item>
                  <item>"Remarks"</item>
                  <item>"Contract"</item>
                  <item>"Agreement"</item>
                  <item>"Statement"</item>
                  <item>"Statement"</item>
                  <item>"Memorandum"</item>
                  <item>"Account of Shipment"</item>
                  <item>"Statement of Account"</item>
                  <item>"Militia Commission"</item>
               </list>
            </p>
            <p xml:id="p16">This small snippet of values shows how diverse the content of the corpus
               is regarding the different document types. The breadth of materials alone makes this
               digital edition a useful resource for scholars from different fields, working on
               different research questions. Unfortunately, the channel count given above is not
               quite accurate and exaggerates the variety within DAPs documents. The values given in
               the XML are not always consistent, evident here in the two ‘Statement’ values, only
               deviating by a whitespace. Combinations of document types, such as ‘Letter / Court
               Case’, are also present in the XML files. As useful and interesting as this
               information is to researchers, such combinations complicate the data model and
               machine readability. Pros and cons should be discussed and made transparent. Overall,
               some data cleaning is needed before reliable conclusions can be drawn. Once cleaned,
               the categorisation of the documents would make an interesting browsing option for
               DAP, providing new perspectives on the dataset.</p>
            <p xml:id="p17">
               <figure xml:id="img2">
                  <graphic
                     url="http://ride.i-d-e.de/wp-content/uploads/issue_17/austin-papers/pictures/picture-2.png"/>
                  <head type="legend">Full-text view of an Austin letter.</head>
               </figure>The digital texts are presented individually as full-texts, accessible
               either through the browsing options or through the search. To give a visual example,
                  <ref type="crossref" target="#abb2">figure 2</ref> provides a screenshot of a
               letter from John Blanchard and George Lauman to Moses Austin sent on the 16th of
               March, 1795 (cf. <ref type="crossref" target="#barker2021">Barker 1924</ref>). As
               depicted, each full-text viewer provides a title (predominantly Sender to Recipient
               and Date), a summary of the contents extracted from the print edition, followed by
               the text and the source of the letter.<note xml:id="ftn9">
                  The source refers to the printed edition
                  compiled by Barker rather than a suggested citation for the digital edition.
               </note> Further contextual materials such as editorial comments, links to external
               sources etc., are not present. Offset to the top right, a ‘Download XML’ button
               offers users direct access to the letter’s XML file, which is a highly valuable
               feature. Due to various reasons, some digital editions choose only to offer their XML
               files in bulk from a public repository.<note xml:id="ftn10">Something DAP also does.</note> Although this
               option is preferable in some scenarios, for example when using the edition’s data for
               other projects, a single file download is a nice addition to gain a quick
               understanding of the data.</p>
            <p xml:id="p18">Taking a closer look at the XML files, the text encoding of the data
               seems rather sparse. A key point to begin with: DAP’s XML follows the TEI-P5
               guidelines, version 2.3.0, and was validated against the version 2.3.0 P5 DTD.<note
                  xml:id="ftn11"> See <ref
                     target="https://web.archive.org/web/20231126160009/https:/tei-c.org/Vault/P5/2.3.0/xml/tei/custom/schema/dtd/"
                     >https://web.archive.org/web/20231126160009/https:/tei-c.org/Vault/P5/2.3.0/xml/tei/custom/schema/dtd/</ref>.</note>
               The project’s documentation makes no mention of a project-specific schema. By
               following the TEI format, and clearly documenting this decision, DAP facilitates
               possible future integration of its data into other corpora. Thus, DAP fulfils one of
               the aspects recommended by the FAIR principles.<note xml:id="ftn12">For more information on the FAIR principles
                  see <ref
                     target="https://web.archive.org/web/20231211084756/https:/www.go-fair.org/fair-principles/"
                     >https://web.archive.org/web/20231211084756/https://www.go-fair.org/fair-principles/</ref>.
               </note>
            </p>
            <p xml:id="p19">Also found in the project’s documentation is a description of the XML
               file creation process. This includes a summary of the steps starting with the initial
               digitization, transcription through OCR, and finally editing/tagging. There is
               mention of various metadata fields to be included in the XML files, as well as some
               data points to be tagged.</p>
            <p xml:id="p20">Concerning the <code>&lt;body&gt;</code> of the texts, the documentation
               only states that mentioned people and places were tagged. Looking at the XML files it
               is clear that these requirements have been met. Next to some minor stylistic and
               structural tags such as <code>&lt;div1&gt;</code>, <code>&lt;p&gt;</code> and
                  <code>&lt;hi&gt;</code>, the focus has been placed on people, places, and dates.
               Considering DAP’s aim to explore sentiment and topic modelling based browsing
               functionalities, further tagging of the text body is not strictly necessary. Name,
               place, and date tags cover all the remaining search options. </p>
            <p xml:id="p21">It is worth mentioning, however, that the tagged people and places do
               not come with <code>@ref</code>, project-specific IDs or Authority File IDs. This is
               a missed opportunity, especially considering that the standardized place names found
               in the <code>&lt;teiHeader&gt; (&lt;placeName type="origin"&gt;</code> and
                  <code>&lt;placeName type="destination"&gt;</code><note xml:id="ftn13">
                  These elements are found in the
                     <code>&lt;sourceDesc&gt;</code>. Information describing the actions of a
                  correspondence (for example the act of sending or receiving) are commonly found in
                     <code>&lt;correspDesc&gt;</code>. For more details, see <ref
                     target="https://web.archive.org/web/20231211144836/https:/www.tei-c.org/release/doc/tei-p5-doc/de/html/ref-correspDesc.html"
                     >https://web.archive.org/web/20231211144836/https://www.tei-c.org/release/doc/tei-p5-doc/de/html/ref-correspDesc.html</ref>.</note>)
               were passed through Geonames to collect coordinates for the map-based browsing
               interface. It should not pose too much work to retroactively create project-based
               person IDs or add geoNames IDs in the XML files, should work on the project continue
               in the future. On the other hand, including Authority File IDs for correspondents may
               require more effort and a deeper understanding of the subject matter. The results,
               however, would be worth the effort. These additions could improve some of the search
               results discussed later in this review. The interoperability and reusability of DAP’s
               data would also be positively affected, as it improves the finding and linking of
               people/places across projects.</p>
            <p xml:id="p22">Overall, the data has much to offer, more than is currently tagged. One
               example would be organisations mentioned in the text. Occasionally, these are tagged
               as places (<code>&lt;placeName&gt;</code>) rather than institutions.<note
                  xml:id="ftn14">
                  This is the case in John Adams’ letter to
                  Stephen Austin from the 7th of January 1808: <ref
                     target="https://web.archive.org/web/20220630202923/http:/digitalaustinpapers.org/document?id=APB0134.xml"
                     >https://web.archive.org/web/20220630202923/http://digitalaustinpapers.org/document?id=APB0134.xml</ref>.</note>
               Stephen F. Austin’s role as a land agent meant that he had close connections with
               government institutions and small businesses. Tagging these mentions and
               incorporating them into the search would lead to new research opportunities. Creating
               and presenting a list of all tagged organisations and their frequency could prove
               very interesting.</p>
            <p xml:id="p23">Having said that, it would be remiss not to mention the inclusion of the
                  <code>&lt;revisionDesc&gt;</code> element and the <code>&lt;change&gt;</code>
               tags. These tags document major changes made to the files, when these occurred, and
               who was responsible for the changes. By incorporating this information in the
                  <code>&lt;teiHeader&gt;</code>, DAP takes measures to ensure documented versioning
               of its data. The data stages pertaining to the first two major changes (“Digital
               creation of XML file” and “Restructured to meet TEI P5 standards”<note xml:id="ftn15">
                  The changes are consistent across all XML
                  files. Compare with GitHub Repository: <ref
                     target="https://github.com/DigitalAustinPapers/AustinTranscripts"
                     >https://github.com/DigitalAustinPapers/AustinTranscripts</ref>. </note>) can
               be compared in the project’s GitLab repository, in the folders ‘source_xml’ and
               ‘teip5_xml’.</p>
         </div>
         <div xml:id="div4">
            <head>Documentation</head>
            <p xml:id="p24">DAP’s documentation is primarily located on the ‘About’ page of the
               website. The informative text is divided into eleven sections: <ref
                  target="https://digitalaustinpapers.org/about#overview">Overview</ref>, <ref
                  target="https://digitalaustinpapers.org/about#manuscript-print">Austin Papers in
                  Manuscript and Print</ref>, <ref
                  target="https://digitalaustinpapers.org/about#creating">Creating the Digital
                  Edition</ref>, <ref
                  target="https://digitalaustinpapers.org/about#transcription-markup">Transcription
                  and Markup</ref>, <ref target="https://digitalaustinpapers.org/about#tei-xml">TEI
                  and XML</ref>, <ref
                  target="https://digitalaustinpapers.org/about#data-transformations">Data
                  Transformations for the Online Browse and Search Interfaces</ref>, <ref
                  target="https://digitalaustinpapers.org/about#browsing-interface">DAP Browsing
                  Interface</ref>, <ref
                  target="https://digitalaustinpapers.org/about#search-interface">DAP Search
                  Interface</ref>, <ref
                  target="https://digitalaustinpapers.org/about#sentiment-analysis">Sentiment
                  Analysis</ref>, <ref
                  target="https://digitalaustinpapers.org/about#future-development">Future
                  Development of DAP</ref>, and <ref
                  target="https://digitalaustinpapers.org/about#copyright">Copyright</ref>. Each
               section gives a concise description of the relevant aspects of the project and
               provides external links to repositories or secondary literature when applicable.
               Overall, the documentation is well executed.</p>
            <p xml:id="p25">The more technical aspects of the digital edition<note xml:id="ftn16">
                  Here I refer to sections such as ‘Data
                  Transformation’ or ‘Sentiment Analysis’.</note> are recorded in a way that can be
               easily understood, making it accessible to all users regardless of their technical
               proficiencies. Personally, as someone more familiar with the coding and technical
               aspects of digital scholarly editions, I find that there are one or two occasions
               where I wish the documentation had gone into greater detail. One example is the
               inclusion of links to the GitHub repository of the open-source ruby sentiment
               analysis libraries used in the testing process. </p>
            <p xml:id="p26">Historical context for the edition is provided in abbreviated form on
               the homepage and in slightly more detail on the ‘About’ page. Overall, the contextual
               information is only sufficient for users with prior knowledge of the time period and
               the key figures portrayed. To ensure a better understanding and appreciation for
               DAP’s subject matter, the editors may consider adding a new page dedicated to the
               historical context of the project. Similarly, a DAP-specific bibliography with
               project-relevant sources would be a useful addition, if developments on the project
               recommence.</p>
         </div>
         <div xml:id="div5">
            <head>Licensing and Citations</head>
            <p xml:id="p27">The DAP is licensed under a Creative Commons Attribution-ShareAlike 3.0
               Unported License.<note xml:id="ftn17">For more details see
                  <ref
                     target="https://web.archive.org/web/20230311010802/https:/creativecommons.org/licenses/by-sa/3.0/"
                     >https://web.archive.org/web/20230311010802/https://creativecommons.org/licenses/by-sa/3.0/</ref>.
               </note> This information is easily found under ‘Copyright’ on the ‘About’ page.
               Alternatively, a detailed Apache License text is available in the project’s GitHub
               ‘Digital Austin Site’ repository.<note xml:id="ftn18">
                  See <ref
                     target="https://github.com/DigitalAustinPapers/DigitalAustinSite"
                     >https://github.com/DigitalAustinPapers/DigitalAustinSite</ref>. </note>
               Without reopening the discussion of which licence is most suitable for a digital
               scholarly edition, the chosen licensing permits free access to reuse and adapt the
               project data. In the age of open access and linked open data, this is a welcome sight
               to all researchers. Regarding DAP’s citability, some things are left to be desired.
               Neither the digital edition as a whole nor the individual letters in the corpus offer
               a citation suggestion or permalink. Although a convenient addition to any edition,
               this can be excused if all relevant citation information is found easily on the
                  website.<note xml:id="ftn19">
                  See <ref type="crossref" target="#bleier2021"
                     >Bleier 2021</ref> for more details on how to cite a digital edition.</note>
               Unfortunately, this is only partially true for DAP. The digital edition does a
               commendable job of recognising its contributors, and listing the names and roles of
               the editorial and technical staff (both on the website and in the XML files).<note
                  xml:id="ftn20">
                  Compare with the ‘About’ page: <ref
                     target="https://web.archive.org/web/20231205064022/https:/digitalaustinpapers.org/about"
                     >https://web.archive.org/web/20231205064022/https://digitalaustinpapers.org/about</ref>.
               </note> The developing institutions and project partners are also clearly named in
               the website footer. Unfortunately, the date of publication, or alternatively the
               general runtime of the project, appears to be missing. I recommend amending this data
               point as soon as possible.</p>
            <p xml:id="p28">Despite this minor criticism, the digital edition does a thorough job of
               ensuring users know how and to what extent their materials are reusable. Combined
               with the two XML download options available to users (direct download of single files
               or in bulk from the GitHub repository AustinTranscripts), DAP lays the foundation for
               transparency of the research process and enables access to data for futher
               research.</p>
         </div>
         <div xml:id="div6">
            <head>Data Exploration</head>
            <p xml:id="p29">The area in which DAP particularly excels is offering its users many
               different views on the documents. Subdivided into browsing and search
               functionalities, both approaches are accessible through the navigation bar and the
               counters provided on the home page of the digital edition. </p>
            <div xml:id="div6.1">
               <head>Browsing</head>
               <p xml:id="p30">
                  <figure xml:id="img3">
                     <graphic
                        url="http://ride.i-d-e.de/wp-content/uploads/issue_17/austin-papers/pictures/picture-3.png"/>
                     <head type="legend">Browsing page set to authors.</head>
                  </figure>The browsing interface offers users the choice between browsing the
                  corpus by date, author, recipients, geographical origins, and destinations of the
                  documents. Once a browsing option is selected, the users are presented with a list
                  of all the matched letters; for example, all the authors of the documents, as
                  shown in <ref type="crossref" target="#abb3">figure 3</ref>. A useful feature is
                  the alphabetic letter selection offered for correspondents and places. This allows
                  users to jump ahead in the results list to the names starting with the selected
                  letter.</p>
               <p xml:id="p31">A noteworthy programming choice is how documents with two or more
                  authors (or recipients) are presented in the browsing results. As can be seen in
                     <ref type="crossref" target="#abb3">figure 3</ref>, these letters are listed
                  under a collective header consisting of all names rather than being placed under
                  the individuals’ entry. This presumably stems from the process by which the names
                  and correlating documents are collected.<note xml:id="ftn21">
                     Recipients/ authors were collected in a
                     list with the correlating xml:ids of the documents. For more details, compare
                     the ‘About’ page.</note> An author’s list of correspondences does not
                  necessarily include all the letters which can be associated with that person.
                  Their co-authored or co-received letters are found in separate lists. A combined
                  list would give users a better understanding and overview of the correspondences
                  in which every person was involved in. Furthermore, given that no registers were
                  used for this project, it is unclear how identical names for different people (if
                  at all present) were handled. </p>
            </div>
            <div xml:id="div6.2">
               <head>Search</head>
               <p xml:id="p32">
                  <figure xml:id="img4">
                     <graphic
                        url="http://ride.i-d-e.de/wp-content/uploads/issue_17/austin-papers/pictures/picture-4.png"/>
                     <head type="legend">Search options and results list.</head>
                  </figure>In contrast to the browsing page with its standard variety of options,
                  the search functionality diverges from the norm. Users are offered the choice
                  between a full-text search, pre-set authors, recipients, dates, locations, and
                  sentiment scores, or a combination of these (depicted in <ref type="crossref"
                     target="#abb4">figure 4</ref>). The filters provided in the drop-downs are full
                  lists of the correspondents etc. found in the dataset. Unfortunately, the contents
                  of the drop-downs are not reactive to each other. The individual filter options
                  are not updated to ensure results when combined. This makes data exploration via
                  the ‘Search’ somewhat tricky.</p>
               <p xml:id="p33">The sentiment-based search is a unique characteristic of DAP.
                  Although letters often act as the corpus in sentiment analysis projects,<note
                     xml:id="ftn22">
                     Some examples include Svevo Letters
                     Analysis (<ref target="https://github.com/gsarti/svevo-letters-analysis"
                        >https://github.com/gsarti/svevo-letters-analysis</ref>), “Digitally Mapping
                     Cicero's Networks, Letters, and Emotions” (<ref type="crossref"
                        target="#marley2018">Marley 2018</ref>), and “To Better Understand Vincent”
                        (<ref type="crossref" target="#whissell2022">Whissell 2022</ref>).</note> to
                  my knowledge, this method is not often incorporated into scholarly digital
                  editions and their web platforms. The sentiment scores in DAP were calculated
                  using <ref target="https://github.com/stiang/textmood">TextMood</ref>. Based on
                  the available documentation, I was not able to discern whether a project-specific
                  dictionary was used.</p>
               <p xml:id="p34">Once a search is initiated, the results can be explored through four
                  different views/methods. The first and initial viewer is a general list of
                  results. As shown in <ref type="crossref" target="#img4">figure 4</ref>, the results can be sorted by date, relevance, and
                  sentiment scores. Each result provides the title of the letter, date, summary, and
                  sentiment score. The sentiment score is given as ‘positive’, ‘negative’, or
                  ‘neutral’, with a specific score appearing when hovering over the question mark
                  icon. These scores are an approximation of the overall emotion projected in the
                  text and should be treated as such. Emotions are very subjective, and in some
                  cases, the assigned scores are not self-evident when reading the letter.<note
                     xml:id="ftn23">
                     For example, <ref
                        target="https://web.archive.org/web/20231030171753/https:/digitalaustinpapers.org/document?id=APB0001.xml"
                        >Maria Austin’s letter to her husband Moses Austin on the 24th of August
                        1789</ref> has a neutral sentiment score of -0.65. In contrast, her <ref
                        target="https://web.archive.org/web/20231215085736/https:/digitalaustinpapers.org/document?id=APB0220.xml"
                        >letter from the 23rd of June 1812</ref> with a positive score of 5. Both
                     letters contain affectionate language addressed to her husband and family, as
                     well as negative language when she voices concerns or relates bad news. As a
                     reader, I would assume the sentiment scores to be closer to one another.
                     Readers should not solely rely on the sentiment scores provided when searching
                     for letters. When looking for ‘positive’ letters, it may be advisable to
                     include letters from the higher ‘neutral’ range (the neutral score range in DAP
                     is -2 to 2) in the search pool. </note>
               </p>
               <p xml:id="p35">
                  <figure xml:id="img5">
                     <graphic
                        url="http://ride.i-d-e.de/wp-content/uploads/issue_17/austin-papers/pictures/picture-5.png"/>
                     <head type="legend">Histogram showing the distribution of documents and
                        sentiments over time.</head>
                  </figure>Next is the ‘Timeline/Sentiment’ viewer depicted in <ref type="crossref"
                     target="#abb5">figure 5</ref>. In this viewer, users can consult one of two
                  histograms showing:<list rend="bulleted">
                     <item>the number of documents found per year.</item>
                     <item>the proportion of search results in a given year compared to the total of
                        all documents. </item>
                  </list>
               </p>
               <p xml:id="p36">The documents per year are grouped by sentiment (positive, neutral,
                  negative). Clicking on a particular sentiment grouping within the histogram
                  results in a new search with the parameters year and sentiment preselected. This
                  form of data visualisation is a great way to gain a better overview of the
                  distribution of the data, both in terms of the temporal distribution and the
                  grouping of sentiments across time. Combining these two aspects is particularly
                  interesting within the context of DAP and its subject matter. As mentioned
                  previously, the documents cover a time of great change in Texas and the
                  surrounding areas. The histogram helps visualise if and when the political and
                  social changes are reflected in the emotions expressed in the letters. Be this in
                  personal letters or official documents.</p>
               <p xml:id="p37">Given that the search methods discussed up until now both incorporate
                  sentiment scores in their presentation, I would like to point out a few
                  observations. As discussed in the documentation section of this review, the
                  overall methodology for calculating the sentiment scores is well documented. In
                  terms of re-usability, however, it is disappointing that the sentiment scores per
                  document are not provided in the GitHub repository or the TEI header section of
                  the individual XML files. These results can be valuable for other projects. They
                  could be used as a part of a research project or as a comparison/guide for other
                  digital editions aiming to incorporate sentiments in their tool. </p>
               <p xml:id="p38">
                  <figure xml:id="img6">
                     <graphic
                        url="http://ride.i-d-e.de/wp-content/uploads/issue_17/austin-papers/pictures/picture-6.png"/>
                     <head type="legend">Mapping of letters with coloured arcs connecting the origin
                        and destination.</head>
                  </figure>The third viewer is the geographical mapping of origins and destinations. Once again, providing a visual representation of the data is
                  a very welcome sight. Letters in particular are well suited for mapping as they
                  generally contain geographical information that is easy to process. As seen in
                     <ref type="crossref" target="#abb6">figure 6</ref>, the plotted locations
                  provide information on how many letters were sent to and from each location.
                  Clicking on a location marker results in a new search with the location
                  preselected. Users can draw some interesting insights from this particular
                  visualisation, including the direction in which letters were sent between places.
                  Through the dominance of colour (red for origin, blue for destination), users can
                  also deduce whether a location mainly acted as the origin or destination of
                  letters. </p>
               <p xml:id="p39">
                  <figure xml:id="img7">
                     <graphic
                        url="http://ride.i-d-e.de/wp-content/uploads/issue_17/austin-papers/pictures/picture-7.png"/>
                     <head type="legend">Zoomed in results from figure 6.</head>
                  </figure>One improvement suggestion from a usability standpoint would be to
                  integrate a note informing users that further location markers will become visible
                  upon zooming into the map. As shown in figures <ref type="crossref" target="#abb6"
                     >6</ref> and <ref type="crossref" target="#abb7">7</ref>, only a handful of
                  places are initially plotted on the map when the viewer is opened. The remaining
                  location markers only become visible by zooming in. This is not very intuitive and
                  can lead to false interpretations of the results. A simple note can rectify this
                  issue.</p>
               <p xml:id="p40">The fourth and final viewer is the word count. I have yet to come
                  across another edition that provides a word count per search results. Therefore,
                  this final viewer is a good example of how DAP strives to provide new methods of
                  exploration. </p>
               <p xml:id="p41">
                  <figure xml:id="img8">
                     <graphic
                        url="http://ride.i-d-e.de/wp-content/uploads/issue_17/austin-papers/pictures/picture-8.png"/>
                     <head type="legend">Word count viewer of search results.</head>
                  </figure>Three sets of 50 ‘words’ are provided per letter result: most common
                  words, named persons, and named places. Each word gives the total number of
                  occurrences in the collection. Taking a closer look at <ref type="crossref"
                     target="#abb8">figure 8</ref>, two observations in particular can be made about
                  the ‘word count’ viewer. The first is that the mentioned people and places seem to
                  give reliable results. This is likely because the tagged names were extracted
                  directly from the TEI/XML and did not require further processing to remove stop
                  words etc. There are, however, some names that are not as useful. Some examples
                  include ‘brother’, ‘river’ or ‘man’. This is where indices and person/place IDs
                  would be useful. The word count could then group different versions of a name
                  through common IDs, at least in theory. However, even with this method, there will
                  always be unknown references, which begs the question of whether the (possibly)
                  improved results would justify the added effort.</p>
               <p xml:id="p42">The second observation is that the overall word count occasionally
                  returns single numbers and letters as results. In lieu of documentation, I can
                  only speculate what the cause may be. Stop words such as ‘a’, ‘and’, ’the’ seem to
                  be excluded from the word list. After testing different search combinations, I
                  have found that the results seem to improve with a greater number of letters in
                  the results collection. </p>
               <p xml:id="p43">Despite this, the word count view is an interesting addition to the
                  digital edition. Similar to the mapping, and timeline/sentiment viewer, the word
                  count provides a new perspective on the collection. The results can provide users
                  with a first impression of the topics handled in the documents, and help identify
                  important persons/places based on the number of overall mentions. </p>
            </div>
         </div>
         <div xml:id="div7">
            <head>DAP and the FAIR Principles</head>
            <p xml:id="p44">DAP covers various aspects of a digital edition following the FAIR
               principles, but some areas can be improved on.</p>
            <p xml:id="p45">Finding the edition for first-time visitors may be tricky, as it is not
               registered in well-known catalogues such as the “<ref
                  target="https://web.archive.org/web/20240218141740/https:/dig-ed-cat.acdh.oeaw.ac.at/"
                  >Catalogue of Digital Editions</ref>” and “<ref
                  target="https://www.digitale-edition.de/">a catalogue of: Digital Scholarly
                  Editions</ref>”. DAP is, however, the first result found in a regular search
               engine. Once on the platform, researchers have full access to the collected and
               processed data. The documents can be explored using the website interface or
               downloaded individually as TEI/XML files. Alternatively, users can access the web
               code and data through the project’s GitHub repository. This is a recommendable aspect
               of DAP as it is open access and offers researchers another place to find the
               project’s research data. To further improve the findability of the data DAP could
               consider publishing its data in subject-relevant repositories, if available. Doing
               this would place the project in context with similar editions and make it visible to
               a wider audience. The materials are easily accessible and available for re-use under
               a CC-BY-SA 3.0 licence. DAP does not provide an API to permit automatic queries of
               the data.</p>
            <p xml:id="p46">The brief but concise documentation provides information on all of the
               steps involved in the development of DAP, as well as the reasoning behind them. This
               allows users to gain a full understanding of the source material and the processing
               involved. Major changes made to the TEI/XML are recorded in the
                  <code>&lt;teiHeader&gt;</code> of the files, along with the individuals
               involved.</p>
            <p xml:id="p47">DAP adheres to the norm in terms of the data format. Its documents
               follow the TEI-standard; the precise version and schema used for validation are
               recorded and easy to find. A project-specific schema was not used, which is
               understandable given the comparatively low level of data tagging. Nevertheless, the
               lack thereof can affect the reusability and interoperability of the research
               data.</p>
            <p xml:id="p48">The same applies to the data modelling, which leaves room for
               improvement. Project-relevant aspects were included in the data model, such as
               mentioned people and places, and the creation/destination locations of the documents.
               Unfortunately, these data points were not assigned project-specific IDs or Authority
               File IDs. Including these would improve certain aspects of the data, such as better
               facilitating its integration into- or cross-referencing with external sources.</p>
         </div>
         <div xml:id="div8">
            <head>Conclusion</head>
            <p xml:id="p49">
               <emph>Digital Austin Papers</emph> offers researchers a platform to search through
               and access Stephen F. Austin’s vast collection of correspondence from the 1820s and
               1830s. The edition aims to test and provide new ways to explore its material,
               revealing new patterns hidden within. The project’s ‘Browsing’ page offers users the
               standard array of filter options: correspondents, location, and date. The ‘Search’,
               on the other hand, is where DAP sets itself apart. It demonstrates how different
               approaches and methods can be integrated into a digital edition to reveal new
               perspectives on the data. An example of this is the inclusion of sentiment analysis.
               This method is interesting given the historical climate in which the correspondences
               were written. When combined with time as a factor, this functionality can reflect
               emotional changes during a time when society and politics were in flux.</p>
            <p xml:id="p50">The subject material is accessible on the DAP website and in the
               project’s GitHub repository, where the TEI/XML files are available for reuse under a
               CC-BY-SA 3.0 licence. The project’s documentation explicitly encourages this.
               Overall, DAP briefly addresses all the different aspects of the edition, explaining
               certain decisions made in the development process. For example, DAP clarifies why
               they chose to unitise the Barker edition for its transcriptions.</p>
            <p xml:id="p51">The materials handled in DAP are valuable resources for scholars
               interested in the Texas area during the early 19th century. The documents hold
               first-hand accounts and reactions to the historical events leading to the Texas
               Revolution. For this reason, DAP has the potential to provide its researchers with
               more in-depth access to the materials than currently provided. The data modelling is
               relatively simple, covering core aspects such as mentioned people and places.
               Addressing other aspects of the text, for example, mentioned organisations and
               discussed topics would offer additional entry points into the corpus. Providing more
               historical context would also give researchers a better framework by which they can
               explore DAP’s historically rich materials.</p>
            <p xml:id="p52">Overall, I find that <emph>Digital Austin Papers</emph> succeeded in its
               aims and brought forth a valuable and interesting digital scholarly edition. It also
               has the potential to improve its offer, in terms of both the volume and quality of
               data.</p>
         </div>
      </body>
      <back>
         <div type="bibliography">
            <listBibl>
               <bibl xml:id="barker2021">Barker, Eugene C. 2021. “Austin, Stephen Fuller.”
                     <emph>Handbook of Texas Online</emph>. <ref
                     target="https://web.archive.org/web/20230311192159/https://www.tshaonline.org/handbook/entries/austin-stephen-fuller"
                     >https://web.archive.org/web/20230311192159/https://www.tshaonline.org/handbook/entries/austin-stephen-fuller</ref>.</bibl>
               <bibl xml:id="bleier2021">Bleier, Roman. 2021. “How to Cite This Digital Edition?”
                     <emph>Digital Humanities Quarterly</emph> 15 (3). <ref
                     target="https://web.archive.org/web/20230419101557/http:/www.digitalhumanities.org/dhq/vol/15/3/000561/000561.html"
                     >https://web.archive.org/web/20230419101557/http:/www.digitalhumanities.org/dhq/vol/15/3/000561/000561.html</ref>. </bibl>
               <bibl xml:id="brands2019">Brands, Henry W. 2019. “When Mexico’s Immigration Troubles
                  Came From Americans Crossing the Border.” Smithsonian Magazine. <ref
                     target="https://web.archive.org/web/20231211104502/https:/www.smithsonianmag.com/history/americans-illegally-immigrated-mexico-180973306/"
                     >https://web.archive.org/web/20231211104502/https://www.smithsonianmag.com/history/americans-illegally-immigrated-mexico-180973306/</ref>.</bibl>
               <bibl xml:id="britannica2023">Britannica, The Editors of Encyclopaedia. 2023. “Daniel
                  Boone.” <emph>Encyclopedia Britannica.</emph>
                  <ref
                     target="https://web.archive.org/web/20231211101528/https:/www.britannica.com/biography/Daniel-Boone"
                     >https://web.archive.org/web/20231211101528/https:/www.britannica.com/biography/Daniel-Boone</ref>.</bibl>
               <bibl xml:id="cummins2019">Cummins, Light T. 2019. <emph>To the Vast and Beautiful
                     Land: Anglo Migration into Spanish Louisiana and Texas, 1760s–1820s</emph>
                  (First edition.). College Station: Texas A&amp;M University Press.</bibl>
               <bibl xml:id="austin2016a">Digital Austin Papers. 2016a. “About the Project.” <ref
                     target="https://web.archive.org/web/20231205064022/https:/digitalaustinpapers.org/about"
                     >https://web.archive.org/web/20231205064022/https://digitalaustinpapers.org/about</ref>.</bibl>
               <bibl xml:id="austin2016b">Digital Austin Papers. 2016b. Developed by the University
                  of North Texas and The Portal to Texas History. <ref
                     target="https://web.archive.org/web/20231211083736/https:/digitalaustinpapers.org/index"
                     >https://web.archive.org/web/20231211083736/https://digitalaustinpapers.org/index</ref>.</bibl>
               <bibl xml:id="department">“Department of History.” N.d. University of North Texas.
                     <ref
                     target="https://web.archive.org/web/20230312094827/https:/history.unt.edu/"
                     >https://web.archive.org/web/20230312094827/https://history.unt.edu/</ref>.</bibl>
               <bibl xml:id="portal">“The Portal to Texas History”. 2023. <ref
                     target="https://web.archive.org/web/20230311192516/https:/texashistory.unt.edu/"
                     >https://web.archive.org/web/20230311192516/https://texashistory.unt.edu/</ref>.</bibl>
               <bibl xml:id="humphrey2023">Humphrey, David C. 2023. “Austin, TX (Travis County)”.
                     <emph>Handbook of Texas Online</emph>. <ref
                     target="https://web.archive.org/web/20231024010546/https://www.tshaonline.org/handbook/entries/austin-tx-travis-county"
                     >https://web.archive.org/web/20231024010546/https://www.tshaonline.org/handbook/entries/austin-tx-travis-county</ref>.</bibl>
               <bibl xml:id="franzinietal2018">Franzini, Greta, Peter Andorfer, and Ksenia Zaytseva.
                  2018. “Catalogue of Digital Editions: The Web Application.” DOI: <ref
                     target="https://doi.org/10.5281/zenodo.1250797"
                  >10.5281/zenodo.1250797</ref>.</bibl>
               <bibl xml:id="marley2018">Marley, Caitlin. 2018. “Digitally Mapping Cicero’s
                  Networks, Letters, and Emotions.” <emph>Society for Classical Studies</emph>
                  (blog). <ref
                     target="https://web.archive.org/web/20230312105243/https:/classicalstudies.org/scs-blog/caitlin-marley/blog-digitally-mapping-ciceros-networks-letters-and-emotions"
                     >https://web.archive.org/web/20230312105243/https://classicalstudies.org/scs-blog/caitlin-marley/blog-digitally-mapping-ciceros-networks-letters-and-emotions</ref>.</bibl>
               <bibl xml:id="moses">“Moses and Stephen F. Austin Papers.” <emph>The Portal to Texas
                     History. University of North Texas Libraries</emph>. <ref
                     target="https://web.archive.org/web/20230312100106/https://texashistory.unt.edu/explore/collections/AUSTIN/"
                     >https://web.archive.org/web/20230312100106/https://texashistory.unt.edu/explore/collections/AUSTIN/</ref>. </bibl>
               <bibl xml:id="sahle2022">Sahle, Patrick et. al. 2020ff. “A Catalog of Digital
                  Scholarly Editions.” <ref target="https://www.digitale-edition.de/"
                     >https://www.digitale-edition.de</ref>. </bibl>
               <bibl xml:id="taylor2015">Taylor, Lonn. 2015. “Father Figure: How Stephen F. Austin
                  Wanted to Be Seen.” <emph>Texas Monthly</emph>. <ref
                     target="https://web.archive.org/web/20231211095912/https:/www.texasmonthly.com/the-culture/father-figure/"
                     >https://web.archive.org/web/20231211095912/https://www.texasmonthly.com/the-culture/father-figure/</ref>.</bibl>
               <bibl xml:id="texaslibrary2017">Texas State Library and Archives Commission. 2017.
                  “Giants of Texas History: Stephen F. Austin.” <ref
                     target="https://web.archive.org/web/20231211101906/https://www.tsl.texas.gov/treasures/giants/austin/austin-01.html"
                     >https://web.archive.org/web/20231211101906/https://www.tsl.texas.gov/treasures/giants/austin/austin-01.html</ref>.</bibl>
               <bibl xml:id="turner1906">Turner, Frederick J. 1906. “The Colonization of the West,
                  1820–1830.” <emph>The American Historical Review </emph>11 (2): 303–27. DOI: <ref
                     target="https://doi.org/10.2307/1834646">10.2307/1834646</ref>. </bibl>
               <bibl xml:id="whissell2022">Whissell, Cynthia. 2022. “To Better Understand Vincent: A
                  Study of The Emotional Tone of Vincent Van Gogh’s Letters to His Brother Theo,
                  1872–1890.” <emph>International Journal on Studies in English Language and
                     Literature</emph> 10 (10): 37–53. DOI: <ref
                     target="http://dx.doi.org/10.20431/2347-3134.1010005"
                     >10.20431/2347-3134.1010005</ref>. </bibl>
            </listBibl>
         </div>
      </back>
   </text>
</TEI>