Get finding aid

100%

Get finding aid

✓ Published0🌍 Public

Last edited Jun 12, 2015

Created on Jun 12, 2015

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.

AI-generated description

Similar vizzes

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

72% match

Loading thumbnail…

EAD template using MSS.102

An EAD (Encoded Archival Description) template renders a collection’s metadata from an XML file, displaying the finding aid’s title, publication statement, scope notes, and series listing. The visualization structures the archival hierarchy using the EAD XML schema, with fields for repository, unit ID, extent, and dates. The code relies on standard XML parsing to extract elements such as `<eadheader>`, `<archdesc>`, and `<scopecontent>`, presenting the collection’s linear feet and box count alongside its inclusive date range. The interface highlights the template’s reusable structure for archival description.

CCliffordAnderson

69% match

Loading thumbnail…

Xquery for Unit Dates

This example demonstrates a preprocessing step for visualizing dates in archival finding aids, extracting four-digit years from `<unitdate>` elements in a single EAD XML document. The XQuery script uses the XQuery 3.0 `copy` and `modify` expressions to insert a `normal` attribute containing the extracted year onto each unitdate node. It leverages a namespace declaration for the EAD standard and the `fn:doc` and `fn:replace` functions to fetch the remote XML file from GitHub and parse the date text via regular expressions. The output is the modified XML nodes, ready for downstream temporal analysis or charting.

CCliffordAnderson

68% match

Loading thumbnail…

For Zach Johnson

This example transforms a raw XML extract of the Jesse Wills finding aid into structured archival units using XQuery 3.1. The code loads a source document from a GitHub gist, then uses a tumbling window to pair adjacent XML elements into `c02` records. It tokensizes `unittitle` text by semicolons and periods, classifies segments as folder containers or dates, and constructs `did` elements with normalized `unitdate` and `unittitle` values. The result is a cleaned, hierarchical data structure suitable for downstream visualization, though no rendering library is invoked here.

CCliffordAnderson

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

66% match

Loading thumbnail…

Documentation for Introduction to EAD Workshop at Vanderbilt University

This example documents a two-day introductory workshop on Encoded Archival Description (EAD), showing the training schedule, linked reference materials, and a hands-on XML markup exercise using a postcard from the Library of Congress. It demonstrates the use of XML schema validation, including a Relax NG compact schema (`postcard.rnc`) and a sample EAD template with namespace declarations. The code highlights specific APIs and standards, such as the `xsd:date` datatype, `xml-model` processing instruction, and the EAD XML schema (`ead.xsd`). The data originates from the workshop’s GitHub gist, featuring raw text files and images.

CCliffordAnderson

65% match

Loading thumbnail…

{$title || " - "}

This example displays a list of EAD (Encoded Archival Description) titles sorted alphabetically from a collection of finalized XML files, rendered as plain paragraph elements in an XHTML page. It uses XQuery 3.1 with the `fn:collection` function to gather titles from `titleproper[@type="filing"]` nodes, and a local template function `local:template` constructs the HTML output, setting a dynamic heading level and tab title. The code demonstrates a server-side, XML-to-HTML transformation pipeline without client-side JavaScript libraries or interactive visualization components.

CCliffordAnderson

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

61% match