Roster variables

Scenario: The numerical answer to a question serves to establish on how many cases it is required to ask for particular characteristics.

Example: The answer to a given question establishes that there are 500 water wells. For each well, it is necessary to know several characteristics: such as the depth, the number of extracted cubic meters, the frequency of use, etc.

  1. We found that there is a limit of 200 items on the list so it is not possible to request characteristics for all cases. Is there a solution to this limitation within the system?

  2. For this kind of variables, sometimes more than two different response options are required, for example: “Yes”, “No”, “Don’t Know”, "Don’t answer’. To simplify the management of these answers the designer needs to develop a matrix, but the system does not accept more than two columns. Is it possible to generate a matrix for variables of this type that allows more than two columns (questions) per case?

A few quick answers below:

  1. The maximum number of rows in the type of roster you describe (in our jargon, a "simple roster) is indeed 200. See more on Survey Solutions limits here. One work-around would be to create, in your case, three rosters of 200 rows each. Can explain idea more if of interest.
  2. Not sure I understand the issue. If one wants a question to have 4 answer options-- “Yes”, “No”, “Don’t Know”, “Don’t answer”–one simply creates those answer options. If this question is a first question asked of each item in a roster before more questions are asked about that item (e.g., “did you consume [FOOD ITEM] in the last 7 days?”), the multi-select yes/no control only allows for “yes” and “no” (and unanswered could be interpreted perhaps as “didn’t answer”). If the multi-select yes/no control is not appropriate, consider a fixed roster whose first question for each item is a question with all of the desired options. If necessary, one might be able to have the yes/no/don’t know/didn’t answer questions be in one fixed roster and the follow-up questions in another roster, with some enablement condition code linking yes/no/don’t know/didn’t answer questions in the i-th row of the first roster with enablement of the j-th row in the second roster.

Conduct the survey at the level of wells.