 |
jboogie21, can you please attach a short sample survey that has the issue with the missing/wrong labels? |
|
|
I just uploaded an archive file with sample data. |
|
|
Jboogie21: STATA only uses value labels on numerical variables. If the answer codes are not numerical the plugin exports the full text-answer. |
 |
mfaber, can you please add an according hint to the documentation and maybe let the Stata export try a decent conversion of the answer code to a number (A1 -> 1) |
|
|
mfaber: That makes sense. As c_schmitz suggested, I think a statement in the documentation would be very helpful. Related to my other question, do you know why the token name fields are not maintaining when exporting to STATA? |
|
|
I added a note regarding value labels in the wiki. Reluctant to change the plugin in a way that it changes the underlying answer codes during export. Feels like tampering with the data to me. If someone wants to have a properly labelled data set, it's easy to use numerical answer codes. About the token name fields: I never used them myself so I might have just overlooked these fields while developing the plugin. Will try to come up with a fix in the next few days. Thanks for reporting this issue! |
|
|
jboogie: I attached a new version of the stata_writer plugin. If you can, please copy the file to application\core\plugins\ExportSTATAxml\ in your limesurvey installation directory. Please give me feedback if the additional token fields are exported ok then. |
|
|
Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=14226 |
|
|
It works as expected. This is exciting! |
|
|
LimeSurvey 2.05+ Build 140618 released. |
- Anonymous
