Appearance
Chapter overview
NOTEBOOK 05

Pipe Organ Dataset

You’re reading the fixed September 2026 · research guides edition.Current notebook ↗
RESOURCES / NOTEBOOK 05

A collection with a memory

POD brings organ records together while preserving attribution, disagreement and historical context.

The MODAVIS Pipe Organ Dataset (POD) connects instrument identities with source accounts, people, places, specifications and documented events. Its release structure provides a fixed basis for reuse and comparison.

POD 1.6.0Published corpus
Canonical organs215,769
Actors11,778
Places203,831
Source collections25
Virtual instruments897

These are release-specific corpus counts, not a census of all surviving instruments. Coverage depends on the contributing collections, their documentation and the reconciliation work embodied in this release.

A record is a meeting point for accounts

The corpus connects instrument identities with attributed descriptions. Several sources can discuss the same organ, and one source can document more than one state. That makes the distinction between an instrument and an account central to reuse. A convenient instrument summary should remain traceable to the statements from which it was assembled.

What the numbers count

UnitMeaning for analysis
Instrument identityA canonical point of reference for an organ within the released corpus.
Source membershipA connection between a record and one contributing source collection.
Specification accountA particular attributed description of an instrument’s configuration.
Stop occurrenceA stop recorded within a source account; not necessarily a unique physical stop.
Documented eventAn attributed historical occurrence, distinct from a processing operation.

These levels should not be added together or substituted for one another. Two accounts can describe the same physical stop, and an account may preserve only part of a specification. A larger number of stop occurrences can therefore reflect richer documentation rather than a larger population of instruments or components.

What a release makes stable

A release fixes an interpretable state of the corpus, including its methods, distributions and known limits. It provides a common basis for comparison even while a public interface or development workspace changes. Keep that release identity with any extracted table, graph or derived dataset; the values alone do not record the conditions under which they were produced.

Sources & further reading

  1. Pipe Organ Dataset 1.6.0

    The fixed dataset release, methods and checksums.

  2. Dominik Ukolov · Musikinstrumente im virtuellen Raum (2026)

    Dissertation submitted to Universität Leipzig, 11 September 2026. Chapters 1–6 and 8; Appendix I.4 for the software and resource inventory. See the dedicated research guides for claim-specific section references. Page numbers refer to the printed manuscript pagination. The manuscript is not distributed by this website.

Page editions 2026-09-r4 ↓

Read a fixed snapshot of this chapter, or return to the current notebook.

Edition 2026-09-r4 · SHA-256 0430a3a16313Page metadata ↗