Analysis options in shared lists
If you always want to create the same analysis elements every time you use a shared list, you can define those elements as part of the shared list rather than inserting them in every question that uses the list. This is a good time saver in ratings lists, where you may always want to use a specific set of factors or create a "top two" element. Here’s an example for a "top two" element:
RatingList "" define
{
Top2 "Top 2" elementtype(AnalysisCategory) expression("@ * {Excellent, VeryGood}"),
Excellent "Excellent",
VeryGood "Very Good",
Good "Good",
Fair "Fair",
Poor "Poor"
}
The Top 2 element is flagged as an AnalysisCategory element so it does not appear in interviews. However, more importantly, the expression that determines which data contributes to this category uses the @ parameter that tells the analysis program to use the data for the current question. So, if questions RateA and RateB both use this shared list, an analysis program will use the data for RateA if the user is tabulating RateA, and the data for RateB when the user is tabulating RateB.
Notes
▪This facility does not work if you use namedspaced shared lists in a question’s response list. The script runs and generates interviews, but fails when you try to use the question in analyses. The failure is because the response names in the Top 2 element do not match the response names in the question. The response names in the Top 2 element are simple names whereas those in the question are full names that include the list name as well as the response name.
▪Axis blocks do not work in shared lists.
See also