View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
16159 | Bug reports | Other | public | 2020-04-20 11:42 | 2021-03-29 14:53 |
Reporter | f_funke | Assigned To | |||
Priority | normal | Severity | feature | ||
Status | acknowledged | Resolution | open | ||
Product Version | 3.22.15 | ||||
Summary | 16159: incorrect data structure for multiple choice question | ||||
Description | When using multiple choice question type, only checked checkboxes are saved in the data set (value "Yes [Y]"). This leads to the problem that when analyzing multiple choice questions (e. g., with R or SPSS Statistics) you can only count how many people checked a response. But when analyzing a multiple choice question you always need the number of people who saw a question but did not check a response (e.g., percentage of yes vs. no). The current implementation becomes really problematic if you have to deal with incomplete data sets (which is almost always the case) or when subquestions are not shown to all respondents (because of filtering/conditions). Imagine a survey with three multiple choice options. SQ1 is visible for all participants, SQ2 is conditionally visible only if SQ1 was checked and SQ3 was visible for all.
The current data structure looks like this: id | Q1_SQ01 | Q1_SQ02 | Q1_SQ03 So when just looking at the data set, you don't know which respondent saw which subquestion and chose to answer it or not. This really makes analyses and reporting very difficult and can easily result in wrong interpretation of data. Especially id 3 is hard for analyses (keeping real nonresponse and no answer because a subquestion was not shown apart). To avoid these problems, the data set must look like this: id | Q1_SQ01 | Q1_SQ02 | Q1_SQ03 | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Bug heat | 4 | ||||
Complete LimeSurvey version number (& build) | 4.1.18 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | |||||
Database type & version | n/a | ||||
Server OS (if known) | |||||
Webserver software & version (if known) | |||||
PHP Version | n/a | ||||
As illustration of data structure is not that readable above: |
|
And in the ideal data set you would also find a code for people who did not see a subquestion: |
|
See related issues |
|
so see However, the issue with data structure reported here and in In any case, please keep the data perspective in mind. I know that changes in the response table require a lot of work and not all users will recognize these efforts. But the lack of a well-structured raw dataset is in my eyes a big flaw for those who want to do serious online research. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2020-04-20 11:42 | f_funke | New Issue | |
2020-04-20 11:42 | f_funke | Status | new => assigned |
2020-04-20 11:42 | f_funke | Assigned To | => cdorin |
2020-04-20 11:42 | f_funke | Relationship added | related to 16157 |
2020-04-20 11:43 | f_funke | Relationship added | related to 16158 |
2020-04-20 11:46 | f_funke | File Added: grafik.png | |
2020-04-20 11:46 | f_funke | Note Added: 57262 | |
2020-04-20 11:56 | f_funke | File Added: grafik-2.png | |
2020-04-20 11:56 | f_funke | Note Added: 57266 | |
2020-12-29 17:54 | cdorin | Assigned To | cdorin => |
2020-12-29 17:54 | cdorin | Status | assigned => acknowledged |
2020-12-29 17:54 | cdorin | Note Added: 61285 | |
2020-12-30 13:04 | f_funke | Note Added: 61315 | |
2021-03-10 22:19 | ollehar | Priority | none => normal |
2021-03-29 14:53 | c_schmitz | Severity | partial_block => feature |
2021-03-29 14:53 | c_schmitz | Product Version | 4.1.18 => 3.22.15 |