openMusiXplora

Research and data access

Working with the data offline

Read a complete record as JSON, identify its source and verify the files.

Examples from data edition 1, issued on 20 November 2026.

Choose a distribution

For tabular analysis, catalogue-csv.zip contains tables from the base catalogue. catalogue.jsonl.gz supplies its records in JSON Lines format. The July place retrieval has its own download. Document which components of the edition you combined for an analysis.

Select a record from the base export

Download catalogue.jsonl.gz from the online catalogue’s downloads page. Place it in your working directory. This example reads the export one line at a time until it reaches ID f0394.

import gzip
import json

with gzip.open("catalogue.jsonl.gz", "rt", encoding="utf-8") as source:
    for line in source:
        record = json.loads(line)
        if record["profile"]["id"] == "f0394":
            print(record["profile"]["label"], len(record["relationships"]))
            break

The program prints “Josef Focht 229”. In openMusiXplora Portable the same query needs only one of the ZIP archives.

Read one JSON file from an archive

openMusiXplora Portable contains 31 ZIP files with individually named JSON records. In Josef Focht’s record, “JSON file in the edition archive” gives the archive name and exact member path. Download records-0024.zip and run the Python example in the same directory.

import json
from zipfile import ZipFile

with ZipFile("records-0024.zip") as archive:
    with archive.open("records/d5/f0394.json") as source:
        record = json.load(source)
print(record["profile"]["label"], len(record["relationships"]))

The result is “Josef Focht 229”. The profile field contains the record summary and relationships contains the complete relationship list. The online API returns that list in pages.

Verify the version used

Compare the downloaded file’s SHA-256 checksum with the inventory for the same edition. Report the edition, filename and checksum in a publication. In a derived table, identify any normalisation or attributions you added.