{
  "title": "From exploration to a fixed source — MODAVIS Navigator",
  "text": "MODAVIS (2026). From exploration to a fixed source — MODAVIS Navigator. Research notebooks, September 2026 · expanded edition. https://modavis.org/editions/2026-09-r3/navigator/data/",
  "bibtex": "@misc{modavis_navigator_data_2026_09_r3,\n  author = {{MODAVIS}},\n  title = {From exploration to a fixed source — MODAVIS Navigator},\n  year = {2026},\n  month = {09},\n  version = {2026-09-r3},\n  url = {https://modavis.org/editions/2026-09-r3/navigator/data/},\n  note = {Content SHA-256: f25ace6522f0710079091f2851d60ccdcd90a7f6f973f684e81d215ba9041940}\n}",
  "url": "https://modavis.org/editions/2026-09-r3/navigator/data/",
  "sha256": "f25ace6522f0710079091f2851d60ccdcd90a7f6f973f684e81d215ba9041940",
  "edition": "2026-09-r3",
  "date": "2026-09-26",
  "canonicalPayload": "{\"book\":{\"number\":\"04\",\"slug\":\"navigator\",\"title\":\"MODAVIS Navigator\"},\"chapter\":{\"blocks\":[{\"text\":\"A changing research interface is useful for discovery. A fixed dataset release makes an analysis attributable and repeatable. Record both the route you used to explore and the version of the data that supports your findings.\",\"type\":\"p\"},{\"id\":\"research-note\",\"text\":\"A practical research note\",\"type\":\"heading\"},{\"items\":[\"The research question and date of access.\",\"The POD release version and DOI.\",\"Filters, selected fields and any exclusions.\",\"Relevant source accounts and unresolved relationships.\",\"The downloaded distribution and its checksum when working locally.\"],\"type\":\"list\"},{\"text\":\"The dataset notebook explains the available distributions. The site’s own citation control refers to the explanatory notebook page; it does not replace a citation of the underlying dataset.\",\"type\":\"p\"},{\"id\":\"discovery-trail\",\"text\":\"Separate the discovery trail from the analysis input\",\"type\":\"heading\"},{\"text\":\"A useful note captures the live interface URL and access date, but a URL alone may not preserve the selected rows or the data state behind them. Record the identities in the selection and identify the fixed release used when the work becomes an analysis. If the interface and your local distribution differ, describe the difference rather than silently treating them as the same input.\",\"type\":\"p\"},{\"id\":\"note-template\",\"text\":\"A reusable research-note template\",\"type\":\"heading\"},{\"label\":\"Illustrative template · fill with the actual values\",\"text\":\"Question:\\nDiscovery URL and access date:\\nDataset version and version DOI:\\nDistribution filename and checksum:\\nInstrument / account identifiers selected:\\nFilters and exclusions:\\nUnit counted or compared:\\nUnresolved dates, roles or relationships:\\nAnalysis procedure and software version:\\nResult files and their checksums:\",\"type\":\"code\"},{\"text\":\"The unit line is particularly important. An instrument count, a source-account count and a stop-occurrence count can describe the same selection at different levels. A later researcher should be able to tell which one your chart or table uses without reconstructing your assumptions from the code.\",\"type\":\"p\"},{\"id\":\"claim-citation\",\"text\":\"Cite the sources at the level of the claim\",\"type\":\"heading\"},{\"text\":\"Use the dataset version to identify the corpus used for selection or computation. Where a historical argument depends on a particular source statement, cite that statement’s source as well. Cite the application separately when a software-specific method matters. The notebook can explain the workflow, but its citation does not stand in for the evidence underlying an attribution or date.\",\"type\":\"p\"},{\"text\":\"Compare version, file identity, projection and documented changes before interpreting a mismatch as a scientific disagreement. Keep the earlier input and analysis record available until the difference is understood.\",\"title\":\"When a download differs\",\"type\":\"note\"},{\"items\":[{\"detail\":\"The fixed dataset release, methods and checksums.\",\"href\":\"https://doi.org/10.5281/zenodo.22308263\",\"label\":\"Pipe Organ Dataset 1.6.0\"},{\"href\":\"/notebooks/dataset/access/\",\"label\":\"Choose a data distribution\"}],\"type\":\"links\"}],\"intro\":\"Use the Navigator to discover; use a versioned release to identify the exact data behind your analysis.\",\"slug\":\"data\",\"sources\":[{\"detail\":\"The fixed dataset release, methods and checksums.\",\"href\":\"https://doi.org/10.5281/zenodo.22308263\",\"label\":\"Pipe Organ Dataset 1.6.0\"}],\"title\":\"From exploration to a fixed source\"},\"date\":\"2026-09-26\",\"edition\":\"2026-09-r3\",\"figures\":{}}",
  "payload": {
    "edition": "2026-09-r3",
    "date": "2026-09-26",
    "book": {
      "slug": "navigator",
      "title": "MODAVIS Navigator",
      "number": "04"
    },
    "chapter": {
      "slug": "data",
      "title": "From exploration to a fixed source",
      "intro": "Use the Navigator to discover; use a versioned release to identify the exact data behind your analysis.",
      "blocks": [
        {
          "type": "p",
          "text": "A changing research interface is useful for discovery. A fixed dataset release makes an analysis attributable and repeatable. Record both the route you used to explore and the version of the data that supports your findings."
        },
        {
          "type": "heading",
          "text": "A practical research note",
          "id": "research-note"
        },
        {
          "type": "list",
          "items": [
            "The research question and date of access.",
            "The POD release version and DOI.",
            "Filters, selected fields and any exclusions.",
            "Relevant source accounts and unresolved relationships.",
            "The downloaded distribution and its checksum when working locally."
          ]
        },
        {
          "type": "p",
          "text": "The dataset notebook explains the available distributions. The site’s own citation control refers to the explanatory notebook page; it does not replace a citation of the underlying dataset."
        },
        {
          "type": "heading",
          "text": "Separate the discovery trail from the analysis input",
          "id": "discovery-trail"
        },
        {
          "type": "p",
          "text": "A useful note captures the live interface URL and access date, but a URL alone may not preserve the selected rows or the data state behind them. Record the identities in the selection and identify the fixed release used when the work becomes an analysis. If the interface and your local distribution differ, describe the difference rather than silently treating them as the same input."
        },
        {
          "type": "heading",
          "text": "A reusable research-note template",
          "id": "note-template"
        },
        {
          "type": "code",
          "label": "Illustrative template · fill with the actual values",
          "text": "Question:\nDiscovery URL and access date:\nDataset version and version DOI:\nDistribution filename and checksum:\nInstrument / account identifiers selected:\nFilters and exclusions:\nUnit counted or compared:\nUnresolved dates, roles or relationships:\nAnalysis procedure and software version:\nResult files and their checksums:"
        },
        {
          "type": "p",
          "text": "The unit line is particularly important. An instrument count, a source-account count and a stop-occurrence count can describe the same selection at different levels. A later researcher should be able to tell which one your chart or table uses without reconstructing your assumptions from the code."
        },
        {
          "type": "heading",
          "text": "Cite the sources at the level of the claim",
          "id": "claim-citation"
        },
        {
          "type": "p",
          "text": "Use the dataset version to identify the corpus used for selection or computation. Where a historical argument depends on a particular source statement, cite that statement’s source as well. Cite the application separately when a software-specific method matters. The notebook can explain the workflow, but its citation does not stand in for the evidence underlying an attribution or date."
        },
        {
          "type": "note",
          "title": "When a download differs",
          "text": "Compare version, file identity, projection and documented changes before interpreting a mismatch as a scientific disagreement. Keep the earlier input and analysis record available until the difference is understood."
        },
        {
          "type": "links",
          "items": [
            {
              "label": "Pipe Organ Dataset 1.6.0",
              "href": "https://doi.org/10.5281/zenodo.22308263",
              "detail": "The fixed dataset release, methods and checksums."
            },
            {
              "label": "Choose a data distribution",
              "href": "/notebooks/dataset/access/"
            }
          ]
        }
      ],
      "sources": [
        {
          "label": "Pipe Organ Dataset 1.6.0",
          "href": "https://doi.org/10.5281/zenodo.22308263",
          "detail": "The fixed dataset release, methods and checksums."
        }
      ]
    },
    "figures": {}
  }
}