Using existing Odin scripts

Use the QubeSurvey extension to inspect, check and test an existing Odin questionnaire. You can upload a version to run on QubeSurvey, or use local checks and tests before running the script on NIPO Fieldwork System. For a new QubeSurvey survey, follow Getting started with QubeScript.

Filenames

The NIPO convention is a DOS-style filename without an extension, with the leafname ending in q, for example p1234q. QubeSurvey uses the .odin suffix so VS Code can recognize the language automatically. For editing and uploading in QubeSurvey, save a copy as p1234q.odin. The suffix is an editor integration convention; it does not change the Odin source. Keep the extensionless name when preparing the script for NIPO Fieldwork System.

Open and check the script

Install the QubeSurvey extension from the VS Code Marketplace (or follow the extension guide). Open the .odin file in VS Code. Review the reported errors and warnings before testing. The extension also has commands for Odin data positions, question renumbering and translation sections.

Test locally

With the Odin file active, run QubeSurvey: Run Interview. Use invented answers to check the expected questions, routes and endings. QubeSurvey has its own Odin parser and runtime, so test the script in the specific host where it will run. The extension can navigate to a *MERGE file, but merged runtime execution is not supported.

Upload a version to QubeSurvey

Run QubeSurvey: Open in QubeSurvey (online) and select a Script where you have edit access. The command uploads the current .odin source as a new immutable version. Open that version’s Test view and check its behavior; use the reviewed version when creating a Run. Continue with Getting started for the shared team review, fieldwork and export steps.

Use the extension before NIPO

The extension can help audit and test Odin source before you run it on NIPO Fieldwork System. It does not deploy the script to NIPO. Test it in the NIPO version you intend to use, since host behavior can differ. See the Odin reference for supported commands and host differences.

Before exchanging a script, check these in both hosts:

  • Routes and conditions that depend on an earlier answer.
  • Other and exclusive answers, attached open text and *BUT buttons.
  • Bounds: *RANGE, *MIN/*MAX on multiple answers, and *LINE limits.
  • Repetitions, *FIELD layout and mention order.
  • Endings and the code each host records.
  • Export columns and field widths.

The reference’s Differences from NIPO Odin section lists what is known to differ, including commands QubeSurvey recognises but does not execute.