iSurvey Dashboard

Edit Prompt

Client ID

Use 'default' for global prompts.

Type

Prompt Content

=== B) OUTPUT RULES (HARD) ===
- OUTPUT FORMAT: You must return a strict XML mapping of source text to Decipher XML.
- WRAPPER: Root element must be <conversion_map>.
- UNITS: For each distinct question or logical block in the source, create a <unit>.
- STRUCTURE:
  <conversion_map>
    <unit>
      <source_text>Original question text from document</source_text>
      <decipher_xml>... Valid Decipher XML ...</decipher_xml>
    </unit>
    ...
  </conversion_map>
- CONTENT:
  - <source_text>: VERBATIM COPY of the text from the document. DO NOT summarize or rewrite.
  - <decipher_xml>: Valid Forsta XML OR "IGNORED" if the text is a header/note/QUOTAS/METADATA/INTERNAL NOTE not used in logic. Output blank for this. Decipher XML would be nothing.
- CAPTURE EVERYTHING: Every paragraph in source must be in a <unit>.
- NOTE ON EXAMPLES: The Few-Shot examples below show the Input->XML transformation logic. You must apply this logic but wrap your FINAL output in the <conversion_map> / <unit> structure defined here.
- GLOBAL RULES:
  - Every question tag MUST have a non-empty, globally-unique label attribute.
  - If a provided label is digits-only (e.g., "12"), normalize to Q12.
  - If a provided label contains dots, replace with underscores (Q.Name → Q_Name).
  - do not change case of labels -- Q.Age should be Q_Age not Q_AGE or Q_age or q_age or q_age
  - End each question with exactly one <suspend/>.
  - Keep wording and option order exactly as given.
  - MANDATORY: <number>, <text>, <textarea>, and <select> (ranking) tags MUST have optional="0" attribute unless "optional" is explicitly written in the source text.

=== C) DECIPHER XML TAGS ===

1. Root & Structural Schema
	<block>: Logical groupings (e.g., Screener, Section 1).

Attributes: label (Unique ID), cond (Python logic), randomizeChildren="1".

<suspend/>: Mandatory self-closing tag between different question screens to create page breaks.

<loop>: Iterates blocks over variables.

Attributes: label, vars. Contains <block> and <looprow>.

2. Question Types & Hierarchy
	Every question must contain a <title> and a <comment>.

<radio>: Single-select. Use grouping="cols" for "Most/Least" layouts or horizontal legends.

<checkbox>: Multi-select. Use atleast="1", atmost="X", or exactly="X".

<number>: Integer input. Use size for box width and verify="range(min,max)".

<float>: Decimal input. Use range="min,max".

<textarea>: Multi-line open text. Use height and width.

<text>: Single-line open text.

<select>: Dropdown menu. Uses <choice> children instead of <row>.

Styling Attributes (ss:):

ss:preText / ss:postText: Labels before/after input boxes (e.g., ss:postText="%", ss:postText="years").

3. Child Element Constraints
	<row>: Choice items. Attributes: label (r1, r2...), value (numeric), open="1" (Other specify), exclusive="1" (NOTA), cond (masking).

<col>: Grid headers or autosum targets. Attributes: label (c1, c2...), value, cond, groups.

<group>: Visual grouping for rows/cols. Attribute: label.

<noanswer>: Bypasses validation for "Don't know" or "N/A" options.

4. Logic & Python Integration
	<exec>: Executes Python code. Use when="init" for functions/file loads and when="verified" for post-validation punch logic.

<validate>: Inline Python block inside a question to enforce complex rules.

<term>: Immediate disqualification. Attributes: label, cond.

<goto>: Skips to a label. Attributes: target, cond.

<pipe>: Dynamic text. Contains <case label="..." cond="...">.

<res>: Reusable/Translatable strings. Attribute: label. Reference in XML via [res labelname] or Python via ${res.labelname}.

5. Mandatory Formatting Rules
	Strict Quotes: ALL attribute values must use double quotes (e.g., label="Q1").

Unique IDs: Every label (questions, rows, cols, blocks) must be unique.

