Review and update the questionnaire in the shared sheet.

Current questionnaire contract

Local IDs, presentation order, and 5D-ASC item numbers are different things.

An AXP item_id is a stable app and data key. It is not a 5D-ASC item number and it is not a factor number. For example, q2 maps to source item 8, not source item 2.

What controls participant order

• q0, q1, and q_context are fixed on the combined entry step; q_free, when present, is fixed at the end.
• With randomize_question_order=0, active sliders appear in their physical row sequence inside the selected language block.
• With randomize_question_order=1 on the English q0 row, the app shuffles those slider rows for the participant. It does not shuffle the fixed entry or final items.
• The numeric order column is compatibility metadata, not a second ordering mechanism. Editing it alone does not change the displayed sequence.

How the 42 AXP ASC items map to German and Spanish

The AXP ASC crosswalk selects 42 non-consecutive items from the original 94-item 5D-ASC. It preserves each selected source number: q2 → 8, q3 → 9, q4 → 12, q5 → 14, and finally q43 → 94. Therefore, “8 through 94” means the lowest and highest selected source numbers, not that AXP contains all 87 items in that interval.

The published Spanish questionnaire explicitly identifies itself as a translation of the Hasler/Cahn English version and credits the original German scale to A. Dittrich, D. Lamparter, and M. Maurer. The source number in the AXP crosswalk therefore identifies the same numbered item across the German source lineage and Spanish translation; the wording changes by language, while the source number is retained. The scale_id is separate: it assigns an AXP item to a scoring factor and does not determine its source number or presentation order.

Download the complete 42-item numeric crosswalk

Sources: the published Spanish 94-item adaptation; bibliographic record for Dittrich, Lamparter, and Maurer’s 2006 German 5D-ABZ manual; and a current scholarly article describing the 94-item original German version and its German/English supplement.

Google Sheets workflow

1. 1
   Open the current shared questionnaire tab.

   Confirm you are working in the intended version before changing anything.

2. 2
   Make the content change.

   Update wording, translations, options, or structural rows in the stacked table. Keep the same columns across language blocks.

3. 3
   Keep stable questions stable.

   Keep the same item_id when the question is still the same underlying question, and keep scorable English rows mapped through canonical scale_id values.

4. 4
   Update comparison_tokens when comparison eligibility changes.

   Do this only when an induction or dose should map to a stable peer bucket. New questionnaire options do not automatically become comparison options.

5. 5
   Let the sheet enforcer sync the tab.

   If the Google Sheets Apps Script is installed, it groups existing rows into language blocks, preserves each block’s existing row sequence, keeps the expected header shape, and applies the questionnaire formatting. It does not sort questions using order.

6. 6
   Create a new dated tab when the version truly changes.

   Use a new dated version when the questionnaire definition should be tracked separately.

7. 7
   Open the running survey once if you want confirmation.

   That is enough to see whether the latest sheet version was picked up. For response logic or scoring changes, complete one submit path and confirm that feedback renders.

8. 8
   Tell download users if files may change.

   If the change affects the meaning of later exports or codebooks, let OSF users know what to expect.

What the Google Sheets enforcer does

• If installed, the Apps Script runs on edit and is also available from the AXP Sheet menu as Sync questionnaire sheet.
• It keeps the questionnaire tab in the expected header order and groups rows into language blocks while preserving the existing row sequence within each block. It does not sort questions by the numeric order field or by English row order.
• It colors and formats rows from the English structural metadata, including active state and scale_id.
• It checks that explicit induction_method_N, dose_options_N, and dose_label_override_N triplets are structurally complete before syncing.
• It helps keep the sheet structurally valid and readable, but it is not a separate publish step. The running survey still reads the questionnaire from the sheet itself.