| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 16888 | Bug reports | Other | public | 2020-12-09 17:12 | 2026-10-21 15:40 |
| Reporter | f_funke | Assigned To | c_schmitz | ||
| Priority | low | Severity | partial_block | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.3.30 | ||||
| Summary | 16888: answer code with leading zero causes problems with data import in R | ||||
| Description | This is about the automatically suggested question codes for closed-ended questions (e.g., radio buttons with list (radio) or arrays). After changing the personal setting "Non-Numerical answer option prefix:" to blank/empty (so that no prefix should be used), the question codes are as follows: The leading zero, however, leads to problems when importing data in R: The variables with question codes starting with a zero are recognized as a character variable, not a numeric variable. The codes should start without the leading zero: | ||||
| Tags | No tags attached. | ||||
| Bug heat | 6 | ||||
| Complete LimeSurvey version number (& build) | LS 4.3.29 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | |||||
| Database type & version | LS Cloud | ||||
| Server OS (if known) | |||||
| Webserver software & version (if known) | |||||
| PHP Version | LS Cloud | ||||
| Git branch / Pull Request URL | |||||
 |
Why not add a settings : «number of or 0» 2 by default ? |
 |
The leading zero makes sense when you use a prefix like "XY" so that it results in Code | Assessment | Answeroption which is still sortable when you have more than 10 answer options. |
|
|
Yes, and sometimes you need A000 for format (3 leading 0). You think nobody want ##000 for format ? only ####0 ? or A00 ? I thoink it can be great to have a solution to allow A00 |
 |
Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=40970 |
