Digitizing Medieval Archives
  • Introduction
  • Overview of the Course
  • Assignments
  • Lead a seminar
  • Readings
  • Week 1 & 2 - Setting Up
    • Signing Up
    • Using Twitter
    • Twitter Strategies
    • Twitter Abbreviations
  • Week 3 - Omeka
    • Dublin Core
  • Week 4 - Github
    • Markdown
    • Github
    • Turning Github into a website
    • Markdown II (Optional)
  • Week 5 - Writing Supports
    • Your first transcription
    • Getting prepared for Transkribus
  • Week 6 - Palæography
    • Distinguishing Late Medieval Scripts
    • Handwriting Analysis Tools
    • Installing Medieval Unicode
    • IRL Abbreviations
  • Week 7 - Abbreviations
    • Transcribing with Transkribus
    • Transcribing
    • Java 8
  • Week 8 - Codicology
    • Codicological Spreadsheet
  • Week 9 - Liturgical Genres
    • Medieval Liturgy - Basic Bibliography
  • Week 10 - Cataloguing
    • Template for Folio Cataloguing
  • Week 11 - Workday
  • Week 12 - Whetting your Digital Appetite
  • Week 13 - The Theory of the Digital
    • Github Project Boards
  • Week 14 - The Promise of DH
    • Criteria for Evaluating DH Projects
  • Week 15 - Capturing Manuscripts
    • How to take photos of documents
    • Image File Formats
  • Week 16 - IIIF
    • Our IIIF Images
    • Understanding IIIF Image Presentation
    • Using IIIF Manifests
  • Week 17 - IIIF Annotations
    • Annotations in Mirador
    • Annotations with Transkribus
  • Week 18 - Online Exhibits
  • Week 19 - TEI
    • Look at a TEI folio description
    • Digital Latin Library
    • TEI export from Transkribus
  • Week 20 - Accessibility and Longevity
  • Week 21 - Work
  • Week 22 - Work
  • Week 23 - Presentations I
  • Week 24 - Presentations II
  • Week 25 - End of the Line
  • About
Powered by GitBook
On this page
  1. Week 19 - TEI

Digital Latin Library

PreviousLook at a TEI folio descriptionNextTEI export from Transkribus

Last updated 6 years ago

Unlike the Fragmentarium project, the Digital Latin Library is more concerned with presenting editions than describing manuscripts. Their template thus focuses less on physical description of manuscripts, and more on the editorial apparati necessary for a modern digital critical edition, which is more closely aligned with the guide to TEI produced by .

The TEI header material is roughly similar between the DLL and the Fragmentarium project, but afterwards differs considerably. This divergence demonstrates the adaptability of the TEI coding guidelines. While our previous example was mostly <fileDesc> information, this template is mostly a <text> block:

DigitalLatin/training/template.xml
<text>
  <front xml:id="front">
  <div type="section" xml:id="preface">
<head>Preface</head>
<p>General introductory remarks about the edition.</p>
<div type="section" xml:id="preface-section-1">
 <!--
This is a subsection within the preface. Editors should use
            subsections (with <div>) to organize the content of the edition's
            preface. For example, there might be a subsection devoted to
            the description of manuscripts.
-->
</div>
</div>
<div type="section" xml:id="bibliography">
<head>Bibliography</head>
 <!--
This is where the bibliography for the edition is listed.
-->
<div type="section" xml:id="bibliography-early-editions">
<head>Early Editions</head>
 <!--
Bibliographical details for early editions or editiones vetustiores, using
            <gi>listWit</gi> with <att>type</att>="editions-witnesses".
-->
</div>
<div type="section" xml:id="bibliography-modern-editions">
<head>Modern Editions</head>
 <!--
Bibliographical details for modern editions and commentaries, using
            <gi>listBibl</gi> with <att>type</att>="editions-sources".
-->
</div>
<div type="section" xml:id="bibliography-secondary-sources">
<head>Secondary Sources</head>
 <!--
Bibliographical details for articles, notes, books, and other sources,
            using <gi>listBibl</gi> with <att>type</att>="secondary-sources".
-->
</div>
<div type="section" xml:id="bibliography-scholars">
<head>List of Scholars Referred to By Name</head>
 <!--
 A list of the names of individual scholars referred to by name in the
            apparatus, if they are not listed elsewhere in the bibliography.
-->
</div>
</div>
<div type="section" xml:id="conspectus">
<head>Conspectus</head>
 <!--
A key to the special sigla and abbreviations used in the edition (drawn
          from the <att>xml:id</att>'s assigned to the various items in the
          bibliography).
-->
</div>
</front>
<body>
<div type="edition" xml:id="edition-text" xml:space="preserve">
<div type="textpart" n="1" xml:id="part1">
<head>Title of First Part</head>
 <!--
Text goes here, according to the conventions laid out elsewhere in these guidelines.
-->
</div>
<div type="textpart" n="2" xml:id="part2">
<head>Title of Second Part</head>
 <!--
Each new major section (e.g., book, volume) has a new <div.
-->
</div>
</div>
</body>
<back>
 <!--
The content of the back matter will be determined in consultation between
        the editor and the staff of the DLL. Because LDLT editions are encoded, the
        matter traditionally found in the back of a printed critical edition may be
        generated by applications instead of having to be entered manually.
        Nevertheless, there is space here for notes, indices, and other kinds of
        information.
-->
</back>
</text>
</TEI>
Andrew Dunning