Difference between revisions of "SurveyCTO Coding Practices"

Jump to: navigation, search
Line 7: Line 7:
Use a lot of groups but do not over use them. This means that you should always ask yourself if anything you do can be done more simplistically with a group. Although, only include a group if they fulfill one of the purposes below:
Use a lot of groups but do not over use them. This means that you should always ask yourself if anything you do can be done more simplistically with a group. Although, only include a group if they fulfill one of the purposes below:


*Apply a [[Relevance Condition to Multiple Fields|relevance condition to multiple fields]]
*If you have [[Multiple Questions Displayed at the Same Time |multiple questions displayed at the same time]]
*Apply a [[Relevance Condition to Multiple Fields|relevance condition to multiple fields]]
*Apply a [[Relevance Condition to Multiple Fields|relevance condition to multiple fields]]



Revision as of 16:53, 12 February 2017

This article discuss solutions to specific but common issues in the programming language used in SurveyCTO. If you want a general introduction to how to structure your approach to programming a CAPI questionnaire or how to use best practices setting that reduce the risk of errors, then see the topic of Questionnaire Programming.

Read First

  • all coding examples linked to in this section is stored in Google Drive. You can either copy that code to an Excel file, but Survey CTO allows you to pull this code using the URL of the Google Sheet directly from your own server.

Groups

Use a lot of groups but do not over use them. This means that you should always ask yourself if anything you do can be done more simplistically with a group. Although, only include a group if they fulfill one of the purposes below:

Repeat Groups

Choice Lists

Back to Parent

This article is part of the topic *topic name, as listed on main page*


Additional Resources

  • list here other articles related to this topic, with a brief description and link