XQuery Conversion for MDID

100%

XQuery Conversion for MDID

✓ Published0🌍 Public

Last edited Jul 20, 2018

Created on Jul 20, 2018

This example demonstrates an XQuery conversion that transforms a collection of XML records into a structured CSV file, preserving field mappings for VRA and VU metadata. The code iterates over all records in a collection, extracts specific child elements and attributes, and constructs new `<record>` elements with standardized tags. It then wraps the records in a `<csv>` root element and uses the `csv:serialize` function with a map specifying `'header': true()` to generate a CSV with column headers. Finally, it writes the output to a file named "vrc.csv". The process relies on XQuery functions like `fn:collection()`, `fn:data()`, and `file:write()`, along with the `csv` module’s serialization API.

AI-generated description

Similar vizzes

Loading thumbnail…

{$doc/RecordTitle/text()}

This example extracts bibliographic records from a collection of quarterly publications and serializes them into CSV format. It queries a local XML document store containing full-text articles, capturing fields such as title, publication, volume, issue, date, pagination, and a document link. The XQuery 3.1 script uses the `csv:serialize` function to convert the generated `element csv` tree into a delimited text file, demonstrating a straightforward data-wrangling pipeline for export and downstream analysis.

CCliffordAnderson

66% match

Loading thumbnail…

XQuery for Complex Migration

This example demonstrates XQuery scripts for cleaning and restructuring VRA Core XML metadata from the DIMLI collection, focusing on consolidating duplicate work records and image records by refid. The code identifies duplicate work entries, merges their associated images while removing redundant id attributes, and normalizes image records. It also runs diagnostic queries to count built works, locations without refids, and image records (targeting 40,420 image records), while filtering location names that reference museums, libraries, or geographic terms. The visualization highlights data-quality issues in cultural-heritage metadata and the programmatic transformations needed to reconcile legacy cataloging inconsistencies.

CCliffordAnderson

66% match

Loading thumbnail…

XQuery Working Group - February 9, 2018

This example demonstrates two XQuery approaches for transforming CSV contact data into XML records, highlighting the difference between excluding a field by name and by structural exception. The first script, `data-munging-with-except.xqy`, uses the arrow operator and `csv:parse` from the XQuery standard library to parse the CSV, then constructs new XML records with `/record/(* except _)` to drop the underscore field. The second script, `data-munging.xqy`, achieves the same result using `$record/*[not(name()='_')]` and additionally persists each record to a database via `db:replace`. Both iterate through parsed records with a `for` loop and assign filenames through the `@name` attribute.

CCliffordAnderson

64% match

Loading thumbnail…

CVS to JSONL example

This example shows a practical data-transformation workflow that converts a CSV file into JSONL format, producing one JSON object per line. It fetches a remote CSV file from a GitHub gist using the `fetch:text` function, parses it into records with `csv:parse`, and iterates through each record to build key-value pairs. The code distinguishes between integer and string values using `castable as xs:integer`, then constructs JSON maps with `xml-to-json` using XQuery 3.1. The output is unindented JSONL, suitable for streaming or line-oriented processing.

CCliffordAnderson

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

58% match

Loading thumbnail…

fn:xml-to-json example

This example demonstrates the transformation of a nested XML document into JSON using the XQuery 3.1 function `fn:xml-to-json`. The XML input encodes workshop information, including leaders and institutions, within a structured `<map>` and `<array>` hierarchy using the XPath Functions namespace. The function converts this XML representation directly into its JSON equivalent, preserving the nested array and map structure. The code relies on the standard XQuery 3.1 function library, with the source document defined inline and the transformed JSON output returned as the query result.

CCliffordAnderson

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

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

56% match