When creating quotas in the survey, there are several standard tags associated with the quota setup. These tags layout both the design and the functionality that will be used. Before building the quotas, each of these should be understood.
Tags
The following tags are commonly used with quotas.
| Tag | Description |
|---|---|
applyif |
When the tag
apply if is present, respondents must first meet the condition specified in order to punch a quota bucket. If it is not met, the respondent simply skips over the quota, without regard for whether or not they qualify for any open quota bucket, or none at all. When this tag is not present, all respondents are subject to the quota. |
audience sheet |
New for r9.2; can be applied as a tag or decorator on a quota variable created with
type: quota to trigger the creation of an audience quota instead of a regular quota. Quotas with this tag will be placed in the Audience Quotas applet instead of the Quotas applet.The
audience sheet tag/decorator requires an audience sheet as input. |
audience type |
New for r9.2; can be included with the
audience sheet tag to organize audience quotas into groups within the Audience Quotas applet. If you apply the audience type tag to a quota variable, all audience quotas with the same "type" (e.g., REP) will be grouped together in the same table. Without the audience type tag are grouped together in one large table, with a single field for establishing the target "N" and variance.The
audience sheet tag can accept user-created strings as groups, or use the following built-in groups:
Note that group names can be either uppercase or lowercase. |
build_quotas_from |
Similar to quotas: y, allows Survey Programmers (SPs) to create quotas from hidden variables automatically by placing the tag directly on questions using type: uszip5. |
create_quota |
When added to a question, |
crosslist tile |
In the case of a quota widget (type: quotas question) utilizing a crosslist, the resulting tile on the Quota Manager will be a crosslist quota. To disable this functionality and have the tile display all options as a typical quota, include this tag and set the input to 'n'. |
defer if none |
Useful for allowing respondents to term at a later point in a survey rather than ending the survey immediately if they do not qualify for any quota buckets. When applied to a quota widget, this tag allows the SP to specify a page label so that the respondent may continue answering questions until they reach that page. |
defer if over |
Useful for allowing respondents to term at a later point in a survey rather than ending the survey immediately if their potential quota buckets are full. When applied to a quota widget, this tag allows the SP to specify a page label so that the respondent may continue answering questions until they reach that page. |
ifnone |
When a respondent fails to qualify for any existing quota bucket, they will be routed to the page with the label specified with this tag. If omitted, respondents are routed to a system-generated ending page. Also accepts the alias 'NEXT' as input, which allows respondents to continue despite failing to qualify, and setting them to status "C" if they complete the remainder of the survey. |
ifover |
When a respondent only qualifies for buckets which are at or over the maximum specified, they will be routed to the page with the label specified with this tag. If omitted, respondents are routed to a system-generated ending page. Also accepts the alias 'NEXT' as input, which allows respondents to continue despite failing to qualify, and setting them to status "C" if they complete the remainder of the survey. |
Used with type: quotas and selectby; specifies the maximum number of quota groups that a respondent may be assigned to, if qualified. If this tag is not used, a respondent can only be assigned to one group. |
|
| If using a list or sheet, this specifies the location of the options to be used. | |
Specifies the description that appears in reports for quotas generated when using quotas: y tags on questions. |
|
qualified value |
Specifies the option that should be punched, instead of relying on selectby to evaluate option conditions or counts. It can be thought of as a cvalue for quotas.
|
quotabase |
Specifies the criteria that must be met to increment counts for this quota. |
quota chapter |
In the case of a quotas: y quota, specifies the chapter in which the derived quota variable should appear. If unspecified, quotas appear in the Quota variables sub-chapter of the Appendix chapter.
|
quota suffix |
Overrides the default "_QUOTA" suffix appended to the quota variables created with |
quota tracking variable |
The |
Specifies how respondents are assigned their quota group(s) when they may qualify for more than one. If left undefined, quotas default to selectby: condition. |
|
status if over |
Specifies an alternate status if respondent only qualifies for quota buckets which have met or exceeded maximum values entered in the Quota Manager. If omitted, defaults to "Q." |
|
The |
|
term text |
Provides a custom option text in reports for the system variable disp, and can be applied to a quota widget. |
track qual |
A tag which accepts 'y' (yes) or 'n' (no) input that automates the creation of a multi-select survey variable which tracks all quota buckets for which a respondent could have qualified. |
Specifies whether to include the quota in the Excel output file that is generated by the translation management tool. Quota variables are set to translate: n by default. To force a quota translation, add translate: y to the quota variable.
|
'selectby' with quotas
The selectby tag is intended to work with type: quotas and quotas: y. However, it cannot be used with quotas: y on software versions prior to r8.0. The selectby tag is only relevant in cases where a respondent qualifies for more than one quota group. If they qualify for more than one, the group must still be below the maximum quota cap in order to be evaluated by the selectby method(s) selected.
If weights are being used in a quota and the group with the highest weight is full, the respondent will then roll over to the next highest weight for which they qualify (perhaps again and again) until an open group is found. This selection process should be thoroughly reviewed with the client.
See the full selectby article for more information on all available inputs and applications for this tag.
Tip! You can use more than one method concurrently to create a tiered approach, such as selectby: weight, counts. This would select options first by highest weight, then lowest counts (if more than one option had the same weight).
Comments
0 comments
Please sign in to leave a comment.