Ed Warga's OAI

100%

Ed Warga's OAI

✓ Published0🌍 Public

Last edited Jul 13, 2015

Created on Jul 13, 2015

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.

AI-generated description

Similar vizzes

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

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

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

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

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…

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

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

54% match

Loading thumbnail…

DPLA Data

This example queries the Digital Public Library of America (DPLA) API to fetch and display search results as a simple webpage. It shows a list of image thumbnails with titles, each linked to its source item. The code uses the XQuery `fetch:text` or `fn:json-doc` functions to retrieve JSON data from the DPLA API, then parses it with `json:parse` or direct JSON navigation. It constructs HTML `<li>` elements containing an `<img>` tag and anchor, filtering out results without a thumbnail or title.

CCliffordAnderson

53% match