Has anyone figured out how to generate a codebook from a LimeSurvey project?

Something like that : api.limesurvey.org/ ?

Denis

Or maybe you are talking about this feature ( www.limesurvey.org/manual/Optional_setti...nd_Response_Browsing ):
"$showsgqacode: (New in 1.91 ) This setting is used at the printable survey feature and defaults to false. If you set showsgqacode = true; the IDs for each question - and answer if applicable - will be shown; these IDs match the column heading at the Lime_survey_12345 table which holds the answer data for a certain survey. These Ids can be used for a code book for manual database queries."

A code book is basically an overview over all questions that show the questions and answer options and the respective codes.

This is to help the person analyzing later in programms like SPSS or similar.

This would be a good feature for Limesurvey to have, because it makes life easier for teams where the programmer of the survey is not the person analyzing it.

Well, showing all codes at the printable version should come near to that (I think it doesn't include the question codes yet).

You can also use the survey logic file for this.

Are there lots of user interested in a "Codebook" plugin for Limesurvey?

I am wondering if the printversion isn't already some kind of code book. I would need to check if the codes can be shown there.

I know the codebook feature from Globalpark (now QuestBack) and in theory it didn't look much different from a HTML page showing all questions, but of course with the relevant question and answer codes.

Usually in Market Research you prepare the questionnaire first in a Word version for example, so that you are able to discuss it with the client and the internal team and only once it is approved programming would start. In theory this word document could be the codebook. But often this version doesn't include the codes or not the correct ones, or during programming codes have been changed.

So for the ones analyzing, it is very important to know which answer actually has which code in the questionnaire.

But even if you have the codes nicely in the word version, imagine that during programming the programmer switched "YES" from code "1" to code "2" and suddenly the analysis fails misserably if it doesn't have this detail. I know that programmers shouldn't do stuff like this in the first place, but shit happens everywhere, so...

holch, if the printable version with the codes looks fine feel free to file a feature request for extending this to question codes and assign it to me.
Maybe I can extend it for 2.06.

Something like Survey Logic File ?


I use it a lot

Example : www.limesurvey.org/manual/File:Mcc_filter5.jpg

I have asked the colleagues to send me an example from Globalpark. I'll have a look how they have done it.

But if I recall right, it was actually very similar to our printed version (hadn't looked at that for a long time), just with the codes for questions and answers showing. If I think if we can implement that as an own link "code book" and actually just show a version of the printed version, this should solve the problem for most cases.

Printed version have a lack of a lot of thing , no ?

Well, the survey logic file is already quite good I guess.

I was never someone to use the codebook much, so I am not 100% sure what the exact needs are, but from my point of few it needs at least the following:
- Questions with question ID / code
- Subquestions / answers with code
- potential filters and skip rules would be probably good.

Seems like the survey logic file has all that. It is a bit cluttered and confusing, but at the end of the day it probably does the trick.