Skip to main content
SimilarExport ZIP
100%

A model MODS document

✓ Published0🌍 Public
CCliffordAnderson
Last edited Feb 6, 2014
Created on Feb 6, 2014

This example shows a blank metadata template for a MODS document, a standard XML format for bibliographic records. It visualizes the empty structure of the schema, including fields for title, creator, language, subject, and publication details. The code parses the XML using JavaScript’s DOMParser and renders the hierarchy as a node-link diagram with d3.forceSimulation for layout and d3.hierarchy for tree traversal. The visualization does not load external data beyond the provided mods.xml file, focusing solely on the schema’s skeleton.

AI-generated description

Similar vizzes

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
74% 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
65% 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
62% match
Loading thumbnail…

Simple Books Document

This example visualizes a small set of books from an XML data source, grouping them by their `class` attribute (fiction or nonfiction). It first shows the hierarchical document structure as a simple indented list, then renders each book as a colored node in a force-directed graph. The visualization uses D3.js’s `d3.hierarchy` and `d3.tree` to lay out the XML tree, while `d3.forceSimulation` positions the book nodes, with the `class` value driving node color and tooltip text. The raw XML is loaded via `d3.xml`, and the document’s structure is directly mirrored in the layout, making the data’s grouping and classification immediately visible.

CCliffordAnderson
62% match
Loading thumbnail…

Full Text IA

This example visualizes the full-text metadata of a book collection, showing how documents are distributed across subject categories. It loads book records from an XML database and filters out any documents tagged with the "Protected DAISY" subject. The visualization uses D3.js’s force-directed layout to position nodes, with each book represented as a point linked to its subject keywords. The code retrieves data via an XQuery query, and the rendering relies on D3’s force simulation to cluster related items, making thematic groupings visible at a glance.

CCliffordAnderson
61% match
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…

Sample RELAX NG for book-relaxng.xml

This example visualizes a RELAX NG compact syntax schema for book metadata, transforming the grammar into a node-link diagram. It shows the hierarchical relationships between elements like `author`, `title`, `publisher`, and `price`, along with their attributes and data constraints. The rendering uses a force-directed layout to position nodes and links, with the schema’s pattern-based text restrictions displayed as labels. The code defines the grammar in `.rnc` format, and the visualization likely employs JavaScript libraries for graph drawing, though the specific API calls are not shown in the provided snippet.

CCliffordAnderson
58% 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
58% match