Outline for TEI Publisher Workshop

100%

Outline for TEI Publisher Workshop

✓ Published0🌍 Public

Last edited May 3, 2019

Created on Apr 30, 2019

This outline introduces TEI Publisher, a tool for publishing TEI-encoded texts, using examples such as Early English Books Online and Shakespeare’s plays. It covers installation via Docker, customization through ODDs with references to the TEI Element Model and a Baudelaire corpus, and view adjustments using Syriaca Gazetteer data. The document also addresses deployment on Digital Ocean. Concrete resources include Docker, eXist-db, and GitHub repositories, but no code libraries or APIs are referenced.

AI-generated description

Similar vizzes

Loading thumbnail…

For Arne

This example visualizes the structure of a single TEI-encoded article by extracting metadata from an XML source and rendering it as a document-tree diagram. It shows the hierarchical relationships between the article’s title, author, issue, and page-range fields, emphasizing how the original bibliographic data maps onto the TEI structure. The visualization uses an XQuery script with XPath queries to pull specific values, such as the issue and article numbers via regular-expression replacement, and the starting/ending pages from the `biblScope`. The rendering then relies on a force-directed layout (via `d3.forceSimulation`) to position nodes, with each node representing a TEI element and links showing parent–child dependencies. The data source is the gist’s embedded TEI file, and the output is a static SVG generated client-side, reflecting the parsed metadata without additional interaction.

CCliffordAnderson

60% match

Loading thumbnail…

<title>TITLE

This example demonstrates a minimal TEI document structure that validates against a custom ODD schema, defining required elements and attributes for book and chapter divisions. The visualization shows the relationship between the ODD specification and the sample instance, with the schema enforcing structural rules like the presence of a `<head>` in each `<div>` and a non-generic document title. The code uses the TEI and Schematron namespaces to declare constraints, while the sample TEI file references the Relax NG schema via `xml-model` processing instructions. The rendering approach highlights the schema’s closed value lists for `type` attributes and the required `xml:id` usage, demonstrating how validation rules shape document structure.

CCliffordAnderson

58% match

Loading thumbnail…

XQuery Blue Mountain Project - Part III

This example shows a pipeline for transforming a single TEI XML document from the Blue Mountain Project—a digitized 1920 issue of the French journal *Action*—into clean, article-level TEI files. The first script removes facsimile elements, end-hyphenation markers, and line breaks, replacing `<lb>` elements with spaces. A second script extracts metadata and article content into a fresh TEI template, while a third builds individual TEI files for each article. The code uses XQuery 3.1 with the `fn:doc` API for document access and node operations like `copy`, `modify`, and `replace node`.

CCliffordAnderson

57% match

Loading thumbnail…

Prompt for marking up TEI P5

This example demonstrates a prompt-driven workflow for converting raw historical text into TEI P5 XML with named entity markup. It shows how the system identifies personal names, queries Wikidata for matching entities, and assigns attributes like @ref, @full, and @cert for disambiguated references. The process relies on the Wikidata API for entity resolution and uses TEI's controlled vocabulary for confidence levels. The output is a self-contained XML fragment, with unidentifiable names marked as unknown. This approach highlights the integration of external linked-data sources into scholarly text encoding, emphasizing automated authority control and metadata enrichment.

CCliffordAnderson

57% match

Loading thumbnail…

<title>{$info[1]}

This example demonstrates a metadata transformation from TEI to MODS, converting bibliographic details from an XML source document. The code uses XQuery 3.0 with custom functions `local:gather-information` and `local:generate-mods` to extract fields like title, author, language, publication info, and abstract from the TEI file, then constructs a MODS record and stores it via `xmldb:store`. The visualization shows how structured metadata can be programmatically reshaped between standards, relying on XPath queries and namespace declarations to map data accurately.

CCliffordAnderson

56% match

Loading thumbnail…

Blue Mountain Project - Dividing Up Languages

This example shows how XQuery processes TEI-encoded periodical documents from the Blue Mountain Project, splitting them into individual articles for database storage. The code traverses document collections with `fn:collection` and `fn:doc`, prunes unwanted elements and attributes using the `copy`/`modify` XQuery Update Facility, and reconstructs TEI structures. It uses the `db:create` function from the eXist-db API to build a new database collection from the transformed articles, demonstrating a pipeline for dividing source documents into discrete, queryable units.

CCliffordAnderson

55% match

Loading thumbnail…

Render module for search namespace

This example shows how TEI-encoded play texts can be rendered into a formatted HTML view, using the `render:render` and `render:recurse` functions to map XML elements like `tei:head`, `tei:speaker`, and `tei:stage` to headings, bold labels, and paragraphs. It relies on XQuery’s `typeswitch` and recursion to process the document tree, while the `render:titles` function generates a hyperlinked table of contents from a list of play elements. The code directly uses the XQuery 3.0 module system and the `declare function` syntax, with no external JavaScript libraries.

CCliffordAnderson

55% match

Loading thumbnail…

<title>{$title}

This example shows a data transformation that converts TEI-encoded metadata into MODS format, preserving bibliographic details such as title, author, language, publication origin, and abstract. The XQuery script, running on the eXist-db platform, uses the `fn:doc` function to read an XML file and XPath expressions to extract specific elements like `tei:titleStmt` and `tei:publicationStmt`. It then constructs a MODS record by mapping these values into the appropriate MODS elements, such as `<titleInfo>` and `<originInfo>`. The code relies on the standard XQuery 3.0 language features, with no external libraries or visualization APIs involved.

CCliffordAnderson

55% match