Skip to main content
SimilarExport ZIP
100%

Retrieving Karl Barth metadata from the Library of Congress using SRU

✓ Published0🌍 Public
CCliffordAnderson
Last edited Jan 22, 2014
Created on Jan 22, 2014

This example shows how to retrieve Karl Barth metadata from the Library of Congress using the SRU protocol, storing each MODS record locally. The XQuery code builds a query URL with parameters like `dc.subject=barth,%20karl` and uses `httpclient:get` to fetch a single record, then extracts the LCCN identifier to save the record as an XML file in `/db/mods/`. The companion `sru.txt` file provides the raw SRU endpoint URL. The visualization relies on the `mods` namespace for parsing and the `httpclient` library for HTTP requests.

AI-generated description

Similar vizzes

Loading thumbnail…

Simple example of requesting items from the SRU gateway at the Library of Congress

This example demonstrates how to query the Library of Congress SRU gateway for a single bibliographic record, using the Library of Congress Control Number (LCCN) as the search key. It shows how to request metadata in a specific format—here, MODS, though DC and MARCXML are also supported—and then extract the record data from the SRU XML response. The code relies on the `http:send-request` function from the EXPath HTTP Client to perform the GET request, and uses XQuery 3.0 with namespace declarations for MODS, Dublin Core, MARCXML, and the SRU/Z39.50 protocol. The returned record is selected via the `zs:recordData` path.

CCliffordAnderson
80% match
Loading thumbnail…

Simple example of retrieving a record in EAD (or Dublin Core) from the Archives Hub using SRU

This example demonstrates how to retrieve a single metadata record from the Archives Hub using the SRU (Search/Retrieval via URL) protocol, converting it into a specified format such as EAD or Dublin Core. It shows a live HTTP query to the Archives Hub API, where the user can adjust the search keyword and the desired metadata schema (e.g., "ead", "srw_dc", or "oai_dc"). The code uses XQuery 3.0 with the `http:send-request` function to fetch the XML response, then extracts the record data via the SRU namespace. The result is the raw metadata record, ready for display or further processing.

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

Example XQuery for Sara S.

This example shows how to extract a three-letter publication location code from a MARC 21 control field, filtering for specific geographic designators. It uses XQuery 3.1 with the `fn:substring` function to pull characters 16 through 18 from the text of the `marc:controlfield` element with `@tag='008'`. The query defines the MARC namespace and applies a `where` clause to return only codes matching `"gau"`, `"other"`, or `"codes"`. The source is a snippet of MARCXML data embedded directly in the script, demonstrating string parsing and conditional filtering in a pure XQuery environment.

CCliffordAnderson
55% match
Loading thumbnail…

Tricky Metadata Problem

This visualization demonstrates the geographic distribution of artists' books by filtering MARCXML records according to publication location codes, then organizing them into a simple table. It shows which US states and territories are represented in the source collection, with each row containing the record’s leader, normalized title, and three-letter location code. The XQuery script uses the `fn:doc()` function to fetch remote XML, the `marc` namespace to parse MARC fields, and `csv:serialize()` from the BaseX or eXist-db library to generate a CSV output. Titles are cleaned by stripping trailing slashes and normalizing whitespace via string functions.

CCliffordAnderson
55% match
Loading thumbnail…

VRA website example

This example demonstrates a focused query of a VRA XML metadata record, extracting and displaying only the `locationSet` element from the source document. The code uses the eXist-db HTTP Client module (`http:send-request`) to fetch the remote XML file from GitHub, then applies an XQuery path expression to isolate the location data. The visualization shows how structured art metadata can be programmatically filtered to reveal just geographic or provenance-related information. By leveraging the VRA Core 4 namespace declaration, the script ensures precise element selection, making it a practical tool for targeted data extraction in digital humanities projects.

CCliffordAnderson
55% match
Loading thumbnail…

Sample code for extracting, transforming, and loading IA metadata into BaseX

This example demonstrates an XQuery 3.1 pipeline for harvesting Open Library search results and persisting them as structured XML in a BaseX database. It first fetches JSON via `fetch:text` and parses it with `json:parse`, then converts each record into a canonical `book` element with attributes for key and full-text availability, and child elements for title, authors, dates, publishers, and subjects. Subsequent scripts extend the process to paginate through large result sets, and a final query retrieves full book texts from the Internet Archive, storing them alongside the metadata.

CCliffordAnderson
52% match
Loading thumbnail…

Collecting Information about UCC Churches

This visualization tracks every UCC church by scraping the organization’s directory. It uses XQuery’s `fetch:text` and `html:parse` to extract all church URL slugs from the “searchclass” div on the CTUCC site, then reconstructs the full addresses. The resulting list is shown as a data-collection step, with no layout or charting library applied—the output is purely the enumerated link set, ready for later visualization.

CCliffordAnderson
52% match