Add the desc
tag to a question to provide alternative question text to reports. This applies to both question and table widgets, as well as blocks and loops.
Syntax
desc: Question description here
Examples
Basic
In the example below, without a desc
tag, Q54 would display the text "Incredibly verbose question text here" in reports. In many cases, these incredibly verbose phrases are cut off and only partially display. With the desc
tag in place, we have now simplified the text to show as "Technician Type" instead. This example also makes use of the desc
element decorator.
54. Incredibly verbose question text here. desc: Technician Type type: radio 1. Non-contract pay-by-the-hour {desc: By the hour} 2. Non-contract flat fee per visit {desc: Flat fee} 3. Contractually obligated {desc: Contract} 4. Near shore outsourced flat fee based {desc: Near shore} 5. Incredibly verbose option here {desc: Other}
The Topline tiles for Q54 would appear as follows, with and without inclusion of the desc
tag and decorators.
With desc tag and decorators |
Without desc tag and decorators |
---|---|
|
|
Blocks
This example shows the benefit of adding the desc
tag to a question within a block or a loop. Often the question text in a block is too long to display well in reports. The report label then becomes unhelpful since the key content that distinguishes this question from others may not be visible.
Reports also display each iteration of a block as a row in a rolled up data point (for example, a grid) in Toplines. However, in all other report types and in data exports, the label is a separate column and appears like a single question, detached from the original question text. Remember, reporting labels default to only showing the piped text. In the example below, only the word "Brand X" would be displayed, instead of "Likelihood to recommend Brand X," then "Brand X" would be repeated, in multiple columns, depending on the number of blocks in the programming. "Brand X" alone is not unique enough to tell the researcher or client which question they are looking at, so adding a desc
tag to the block allows for multiple data points in reports to have distinctive labels. This proactive thinking and labeling really helps the client and researchers involved in the project.
Example of a block with a desc
tag:
Code block | Example of Topline report | ||
---|---|---|---|
10. What is your awareness of the following brands? type: radio table 1. Unaware 2. Aware, never purchased 3. Purchased rows: 1. Brand X 2. Brand Y 3. Brand Z block: <<END 11_%%ID%%. On a scale of 1 to 7, how likely are you to recommend %%TEXT%%? desc: Likelihood to recommend %%TEXT%% type: radio hscale: y headings: Highly Unlikely, Highly Likely optsfrom: series [1..7] END list: T10.rows {if anyChecked($Q10R[id],3)} |
|
Example of a block without a desc
tag:
Code block | Example of Topline report | ||
---|---|---|---|
10. What is your awareness of the following brands? type: radio table 1. Unaware 2. Aware, never purchased 3. Purchased rows: 1. Brand X 2. Brand Y 3. Brand Z block: <<END 11A_%%ID%%. On a scale of 1 to 3, how likely are you to recommend %%TEXT%%? type: radio hscale: y headings: Highly Unlikely, Highly Likely optsfrom: series [1..3] END list: T10.rows {if anyChecked($Q10R[id],3)} |
|
Example of a block without desc
tag and rollup: n
:
Code block | Example of Topline report | ||
---|---|---|---|
10. What is your awareness of the following brands? type: radio table 1. Unaware 2. Aware, never purchased 3. Purchased rows: 1. Brand X 2. Brand Y 3. Brand Z block: <<END 11B_%%ID%%. On a scale of 1 to 3, how likely are you to recommend %%TEXT%%? type: radio hscale: y headings: Highly Unlikely, Highly Likely optsfrom: series [1..3] END rollup: n list: T10.rows {if anyChecked($Q10R[id],3)} |
|
Comments
0 comments
Please sign in to leave a comment.