Difference between revisions of "Questionnaire Programming"

Jump to: navigation, search
Line 4: Line 4:
= Read First =
= Read First =


You should never start coding your survey before you and your research team has more or less finalized the content of your survey. The reason for this is that content changes might require that you have to re-do something that you have already spent a long time one. A minor change in the question order or in any other way the flow of the questionnaire, might have significant impact on how something has to be implemented in during the questionnaire programming. Late changes to questionnaire content are sometimes needed, but they are by far the most common reason for bugs in the code.
You should never start coding your survey before you and your research team has more or less finalized the content of your survey. The reason for this is that even minor content changes might require that you have to re-do something that you have already spent a long time one. See questionnaire design (content development) and questionnaire programming (functionality development) as two strictly separate tasks which requires the research team's full attention separately. Starting with functionality or late major changes to questionnaire content, are sometimes inevitable, but they are by far the most common reason for quality issues in CAPI survey data.


This chapter related to the set up, work flow and organization of questionnaire programming rather than best practices in SurveyCTO coding best practices. The two topics are related, and you will find many links to such articles. If you want to browse SurveyCTO coding best practices then go to the stand alone chapter called [[SurveyCTO coding practices]].
This chapter related to the set up, work flow and organization of questionnaire programming rather than best practices in SurveyCTO coding best practices. The two topics are related, and you will find many links to such articles. If you want to browse SurveyCTO coding best practices then go to the stand alone chapter called [[SurveyCTO coding practices]].

Revision as of 19:20, 4 January 2017

This chapters relates to the process of digitization of a questionnaire, and not to the process of developing content for Questionnaire Design.


Read First

You should never start coding your survey before you and your research team has more or less finalized the content of your survey. The reason for this is that even minor content changes might require that you have to re-do something that you have already spent a long time one. See questionnaire design (content development) and questionnaire programming (functionality development) as two strictly separate tasks which requires the research team's full attention separately. Starting with functionality or late major changes to questionnaire content, are sometimes inevitable, but they are by far the most common reason for quality issues in CAPI survey data.

This chapter related to the set up, work flow and organization of questionnaire programming rather than best practices in SurveyCTO coding best practices. The two topics are related, and you will find many links to such articles. If you want to browse SurveyCTO coding best practices then go to the stand alone chapter called SurveyCTO coding practices.

Articles often forgotten

Topics

The following topics are ordered in a more or less chronological order

Choosing Software

There are several software on the market for digital data collection. At DIME we have built up

Using the Server

You can either set up your own server, but if your project is a DIME project you can use DIME's development server until your project require its own server

Create a questionnaire

The easiest way to start with one of SurveyCTO's template forms. You can either program your questionnaire in the form builder or in an Excel sheet. We recommend that your default approach is the Excel sheet. Regardless what method you use to program your questionnaire, and regardless if you start with an empty instrument or use a survey that have been used before, it is important that you encrypt your questionnaires.

How to start coding your questionnaire

Before starting the programming, read this article on form settings first.

The organization of how to approach coding a questionnaire (or perhaps the lack therefore) is in our experience the most common reason for serious bugs that should have been avoidable. questionnaire organization programming will provide you with a

Updating a questionnaire already used in the field

While SurveyCTO have fucntionality to allow edits to questionniares already in use, this is not advisable, instead create a new separate version of your questionnaire.