The MODAVIS ecosystem

Use the framework overview to identify the owner of a handoff before designing a cross-component workflow. Keep the source, review and publication decisions attributable as the item moves between components.

When a shared data structure needs to change, establish its schema and integrity contract here before relying on it in processing or public views. A schema migration and a scholarly interpretation are different decisions.

Start here when an approved source needs to enter the research workflow. Retain its acquisition context and original evidence so that later normalization can be assessed against what was actually obtained.

Choose the module that answers a bounded processing question. Keep the candidate or analytical result separate from accepted corpus facts until the relevant review and projection conditions are satisfied.

Use discovery results to decide what deserves acquisition or review. A promising bibliographic or authority match should carry its evidence into the next stage instead of becoming a canonical link automatically.

Begin with an instrument, place or actor and follow its attributed accounts. Record the dataset version and a stable selection when a browsing observation becomes part of a research argument.

Prepare a release only after its intended content and access scope are approved. Preserve the relationship between source artifacts, package metadata and the exact deposited version.

Use observations to locate stale or unavailable components. Pass action to the responsible operator or component; a status observation is not itself a repair or a change to the corpus.

Inspect imported person records in their snapshot context before using them in reconciliation. Preserve source identifiers and distinguish the imported description from an accepted MODAVIS actor identity.

Check the transfer structure first, then stage its content with source identity intact. Structural success is a prerequisite for subsequent interpretation, not a substitute for that interpretation.

Review a proposed normalized value alongside the literal source. When two similar names are proposed as one entity, retain the contextual evidence and the option to leave the link unresolved.

Use the authorized projection path for accepted decisions. Keep the policy version, input bindings and resulting receipt together so that a projection can be interpreted and replayed.

Begin with identified document bytes and retain precise page or text selectors. A candidate assertion is most useful when another researcher can locate the passage that supports it.

Compare candidate places against the name, historical context and provider evidence. Keep precision and ambiguity visible rather than using the highest-ranked coordinate as an unqualified fact.

Treat a language result as evidence about a text span. Short labels, mixed language and historic spelling may warrant qualification or abstention before a downstream language-dependent process runs.

Check extracted authors, dates and pagination against the citation wording. Preserve unknown fields and separate a parsed reference from a verified match to an external bibliographic record.

Use a bounded, authorized source request and retain the evidence behind each proposed fact. Review the result before promoting it into an institution or virtual-instrument record.

Ask how the evidence supports a particular claim and whether sources depend on one another. Keep the assessment’s scope with its output instead of ranking an entire source as universally trustworthy.

Inspect the score or MIDI input and any pitch-control qualifications before interpreting its range. Use the output as evidence about the encoded material, not a direct measurement of sounding hardware.

Review mask alignment and what the selected region actually represents. Assigning an organological class is a further interpretative step that should retain its evidence and status.

Retain the photograph bundle, reconstruction settings and camera relationships with the point cloud. Establish scale and fitness for the intended analysis before using geometry in another modelling workflow.

Plan a documented session or open an existing signal for analysis. Preserve original takes, selection and processing settings alongside any exported figure, sample or VAO package.

Use the map to find instruments and geographic relationships, then inspect the underlying evidence. Do not infer more coordinate precision from the display scale than the source supports.

Inspect the package and supported capabilities before drawing conclusions from an experience. Record which runtime and resources were actually used when describing an interaction or playback result.

Review OCR against the retained crop and literal image content. A suggested corpus match can guide attention, but the accepted transcription should remain a documented editorial choice.

Bind an auralization to its MIDI, virtual instrument and rendering choices. Keep the resulting audio distinct from an in-situ recording of the physical instrument.

Read a listening position and synthesized bell sound in the context of the pilot’s model assumptions. Separate the bell’s documentation, the synthesis method and the urban propagation representation.

Use the report to inspect the relationship between measured dimensions, procedural geometry and passive modes. Do not extend an eigenmode result into an untested claim about active sound production.

Use the architecture to frame research on geometry, material interpretation and room acoustics. Identify which proposed steps need implementation or independent field evidence before claiming an end-to-end result.

Begin with the demonstration’s own instructions and declared inputs. A reproducible example helps assess a component boundary without implying production deployment of the whole ecosystem.

Inspect a pinned release before selecting resource groups and materializing them. Retain the client version and verification results with the local output.

Check the Unity runtime, supported contract and required profile before designing an experience. A successful geometry import alone does not establish playback or XR compatibility.

Use inspection and verified geometry materialization for a documented package. Keep unsupported runtime behaviour explicit when transferring from a playable VAO into a modelling environment.

Use the reference tools with the matching standard release and fixtures. Distinguish their contract checks from the capabilities and release numbering of the separate VAO CLI.

Read this library in the context of OrgRec’s package and validation workflow. Record the containing application release when its behaviour forms part of a reproducible export.

Pin the contract and relevant profiles before implementing a reader or writer. Use versioned fixtures and conformance rules, then separately assess the scientific claims carried by the object.

Start with the identities and evidence relationships required by a research question. Validate the graph against the applicable versioned constraints while retaining the interpretation that motivates it.

Look up a concept without discarding the source’s original wording. Retain language, source identifier, mapping status and the exact reference release used.

Choose an adequate release distribution and define the unit of analysis. Keep instrument identities, source accounts and stop occurrences distinct when counting or comparing records.

Consult the deposit’s access conditions and exact version before planning a review. Do not describe this preservation package as the restricted counterpart of a different public release.

Use the index to discover third-party methods and repositories, then consult each project’s own documentation. The index is a dated research resource rather than a guarantee of current software maintenance.

Compare source focus and documentation practices before selecting a corpus. Use the catalogue to understand coverage rather than treating every portal as an interchangeable witness.

Use the comparative corpus to situate a digitization approach among related projects. Preserve the distinction between a project description and an independent evaluation of its outcomes.

Locate a method family, then inspect its assumptions and evaluation scope. A catalogue entry is a starting point for reading the underlying study, not a universal performance ranking.

Treat the corpus as a documented research reference whose public access remains unverified here. The separately available inventory can support discovery without implying that the timbre material is downloadable.

Check which products or source materials were available in the audited state. A listing and an availability observation do not grant redistribution rights to a sample library.

Open the exact object release and inspect its declared resources and configuration. Relate recordings, geometry and pipe evaluation to their own acquisition or modelling basis.

Use the fixed package as the starting point for comparison. Keep the instrument’s documented history distinct from the date and version of its digital representation.

Inspect the cinema-organ package’s own capabilities and sources before comparing it with another reference object. Preserve the package identity in any derived playback or analysis.

Follow the case’s relationship to bellcast and its acoustic assumptions. Refer to the documented study without presenting an unverified deposit as a confirmed public download.

Use the case to examine how a mechanical information carrier becomes an interpreted event sequence. Keep that interpretation distinct from the instrument’s reed and wind behaviour.

Read the repository as a preceding deposition toolkit and consult its own instructions before reuse. Its presence in the project history does not imply that it owns current MODAVIS release approval.

Use the historical framework to understand replayable heritage processing and project-state capture. Check its own implementation boundaries before adapting a workflow to current MODAVIS contracts.

Trace the division between a web workflow and delegated computation. Preserve the job inputs, processing state and resulting artifacts when assessing a historical HPC-supported example.

Use these references to understand how earlier ingestion and compute workflows developed. Do not substitute an old helper for a current component merely because the names are similar.

Discover related outputs through the community, then move to the exact version record for citation, files and rights. Community membership does not impose a single license on all resources.

Find instrument packages and related VAO work, then inspect their individual manifests and releases. Curated discovery and mathematical file verification remain separate responsibilities.