Query across collections in ExistDB

100%

Query across collections in ExistDB

✓ Published0🌍 Public

Last edited Dec 22, 2013

Created on Dec 22, 2013

This example shows how a single XQuery query can aggregate and expose metadata from multiple Shakespearean text collections stored in an eXist-db database. The query uses the `fn:collection()` function to traverse the `db/shakespeare` path, selecting all `tei:seriesStmt` elements from the TEI namespace, which describe series-level publication information. The visualization renders the resulting XML as a structured graph, with nodes and edges built from the query output using D3.js’s `d3.forceSimulation` for layout. The concrete approach relies on eXist-db’s native XQuery engine to fetch and return the TEI data, which is then parsed and bound to visual elements, demonstrating a direct pipeline from database query to interactive graphic.

AI-generated description

Similar vizzes

Loading thumbnail…

Exploring your Collection

This visualization shows a collection of TEI-encoded texts by querying their titles and full-text content, highlighting matches for terms like “vin” or co-occurring words like “mal” and “je” within the same sentence. It first demonstrates how to list all titles in the collection, then filters those titles using XQuery Full-Text expressions via the `contains text` operator. The code uses the BaseX or eXist-db XQuery 3.0 engine, leveraging the `fn:collection()` function to access documents and the TEI namespace for element traversal, with no external visualization libraries—the output is plain text.

CCliffordAnderson

76% match

Loading thumbnail…

A simple Shakespeare search tool in eXist-db

This example shows a simple full-text search interface for Shakespeare’s plays, returning matching lines from a TEI-encoded corpus. The page uses an XQuery script that queries an eXist-db database via the `ft:query` function, which performs full-text search on `<tei:l>` elements. A plain HTML form submits a query parameter, and the results are rendered as `<p>` elements. The code relies on eXist-db’s request and collection APIs, along with the `output` serialization options for HTML5, but does not use any client-side JavaScript libraries or advanced rendering techniques.

CCliffordAnderson

73% 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

64% match

Loading thumbnail…

XQuery Samples for Blue Mountain Project

This example shows a sequence of XQuery scripts that analyze the language metadata of TEI-encoded journals from the Blue Mountain Project, a digital archive of avant-garde publications. The scripts query a collection called `bluemountain-transcriptions` using the `fn:collection` function, counting documents, extracting distinct languages from `tei:langUsage`, and identifying journals with multiple `tei:textLang/@mainLang` attributes. Later scripts partition documents by language, using `db:create` to store French texts in a new database, and verify the results by listing the URIs of the partitioned files. The code relies on the XQuery 3.1 standard and the eXist-db database API for collection access and database creation.

CCliffordAnderson

64% 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

63% match

Loading thumbnail…

This example of recursive descent in XQuery is adapted from Joe Wicentowski (https://gist.github.com/joewiz/2331558#file-typeswitch-skeleton-xq). It rather naively formats scenes from the Folger Library Shakespeare TEI editions for display in HTML. This example is intended for the demonstration of the concept, not actual use.

This example shows recursive descent in XQuery rendering scenes from a Folger Library Shakespeare TEI edition into HTML. It demonstrates how a typeswitch pattern matches distinct TEI elements—such as `tei:head`, `tei:w`, `tei:stage`, and `tei:speaker`—to produce formatted output like headings, stage directions, and speaker labels. The code relies on XQuery 3.0’s built-in `typeswitch` and function recursion, using `local:render` and `local:recurse` to traverse the XML tree. It serializes to XHTML via `exist:serialize`, pulling the source document from `/db/shakespeare/JC.xml` without external libraries.

CCliffordAnderson

63% 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

61% match

Loading thumbnail…

Query for long and short phrases in Shakespeare's plays

This visualization shows the distribution of long versus short phrases in Shakespeare’s plays, counting how many phrases exceed twenty characters. A bar-like layout compares the two categories, making the frequency difference immediately visible. The code uses XQuery 3.0 with the `fn:collection` and `tei:ab` functions to access and iterate over TEI-annotated text blocks, applying `fn:string-length` to classify each phrase. It groups results by length category using the `group by` clause, then dynamically constructs an element named `long-phrase` or `short-phrase` with the corresponding count, rendering the final output as XML.

CCliffordAnderson

60% match