Managing Segmented Questions
- 3 Minutes To Read
- Print
- DarkLight
Managing Segmented Questions
- 3 Minutes To Read
- Print
- DarkLight
Article Summary
Share feedback
Thanks for sharing your feedback!
In the Questions section you define how each question is segmented. Recall that in our elector data sample, segment 1 contained data regarding an elector’s "membership type", while segment 2 contained data regarding an elector’s “geographic location.”
Now, you will define which elector segments can access each question on the ballot.
Understanding and Using Segment Restrictions
As general rule of thumb, you can think of segmentation this way: if you select multiple segment 1s for instance, these selections represent an “OR” function. Electors will need to meet one of the criteria selected in segment 1 to access the question.
An “AND” function is used between segment 1 and segment 2. So if you specify "Retired" for segment 1 and "Midwest" for segment 2, electors will need to meet one of the criteria selected in segment 1 and one of the criteria selected in segment 2 to access the question.
Before segmentation can be configured for any question, the electors with defined segments must exist in the Voting Systems's elector list. For more information about managing segmented electors, please see Managing Segmented Electors.
To select multiple segment 1s or multiple segment 2s, hold down the “Ctrl” or “Command” key while left-clicking the desired segments.
Character limitations in segmentation fields
When selecting multiple segments 1s or multiple segment 2s, the cumulative number of characters of the selected segments cannot exceed 255, including semicolons and spaces. Note that semicolons are implied when selecting multiple segments: for example, selecting both "Associate" and "Retired" from the segment 1 menu results in the question being restricted to "ASSOCIATE;RETIRED", a total of 17 characters.
If your segment names are too long, consider using abbrevations or acronyms to avoid going over the character limit. For example, a segment named "FACULTY OF ARTS AND SCIENCES" could be renamed "ARTS&SC" to use fewer characters. If you have a large number of segments, consider consolidating multiple segment into one, if possible.
For more information about chacter limitations, visit the FAQ article.
The example above is for a “Retired Representative” question, which relates to all retired members within the organization, regardless of their geographic location. Access will be restricted to all "Retired" electors (segment 1), while adding no restrictions regarding geographic location (segment 2). Thus, all electors that are grouped into the “Retired” segment will have access to this question regardless of their geographic location.
Click the Save button after you’ve filled out the details of the question before proceeding onto question options or before moving onto creating additional questions.
Once you have completed one question, you can create additional questions with other segmentation restrictions, such as questions for only "Northeast" electors, or for only "Northwest Associate" electors, or for "Student and Regular" electors, etc.
Specifying Segments in Description Fields
Optionally, users may wish to specify and inform electors about their specific segment(s) for transparency or other reasons.
To do so, you can use variable placeholders in the Description field on the Election Details page or in the Description field on the Question Details page. This variable placeholder will correspond to each unique elector's specific segment(s), thus allowing them to be dynamically displayed on the ballot if they are used. The placeholders for segmentation are: {{segment1}} and {{segment2}}.
To use a placeholder, simply start typing two open curly brackets (e.g. {{ ) to open a dynamic auto-complete menu of available placeholders depending on the features activated on your account and relevant to this specific field.
Displaying segmentation may only make sense if your segment values are human-readable and can be easily understood – if you are using internal codes for segment values, such values may be confusing.
Was this article helpful?