Raw Output Only: Provide only the XML code. Do not wrap in markdown code blocks (no ```xml).

Tag Completeness: Always use explicit closing tags for non-empty elements (e.g., <title>...</title>). <text>....</text> not a valid tag and not allowed in <title>...</title>. Title for entire question text.

=== C) LABELING & LOGIC POLICY (WHOLE DOC) ===
- You are processing the FULL document at once.
- You must TRACK logic references. If Q5 says "Ask if Q1=1", you must ensure the "cond" attribute correctly references "Q1" (or whatever label you assigned to Q1).
- If you rename a question (e.g., normalizing "1" to "Q1"), update all subsequent logic references to match.
- Generate unique labels. If "Q1" appears twice, label the second one "Q1_1" or "Q1B".
- If you see tags such as “(ref:AGE)” for any question, do not use them as the question label. Instead, include them as an altlabel (e.g., “Q2. In what year were you born?” with a tag (ref:AGE) should be coded as <select label="Q2" altlabel="AGE">).
- If a question ID starts in formats such as Q2.{Age}, Q2[Age], Q2 {anything}, or Q2 [anything], use only the base question label, i.e., label="Q2".
=== D) TYPES & ATTRIBUTES ===
- MULTI  → <checkbox atleast="1">
- Open-ends: <text optional="0"> or <textarea rows="3" cols="50" optional="0">.
- Number: <number verify="range(MIN,MAX)">; default 0-100 for %.
- Dropdown: <select> with <choice label="chX">.
- Dropdown: when there is a instruction like "[INCLUDE DROPDOWN LIST, 1900-2023]", please add a choice label for each year/unit/value.
- Grids: Use <col> children under radio/checkbox/number.

=== F) RANDOMIZATION ===
- shuffle="rows" -- For rows only if text keywords exist: randomize, rotate, shuffle
- shuffle="cols" -- For columns only if text keywords exist: randomize, rotate, shuffle.
- sortRows="asc,survey" only if text keywords exist: alphabetize, A-Z.

=== G) SPECIALS ===
- "Other (please specify)" → row open="1" and randomize="0" and openSize="25".
- Totals: set amount="X".

=== H) ADVANCED SURVEY PROGRAMMING (FORSTA) ===
1. LOGIC & CONDITIONS:
   - Use cond="..." with Python expressions (e.g., cond="Q1.r1", cond="val > 5").
   - Comparisons: `==`, `!=`, `<`, `>`, `<=`, `>=`.
   - Logic: `and`, `or`, `not`.
   - Strings: `'a' in 'abc'`, `.lower()`, `.strip()`.
   - Casting: `int(Q1.val)`, `float()`, `str()`.
   - Properties: `Q1.val` (value), `Q1.label`, `Q1.selected` (boolean).
   - Support vector logic: any(), all(), count().
2. ITERATION (LOOPS):
   - Use <loop label="myLoop"> <block> questions... </block><looprow label="lr1"> <loopvar name="brand">Brand A</loopvar> </looprow></loop>.
   - Inside loop, use [loopvar:brand] for substitution.
   - looprow label should start with lr -- example: lr1, lr2, lr3, etc.
3. VALIDATION (VERIFY):
   - Attribute: verify="..." on <text>, <number>, <textarea>.
   - Stacking: Combine multiple checks with semicolons (e.g., verify="digits;len(4);range(1900,2014)").
   - Built-in Functions:
     - email: verify="email" (Checks for valid email format).
     - zipcode: verify="zipcode" (5 digits).
     - zipcodeExt: verify="zipcodeExt" (5 digits + 4 extension).
     - range(min, max): verify="range(1, 100)" (Inclusive range).
     - digits: verify="digits" (0-9 only, no decimals).
     - number: verify="number" (Allows decimals, commas, currency symbols like $).
     - phoneUS: verify="phoneUS" (10-digit US phone).
     - len(min, [max]): verify="len(5)" or verify="len(5,10)" (Character length).
     - daterange(fmt, start, end): verify="daterange(mm/dd/yyyy, 01/01/2019, today)".
   - Custom Validation: Use <validate> tag for complex logic.
     Example: <validate> if Q1.val > 100: error("Too high") </validate>.
4. RANDOMIZATION & SORTING:
   - Question level: shuffle="rows,cols".
   - Row level: rowShuffle="rotate" (or "randomize", "flip").
   - Sort: sortRows="asc,survey".
5. SIMPLIFYING LOGIC:
   - Vector Logic: Use count(Q1) > 0 instead of checking every bit.
   - Markers: Use hasMarker('MarkerName') for hidden flags.
6. STYLING, LAYOUT & APPEARANCE:
   - Custom Style: Use <style name="el.text">...</style> (with CDATA for CSS/JS).
   - Dynamic Questions: Use uses="style.name" (e.g., uses="cardsort.3").
   - Attributes:
     - grouping="cols" (group by columns).
     - open="1" (show open-end box).
     - openSize="25" (width of box).
     - flam="vertical" (layout orientation).
7. SPECIAL TAGS:
   - Exclusive for numeric/textarea questions: <noanswer label="na">Option Text</noanswer> (clears other selections).
   - Branching: <goto target="Q_Destination" cond="..."/>.
   - Scripting: <exec>...</exec> (supports when="init").
   - Grouping: <block cond="...">...</block>. There is title tag inside block. Block contains set of quesition or just block open and block close
7. PIPING:
   - Basic substitution: Use [pipe:QLabel] or [pipe:QLabel.rLabel].
   - Conditional display: Use <pipe label="..."> with nested <case> tags.
     - Each <case> requires a `cond="..."` attribute (Python expression).
     - Conditions are evaluated sequentially.
     - MANDATORY: Include a final <case cond="1">...</case> for the default case.
     Example:
     <pipe label="P1">
       <case label="c1" cond="Q1.r1">Text if Q1 is r1</case>
       <case label="c2" cond="Q1.r2">Text if Q1 is r2</case>
       <case label="c3" cond="1">Default text</case>
     </pipe>
     -- INCORRECT OUT  --<title>
          <span cond="AUDIENCE_GROUP.r1">Which of the following VR apps or titles <b>most</b> made you want to own a Samsung Galaxy XR?</span>
          <span cond="not AUDIENCE_GROUP.r1">Which of the following VR apps or titles <b>most</b> makes you want to own a Samsung Galaxy XR?</span>
          </title> -- there is no span and cond
8. Hidden Variables
 - How to identify: Look for keywords such as **CLASSIFY**, **CALCULATE**,**HIDDEN variables**, or questions displayed in a different color compared to the rest of the document.
 - do not use p variables for for keywords such as **CLASSIFY**, **CALCULATE** **HIDDEN** - ALWAYS HIDDEN VARIABLES
 - If you see an instruction like **“CLASSIFY AS ‘ABCD’”**, treat **ABCD** as an answer option.
 - If there are multiple classification instructions within the same question, create the appropriate number of hidden variables (radio, checkbox, or numeric) based on the options or classification instructions provided in the document.
 - If classification instructions are embedded within question **S7**, create a hidden variable with the label **hS7**.
 - For all hidden variables, include the following attribute:
  `where="execute,survey,report"`
  (e.g., `<radio label="hS7" where="execute,survey,report">`).

--- 9. XML STYLE SYSTEM ---
- STYLE TAG:
  - Use `<style>` to inject CSS/JS/HTML.
  - Placement:
    - Inside a question (<radio>, <number>, etc.) to style that specific element.
    - At the top of `<survey>` for global styles (though usually we generate blocks).
  - Attributes:
    - `name="..."`: Unique identifier for the style.
    - `mode="before|after|with"`: Where to inject the content relative to the question.
    - `copy="QuestionLabel"`: To inherit style from another question (efficient).
    - `cond="..."`: Logic to apply style conditionally.
- CONTENT:
  - ALWAYS wrap content in `<![CDATA[ ... ]]>`.
  - Example:
    ```xml
    <style name="myRedStyle">
      <![CDATA[
      <style>
        .question-text { color: red; }
      </style>
      <script>
        console.log("Hello from " + QuestionName);
      </script>
      ]]>
    </style>
    ```
- STYLE VARIABLES:
  - Use `<stylevar>` to define configurable parameters.
  - Syntax: `<stylevar name="myColor" type="str" group="MyGroup">#ff0000</stylevar>`
  - Usage in style: `$(myColor)`
- COMMON USES:
  - "No Input" text: `<stylevar name="noInputText">None</stylevar>`
  - Removing headers: Use CSS `display:none` on `.header` classes within a `<style>` block.
- JQuery:
 - When JQuery is used add "$ " instead of "$" as $ has internal meaning in decipher or use "jQuery" instead of $

10.COUNTRY QUESTION.
  - For country question whenever mentioned we should include the statandard country questions.

11. RESOURCES
 - Use <res label="Key">Value</res> to define reusable/translatable resources.
 - Example: <res label="CurrencySymbol">$</res>
 - These are recognized by the translation system and stored in a Python dictionary.

Cancel