{
  "title": "A tool for each part of the work — Tools & experiences",
  "text": "MODAVIS (2026). A tool for each part of the work — Tools & experiences. Research notebooks, September 2026 · Cuntz worked examples edition. https://modavis.org/editions/2026-09-r5/software/introduction/",
  "bibtex": "@misc{modavis_software_introduction_2026_09_r5,\n  author = {{MODAVIS}},\n  title = {A tool for each part of the work — Tools & experiences},\n  year = {2026},\n  month = {09},\n  version = {2026-09-r5},\n  url = {https://modavis.org/editions/2026-09-r5/software/introduction/},\n  note = {Content SHA-256: 134f9f7ccb2853b5e7d4e8981c0bf65148614a6cc8d2f463899c3533861afcd7}\n}",
  "url": "https://modavis.org/editions/2026-09-r5/software/introduction/",
  "sha256": "134f9f7ccb2853b5e7d4e8981c0bf65148614a6cc8d2f463899c3533861afcd7",
  "edition": "2026-09-r5",
  "date": "2026-09-26",
  "canonicalPayload": "{\"book\":{\"number\":\"06\",\"slug\":\"software\",\"title\":\"Tools & experiences\"},\"chapter\":{\"blocks\":[{\"items\":[{\"detail\":\"57 entries · software, modules, standards and research collections\",\"href\":\"/notebooks/software/directory/\",\"label\":\"Explore the complete ecosystem\"}],\"type\":\"links\"},{\"items\":[{\"detail\":\"Explore instruments, sources and their relationships.\",\"href\":\"https://navigator.modavis.org\",\"label\":\"Open MODAVIS Navigator\"},{\"detail\":\"Geographic access to organological data.\",\"href\":\"https://map.modavis.org/\",\"label\":\"OrgMap\"},{\"detail\":\"Browser-based exploration of Virtual Acoustic Objects.\",\"href\":\"https://vaoxr.modavis.org/\",\"label\":\"vaoXR\"},{\"detail\":\"The recording application’s release record.\",\"href\":\"https://doi.org/10.5281/zenodo.22698744\",\"label\":\"OrgRec 0.3.2\"}],\"type\":\"links\"},{\"id\":\"workflow\",\"text\":\"From fieldwork to publication\",\"type\":\"heading\"},{\"text\":\"Recording, reconciliation, analysis and interactive presentation ask different things of a tool. MODAVIS treats them as connected stages with explicit inputs, outputs and responsibilities.\",\"type\":\"p\"},{\"text\":\"Six core components organize the research workflow. Monitor and the musiXplora Bridge provide supporting capabilities. Twelve Processor modules and specialist applications handle particular transcription, analysis, modelling and presentation tasks.\",\"type\":\"p\"},{\"text\":\"A public interface, a software release record and a source repository are separate forms of access. Follow each resource’s own documentation for its availability and licensing.\",\"title\":\"Access differs by component\",\"type\":\"note\"},{\"boundary\":\"The example illustrates component responsibilities without attributing unverified processing history to the actual release.\",\"concept\":\"A processing candidate is a proposed interpretation of source material. Review and publication are additional decisions, with their own evidence and responsibilities.\",\"expanded\":false,\"id\":\"cuntz-software-boundaries\",\"scenario\":\"Use the Cuntz workbook observation to imagine a new import workflow. This is an explanatory mapping to the Processor architecture, not a claim that the published Cuntz release was built by all current Processor modules.\",\"sources\":[{\"detail\":\"Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.\",\"href\":\"https://doi.org/10.5281/zenodo.22151203\",\"label\":\"Cuntz Positiv · VAO 0.5.0-rc.2\"},{\"detail\":\"Identity, state, configuration, evidence, assertions, context and provenance. Teaching examples explain its distinctions without inventing new normative properties.\",\"href\":\"https://doi.org/10.5281/zenodo.22126086\",\"label\":\"MODAVIS Ontology Network 0.1.0\"}],\"steps\":[{\"text\":\"Intake identifies the workbook bytes and source context. Extraction retains the literal cell, property code and unit rather than keeping only a convenient normalized number.\",\"title\":\"Preserve the source\"},{\"text\":\"A normalizer can propose a structured observation and a pipe identity. A reviewer checks the cell interpretation, the identity match and qualifications such as the timestamp note.\",\"title\":\"Inspect the candidate\"},{\"text\":\"An accepted projection keeps the evidence link and decision. A public view can be concise while a fixed release preserves the record needed to re-examine the claim.\",\"title\":\"Publish the accountable result\"}],\"takeaway\":\"Automation can propose a useful structure; an accountable workflow keeps the interpretation and its grounds inspectable.\",\"title\":\"Where does an extracted number become an accepted claim?\",\"type\":\"example\"},{\"id\":\"choose-a-tool\",\"text\":\"Start with an outcome\",\"type\":\"heading\"},{\"headers\":[\"You want to…\",\"Start with…\",\"Then keep…\"],\"rows\":[[\"Explore instruments and their sources\",\"Navigator or OrgMap\",\"Record identities, source references and dataset version.\"],[\"Document a recording session\",\"OrgRec\",\"Original takes, configuration and review decisions.\"],[\"Review photographed text\",\"Scriptor\",\"Source crops, raw transcription and corrections.\"],[\"Inspect a VAO package\",\"VAO CLI or a compatible viewer\",\"Package version, capabilities and verification result.\"],[\"Build a Unity or Blender workflow\",\"The corresponding VAO importer\",\"The importer version and the supported contract.\"],[\"Reuse an analytical corpus\",\"A fixed dataset or research collection\",\"Distribution, checksum and method.\"]],\"type\":\"table\"},{\"text\":\"These entry points serve different audiences. Public viewers offer immediate exploration. Desktop applications and importers require an appropriate local environment. The framework’s backend components organise research processing under controlled operation; they are not public upload endpoints that a visitor is expected to discover or configure.\",\"type\":\"p\"},{\"id\":\"three-versions\",\"text\":\"Read three versions separately\",\"type\":\"heading\"},{\"text\":\"A software version identifies an implementation, a standard version identifies a contract, and a data version identifies an input or object release. A demonstration may combine one of each. Write down all three when reporting a result or a problem: “the latest tool” is not enough to reproduce what happened.\",\"type\":\"p\"},{\"id\":\"demonstration-to-reuse\",\"text\":\"From a demonstration to reuse\",\"type\":\"heading\"},{\"text\":\"A demonstration shows a particular configuration working under particular conditions. Before adapting it, inspect the input assumptions, supported platform and documented output. This is especially important for research modules whose results need review, or whose scope is narrower than a familiar product label suggests. The directory’s expanded entries describe the practical role and the interpretation boundary together.\",\"type\":\"p\"},{\"items\":[{\"href\":\"/notebooks/software/processing/\",\"label\":\"A worked Processor workflow\"},{\"href\":\"/notebooks/software/clients/\",\"label\":\"Choose a VAO client\"}],\"type\":\"links\"}],\"intro\":\"The MODAVIS ecosystem separates research responsibilities while connecting the resulting evidence.\",\"slug\":\"introduction\",\"sources\":[{\"detail\":\"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.\",\"label\":\"Dominik Ukolov · Musikinstrumente im virtuellen Raum (2026)\"},{\"detail\":\"The recording application’s release record.\",\"href\":\"https://doi.org/10.5281/zenodo.22698744\",\"label\":\"OrgRec 0.3.2\"},{\"detail\":\"Research data, software and publications.\",\"href\":\"https://zenodo.org/communities/modavis/\",\"label\":\"MODAVIS on Zenodo\"}],\"title\":\"A tool for each part of the work\"},\"date\":\"2026-09-26\",\"edition\":\"2026-09-r5\",\"figures\":{}}",
  "payload": {
    "edition": "2026-09-r5",
    "date": "2026-09-26",
    "book": {
      "slug": "software",
      "title": "Tools & experiences",
      "number": "06"
    },
    "chapter": {
      "slug": "introduction",
      "title": "A tool for each part of the work",
      "intro": "The MODAVIS ecosystem separates research responsibilities while connecting the resulting evidence.",
      "blocks": [
        {
          "type": "links",
          "items": [
            {
              "label": "Explore the complete ecosystem",
              "href": "/notebooks/software/directory/",
              "detail": "57 entries · software, modules, standards and research collections"
            }
          ]
        },
        {
          "type": "links",
          "items": [
            {
              "label": "Open MODAVIS Navigator",
              "href": "https://navigator.modavis.org",
              "detail": "Explore instruments, sources and their relationships."
            },
            {
              "label": "OrgMap",
              "href": "https://map.modavis.org/",
              "detail": "Geographic access to organological data."
            },
            {
              "label": "vaoXR",
              "href": "https://vaoxr.modavis.org/",
              "detail": "Browser-based exploration of Virtual Acoustic Objects."
            },
            {
              "label": "OrgRec 0.3.2",
              "href": "https://doi.org/10.5281/zenodo.22698744",
              "detail": "The recording application’s release record."
            }
          ]
        },
        {
          "type": "heading",
          "text": "From fieldwork to publication",
          "id": "workflow"
        },
        {
          "type": "p",
          "text": "Recording, reconciliation, analysis and interactive presentation ask different things of a tool. MODAVIS treats them as connected stages with explicit inputs, outputs and responsibilities."
        },
        {
          "type": "p",
          "text": "Six core components organize the research workflow. Monitor and the musiXplora Bridge provide supporting capabilities. Twelve Processor modules and specialist applications handle particular transcription, analysis, modelling and presentation tasks."
        },
        {
          "type": "note",
          "title": "Access differs by component",
          "text": "A public interface, a software release record and a source repository are separate forms of access. Follow each resource’s own documentation for its availability and licensing."
        },
        {
          "type": "example",
          "id": "cuntz-software-boundaries",
          "title": "Where does an extracted number become an accepted claim?",
          "concept": "A processing candidate is a proposed interpretation of source material. Review and publication are additional decisions, with their own evidence and responsibilities.",
          "scenario": "Use the Cuntz workbook observation to imagine a new import workflow. This is an explanatory mapping to the Processor architecture, not a claim that the published Cuntz release was built by all current Processor modules.",
          "steps": [
            {
              "title": "Preserve the source",
              "text": "Intake identifies the workbook bytes and source context. Extraction retains the literal cell, property code and unit rather than keeping only a convenient normalized number."
            },
            {
              "title": "Inspect the candidate",
              "text": "A normalizer can propose a structured observation and a pipe identity. A reviewer checks the cell interpretation, the identity match and qualifications such as the timestamp note."
            },
            {
              "title": "Publish the accountable result",
              "text": "An accepted projection keeps the evidence link and decision. A public view can be concise while a fixed release preserves the record needed to re-examine the claim."
            }
          ],
          "takeaway": "Automation can propose a useful structure; an accountable workflow keeps the interpretation and its grounds inspectable.",
          "boundary": "The example illustrates component responsibilities without attributing unverified processing history to the actual release.",
          "sources": [
            {
              "label": "Cuntz Positiv · VAO 0.5.0-rc.2",
              "href": "https://doi.org/10.5281/zenodo.22151203",
              "detail": "Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release."
            },
            {
              "label": "MODAVIS Ontology Network 0.1.0",
              "href": "https://doi.org/10.5281/zenodo.22126086",
              "detail": "Identity, state, configuration, evidence, assertions, context and provenance. Teaching examples explain its distinctions without inventing new normative properties."
            }
          ],
          "expanded": false
        },
        {
          "type": "heading",
          "text": "Start with an outcome",
          "id": "choose-a-tool"
        },
        {
          "type": "table",
          "headers": [
            "You want to…",
            "Start with…",
            "Then keep…"
          ],
          "rows": [
            [
              "Explore instruments and their sources",
              "Navigator or OrgMap",
              "Record identities, source references and dataset version."
            ],
            [
              "Document a recording session",
              "OrgRec",
              "Original takes, configuration and review decisions."
            ],
            [
              "Review photographed text",
              "Scriptor",
              "Source crops, raw transcription and corrections."
            ],
            [
              "Inspect a VAO package",
              "VAO CLI or a compatible viewer",
              "Package version, capabilities and verification result."
            ],
            [
              "Build a Unity or Blender workflow",
              "The corresponding VAO importer",
              "The importer version and the supported contract."
            ],
            [
              "Reuse an analytical corpus",
              "A fixed dataset or research collection",
              "Distribution, checksum and method."
            ]
          ]
        },
        {
          "type": "p",
          "text": "These entry points serve different audiences. Public viewers offer immediate exploration. Desktop applications and importers require an appropriate local environment. The framework’s backend components organise research processing under controlled operation; they are not public upload endpoints that a visitor is expected to discover or configure."
        },
        {
          "type": "heading",
          "text": "Read three versions separately",
          "id": "three-versions"
        },
        {
          "type": "p",
          "text": "A software version identifies an implementation, a standard version identifies a contract, and a data version identifies an input or object release. A demonstration may combine one of each. Write down all three when reporting a result or a problem: “the latest tool” is not enough to reproduce what happened."
        },
        {
          "type": "heading",
          "text": "From a demonstration to reuse",
          "id": "demonstration-to-reuse"
        },
        {
          "type": "p",
          "text": "A demonstration shows a particular configuration working under particular conditions. Before adapting it, inspect the input assumptions, supported platform and documented output. This is especially important for research modules whose results need review, or whose scope is narrower than a familiar product label suggests. The directory’s expanded entries describe the practical role and the interpretation boundary together."
        },
        {
          "type": "links",
          "items": [
            {
              "label": "A worked Processor workflow",
              "href": "/notebooks/software/processing/"
            },
            {
              "label": "Choose a VAO client",
              "href": "/notebooks/software/clients/"
            }
          ]
        }
      ],
      "sources": [
        {
          "label": "Dominik Ukolov · Musikinstrumente im virtuellen Raum (2026)",
          "detail": "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."
        },
        {
          "label": "OrgRec 0.3.2",
          "href": "https://doi.org/10.5281/zenodo.22698744",
          "detail": "The recording application’s release record."
        },
        {
          "label": "MODAVIS on Zenodo",
          "href": "https://zenodo.org/communities/modavis/",
          "detail": "Research data, software and publications."
        }
      ]
    },
    "figures": {}
  }
}