A simple Shakespeare search tool in eXist-db

100%

A simple Shakespeare search tool in eXist-db

✓ Published0🌍 Public

Last edited Jul 11, 2016

Created on Jul 11, 2016

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.

AI-generated description

Similar vizzes

Loading thumbnail…

Query across collections in ExistDB

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.

CCliffordAnderson

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

70% match

Loading thumbnail…

XQuery Full-Text Examples

This example demonstrates XQuery Full-Text search and scoring over the TEI-encoded poems of *Les Fleurs du Mal*. It shows basic text matching with the `contains text` operator, then extends to counting results via `ft:count()`, highlighting matches with `ft:mark()`, extracting snippets with `ft:extract()`, and ranking hits by relevance using `ft:score()` with descending order. The final `search.xqy` combines scoring, marking, and base-URI display, filtering out a specific document. The code uses the XQuery 3.1 `=>` arrow operator for function chaining, and relies on the `fn:collection()` function to access the poem corpus.

CCliffordAnderson

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

66% match

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

65% match

Loading thumbnail…

Gist ccc08dae693660d7aa1b8cf2708fd13d

This example demonstrates how to query and highlight text passages in the Victorian Women Writers Project TEI corpus using XQuery 3.1. It shows a progression from simple full-text searches for repeated terms to fuzzy matching via `ft:search` and `ft:extract`, and finally visualizes results by marking hits with `ft:mark` and segmenting them into tumbling windows. The code relies on BaseX’s full-text and windowing capabilities to extract and structure paragraph-level matches containing “garden” or “house.”

CCliffordAnderson

64% match

Loading thumbnail…

XQuery Full Text

This example demonstrates the evolution of text search in XQuery, from basic string matching to full-text querying with linguistic processing. It shows how `fn:contains` and `fn:matches` perform literal pattern matching, while the XQuery Full Text 3.1 features—`contains text`, `using stemming`, `ft:mark`, and the `score` clause—enable case-insensitive, stem-aware, ranked search results. The code queries a collection of TEI-encoded texts (`vwwp_tei`) and returns matched paragraphs, with scoring wrapped in XML output and string formatting via `format-number`.

CCliffordAnderson

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

63% match