Difference between revisions of "SurveyCTO Form Settings"

Jump to: navigation, search
Line 82: Line 82:
 
   
 
   
 
(KB: I need to do a little bit of research for this page.)
 
(KB: I need to do a little bit of research for this page.)
 +
 +
Translating a form into multiple languages
  
 
= Back to parent topic =
 
= Back to parent topic =

Revision as of 23:20, 17 January 2017

In the settings tab, there are three categories of settings - i) questionnaire name, id and version, ii) encryption, and iii) language settings. On your server, you can upload multiple questionnaires and multiple versions of a questionnaire. The questionnaire name, questionnaire id, and questionnaire version ensure that the different questionnaires and the data sets linked to them are kept separate by the server. Encryption guarantees the privacy of the data. SurveyCTO servers are installed on third party cloud servers, and with encryption you can still be sure that the data does not end up in wrong hands if security is breached in any of those steps. The language setting is the default language if no other setting has been set.

The focus of this article is having a discussion regarding the best practices on this topics, not how to do them. Read SurveyCTO's instructions on how to do the things discussed in this article.

Read First

  • Each questionnaire id is associated both with a questionnaire and with a data set. That means that if you change the id you create a new data set where data is saved to. It also means that if you change the questionnaire, but not change the id, the data from two different questionnaire will be saved into the same data set.
  • If you upload a completely different survey, with a different questionnaire name and file name but with the same id as a questionnaire already on the server, then the questionnaire already on the server will be replaced by the new one. Data collected with the new questionnaire will be saved to the same data set as the old questionnaire saved data to. Regardless if the variables match or not, or if there is already data there or not. See Version control of questionnaires already used in the field.

Questionnaire name and id

All data on your SurveyCTO data is linked to a questionnaire. So keeping your questionnaires means that you keep your data organized. By skipping some of the best practices described below, you risk corrupting your data on the server.

First of all, when uploading questionnaires written in Excel, the file name of the Excel file is irrelevant for how your questionnaire is tracked on SurveyCTO's server, and on the tablets. It is a good idea to have the same naming conventions on the files saved to disk on your computer but there is no technical requirement.

When you get started, it is really important that you indicate in both the questionnaire name and id that it is a development version of the form. The best way to do that is to include the word pilot. Then you can keep the pilot in the name until you have completed collecting pilot data. Then you remove the name and with the final name there is little risk that someone uses the pilot form to collect the final data. Do this, even if you did not do any changes between pilot and the real data collection since if you do not change the name, then the server will save the real data to the same data set as the pilot data.

It is common to set both the name and the id to the same value. The id does not allow spaces, so you must use underscores (for example, KBMAP_BL_HH_v1). If you think it makes a difference, you can replace the underscores with spaces in the name. The id is the most important value to keep track. The id controls which data set a questionnaire saves the data to and what the data set is called when you export it. There is some functionality in the questionnaire name. For example, if you start with name with the word test, then this form will not be visible to enumerators. You get the same functionality by the more recently added deploy feature.

Survey Form Naming

It is beneficial to follow a very exact structure when you name your questionnaire and give it an id. The name and id of your questionnaire will make sense to you no matter what you call it now, but unless done properly, it will create confusion down the road. Both for you and for anyone else taking over after you. Below is one recommended way to generate name and id to your questionnaires.

The parts of a survey form name
Meaning Part of name Description Other examples
Example survey name : KBMAP_BL_HH_v1
Project KBMAP The name of the project, use an abbreviation or other short form.

A server is usually linked to only one project, so this part does not matter as much on the server. But all data associated with this questionnaire will be tagged with this name, and there the project name is indeed useful.

Any project name. Do not use survey round (baseline, follow up, back check etc.) or unit of observation (household, village, school etc.)
Survey round BL Indicates which survey this is within the project.

Since a difference in name here indicates a different data set on the server, then we want to differentiate between baseline and baseline pilot, as we do not want to mix pilot data with real data.

Baseline (BL), Baseline pilot (BLpilot), Endline (EL), monitoring data, population listing etc.
Unit of observation HH What type of respondents will be interviewed? Household, school, etc. It is both needed to separate multiple survey within a survey round (doctor/patient, teacher/school), but it is also helpful documentation to anyone using the data set in the future. Household (HH), village, civil servant, etc.
Version v1 This is different from the setting version. When you are developing a questionnaire you use the version setting to indicate to the server that you have made updates. After you are happy with your updates (that usually takes testing several uploads) you update the version number in the name, and download this new version to the tablets. The reason why this is important is explained below (KB: link to that section). Number them in natural order, v1, v2 etc.

Your SurveyCTO subscription level determines the number of questionnaires (counting each unique id as one questionnaire) that you can store on your server. If you run out of space you can either upgrade your server, or you can download any questionnaire no longer in use and all the data associated with it. After you have made sure that you have all data, you can delete the questionnaire you are no longer using and then you are able to upload one new questionnaire.

Version control of questionnaires already used in the field

When you update the questionnaire id, all new data collected will be saved in a new data set on the server with a reference to the new id. So if you have started to collect data with one questionnaire, but for some reason have to make an update to your questionnaire, then you should save the form with a new id. The new questionnaire is likely to have different variables and different variable types for existing variables. Hence the data this questionnaire generates will be different. If we do not change the questionnaire id, the server will save the new and slightly different data set to the old data set.

SurveyCTO's servers have a process that makes it possible to save data collected using an updated version of the questionnaire to the same data set as for the previous version. While that feature does a good job, we can do an even better job with Stata where we will be able to exactly document what changes we need to do to the data set in order to combine data from the two versions of the questionnaire.

So when you have already started to collect data and make an update to the questionnaire change the name from KBMAP_BL_HH_v1 to KBMAP_BL_HH_v2. You will end up with two data set and two different import dofiles. After you have imported the data sets separately to Stata, you can make all needed edits to the files so that they can be appended without any complications. Make this edits in a dofile so that everything you do to the data set is documented.

Before appending the different versions, create a variable called questionnaireVersion or similar. In this variable, store the version number of the questionnaire. Fixed effects based on this variable can then be included in the regressions to adjust for any bias that was introduced from collecting data with questionnaires that slightly differ.

Note that this section only relates to updating questionnaire id and it is not relevant for updating questionnaire name or value in the version column in the settings tab.

Questionnaire version (in settings tab)

If two questionnaires have the same id, then they must have a different version settings. This helps the server ensure that if you are replacing an outdated questionnaire on the server with an updated one, then the server makes sure that it is a more recent questionnaire replacing the older one. There is one simple equation you can use that converts the date and time to a unique version number. There is no good reason for not always using this. See this settings example.

Encryption

It is important that all the data is that we collect is encrypted. This way we protect the privacy of the respondents in case any tablets would be stolen, there is a breach to any of the network security etc. It is easy to do, and this is in line with the privacy promises we make in the consent sections.

You need to encrypt the data at the time when you are creating your questionnaire using the template forms.

For detailed instructions on how to encrypt your data, go to your SurveyCTO server, open up the documentation pages and search for "How do I encrypt my data?"

Language

(KB: I need to do a little bit of research for this page.)

Translating a form into multiple languages

Back to parent topic

This article is a part of the topic Questionnaire Programming.

See also

Further Reading