Skip to main content
SimilarExport ZIP
100%

For Arne

✓ Published0🌍 Public
CCliffordAnderson
Last edited Dec 16, 2025
Created on Dec 16, 2025

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.

AI-generated description

Similar vizzes

Loading thumbnail…

<title>Testing XPath

This example demonstrates how an XML TEI document’s structure can be queried using XPath and represented as an interactive node-link diagram. It displays the document’s hierarchical elements—such as `teiHeader`, `text`, `body`, and `p`—as circles connected by links, with text content visible alongside node labels. The visualization uses D3.js’s `d3.hierarchy` and `d3.tree` layout to calculate positions, while `d3.zoom` enables panning and zooming. The code loads the XML via a local file and parses it with `DOMParser`, then applies XPath expressions via `document.evaluate` to extract elements and text for rendering.

CCliffordAnderson
71% 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
67% 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
66% match
Loading thumbnail…

This is my example code from our classroom exercise

This example visualizes stage directions from a TEI-encoded text by associating each person with the stages they appear in. The XQuery code iterates through `//person` elements and collects matching `//stage` elements based on the `@who` attribute, outputting a structured XML list of directions per character. It relies on the TEI namespace and uses `fn:tokenize` to parse multiple ID references. The result is a plain XML document, not a graphical rendering, serving as a preprocessing step for potential downstream visualization.

CCliffordAnderson
66% match
Loading thumbnail…

Here's the query we started in class today.

This example demonstrates how to extract the title and author from a TEI-encoded XML document stored in a database. It shows the direct retrieval of text content from nested XML elements, returning both pieces of metadata as a sequence. The code uses the XQuery language with the `fn:doc()` function to access the document and XPath expressions to navigate the TEI namespace. It specifically traverses the `teiHeader/fileDesc/titleStmt` structure to pull the title and author values, illustrating a fundamental pattern for querying structured text documents in an XML database environment.

CCliffordAnderson
66% match
Loading thumbnail…

XPath Examples - Mellon Institute

This example demonstrates how XPath queries navigate and extract specific content from a TEI-encoded document of the Mellon Institute at Vanderbilt. It shows the progression from simple absolute paths to descendant-or-self axes, then to predicate-based filtering, and finally to more complex relational paths. The code uses the XPath API to select titles, names, sex attributes, and speaker-related paragraphs, referencing the updated TEI Guidelines for the sex element. The example is presented as a gist authored by CliffordAnderson, with the source data being the structured XML markup of the institute’s records, illustrating query patterns for text extraction and attribute matching.

CCliffordAnderson
65% match
Loading thumbnail…

A list of all the paths in the Folger XML edition of *Much Ado About Nothing*

This visualization displays every unique XML element path in the Folger Shakespeare Library’s TEI edition of *Much Ado About Nothing*, showing the document’s structural hierarchy as a collapsible tree. It reveals how the play’s text is organized, from the TEI header’s metadata (like editorial declarations and source descriptions) down to nested speech and stage-direction elements. The code uses D3’s `d3.forceSimulation` to layout the nodes and `d3.hierarchy` to compute parent-child relationships from the path list. The data originates from a gist containing `paths.txt`, which is parsed into a tree structure for rendering.

CCliffordAnderson
64% match
Loading thumbnail…

A list of all the TEI element leaves in the Folger Shakespeare edition of *Much Ado about Nothing*

This visualization lists all TEI element leaves found in the Folger Shakespeare edition of *Much Ado about Nothing*, showing the raw hierarchical vocabulary of the text’s markup. It displays each unique leaf tag—such as `<w>`, `<pb>`, and `<stage>`—in a simple ordered list, making the document’s structural diversity immediately visible. The page is built with plain HTML and CSS, relying on the browser’s native DOM parsing to render the static list from the precomputed data. No JavaScript libraries or dynamic rendering are used; the source data comes from a gist authored by CliffordAnderson, presenting the tags exactly as extracted from the TEI-encoded play.

CCliffordAnderson
64% match