Analysis

Codebook view and open exchange

View complete code meaning and exchange current codebook snapshots through CSV, XLSX, QDC, or QDPX.

Implemented task

Public task

Open the Codebook panel.

Expected outcome: Code meaning, hierarchy, sets, history, operations, and open exchange remain versioned and reviewable.

ApplicationRequires Sign-in, Existing project

Declared product contract

Inputs and task boundary

Inputs

  • The current project codebook
  • Optional CSV, XLSX, QDC, or codebook-subset QDPX import

Input constraints

  • Import uses preview, conflict and loss acceptance before commit.
  • This is a codebook snapshot boundary, not complete-project QDPX round-trip.

User actions

  1. Open the Codebook panel and inspect current meaning and structure.
  2. Preview an import or choose an export format.
  3. Resolve conflicts or losses before committing an import.

Outputs

  • A current codebook view or a validated codebook snapshot exchange.

Artifacts

  • CSV codebook
  • XLSX codebook
  • QDC codebook
  • Codebook-subset QDPX

Decision boundary

Where it fits

  • Inspecting or exchanging the current codebook with explicit loss boundaries.

Outside the boundary

Where it does not fit

  • Complete-project QDPX migration.

Current scope

Limitations

  • This exchanges the current codebook snapshot; complete project QDPX round-trip remains a separate M6 capability.

Verification

Product proof

journey

proof.m2-codebook-workspace

Open artifact
Verified
Review due
Expires
  • Code meaning, hierarchy, sets, merge, split, and history are available in the main workspace.
  • Large codebooks remain virtualized and keyboard-operable.

Failure boundary: Complete-project QDPX exchange remains outside the codebook snapshot boundary.

journey

proof.m10-refi-codebook-handoff

Open artifact
Verified
Review due
Expires
  • A local REFI-QDA validator result remains browser-only until the user selects a project and requests the official codebook preview.
  • The exact formal import preview renders both REFI-QDA codes and the required non-codable-group loss while PostgreSQL contains zero project codes and zero codebook import audit events.
  • The final import stays disabled until the user accepts the REFI-QDA conversion loss.
  • Only a digest-bound final confirmation creates two project codes and one codebook-imported audit event.
  • The audit preserves the REFI-QDA validator tool ID, version, result ID, input fingerprint, source loss, and free-tool acquisition lineage.

Failure boundary: This journey proves the REFI-QDA validator to codebook-import adapter in writable single-user mode; complete-project QDPX migration, multi-user role recovery, template lineage, and sample lineage require their own journeys.

external standard

proof.m10-open-standard-formats

Open artifact
Verified
Review due
Expires
  • A claim-driven inventory applies independent standard checks only to implemented QDC/QDPX-codebook, WebVTT, DOCX, and XLSX claims.
  • Both QDC and the QDPX codebook projection validate against the vendored official REFI-QDA Codebook 1.0 schema.
  • WebVTT and OOXML fixtures pass independent parsers that do not call the product import parsers.
  • Malformed QDC, WebVTT, and DOCX failure injections fail closed.
  • Complete-project QDPX, saved queries, report builder, and all partial/planned capabilities remain explicitly unproved.

Failure boundary: This proof covers implemented open-format boundaries only; it does not certify complete-project QDPX, third-party round trips, saved queries, report builder behavior, or a production service level.

OpenVerbatim is an open-source (Apache-2.0) qualitative data analysis platform for coding and analyzing interview transcripts. AI-suggested codes stay marked as suggestions until a human reviewer confirms or rejects them, and every decision is kept in an audit trail. The full feature set is available when self-hosted; there is no paid feature wall.