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

100%

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

✓ Published0🌍 Public

Last edited Jul 18, 2013

Created on Jul 18, 2013

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.

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

79% match

Loading thumbnail…

Retrieving Karl Barth metadata from the Library of Congress using SRU

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.

CCliffordAnderson

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

62% match

Loading thumbnail…

EAC-CPF Presentation

This example demonstrates how EAC-CPF records structure archival authority data, using a sample XML file and an XQuery expression that fetches a remote document from GitHub. The XML shows a person entity with a control section for maintenance metadata and a cpfDescription containing identity and biographical history. The XQuery code retrieves the Gregory of Nazianzus record via a raw GitHub URL, illustrating how archives can query and reuse published EAC-CPF instances. The presentation highlights the distinction between library and archival authority control through this standards-based exchange format.

CCliffordAnderson

62% match

Loading thumbnail…

Ed Warga's OAI

This visualization shows the full record set harvested from a Harvard DASH repository subset via the OAI-PMH protocol. It demonstrates a recursive pagination pattern using XQuery 3.1, where the `local:resume` function repeatedly calls `fn:doc` on the base URL with a resumption token until no further tokens remain. The code retrieves Dublin Core metadata in `oai_dc` format, concatenating all response documents into a single sequence. The example highlights the use of XPath namespace declarations and string concatenation to construct request URLs for the OAI interface.

CCliffordAnderson

61% match

Loading thumbnail…

Get finding aid

This example demonstrates how to fetch and transform an XML finding aid from a GitHub repository, isolating a specific portion of its hierarchical structure. The code defines a function that rebuilds the EAD document by extracting the header, archdesc attributes, and selected child elements while discarding others. It uses the XQuery language with a custom function `local:build-ead` to restructure the XML. The data source is a remote finding aid document loaded via `fn:doc` from a raw GitHub URL. The transformation explicitly copies the `c01` element and its preceding siblings, omitting the `c02` children, thereby illustrating selective XML reshaping for archival metadata.

CCliffordAnderson

61% match

Loading thumbnail…

Convert JSON to Dublin Core in XML

This example shows a live conversion of movie search results from JSON into Dublin Core XML metadata. It retrieves data from the OMDB API using `fetch:text` and `fn:parse-json` to parse the response, then extracts the `Search` array. For each movie, it creates a Dublin Core `title` and `relation` element, mapping the movie title and poster URL respectively. The code uses XQuery 3.1 with the `dc` namespace, and the final output is an XML `<movies>` wrapper. The example demonstrates a straightforward data transformation pipeline, not a visual chart, but it is included in the gallery for its metadata-handling technique.

CCliffordAnderson

58% match

Loading thumbnail…

XQuery to clean up data from an Excel-generated webpage & generate an EAD document

This example shows how XQuery 3.1 can clean data scraped from an Excel-generated HTML table and use it to generate an EAD (Encoded Archival Description) finding aid. The `fetch:text()` and `html:parse` functions extract rows from a legacy webpage, normalize the text content, and repackage the fields into JSON maps. A second function transforms those entries into EAD `<c02>` components, inserting metadata like titles, abstracts, and thumbnail image links from the Lantern Slide collection at Vanderbilt. Finally, the script rebuilds a complete EAD document, injecting the new `<c02>` elements into the existing archival description hierarchy, preserving the original structure while enriching it with parsed data.

CCliffordAnderson

58% match