home features documentation blog pricing contact us

Features — Data validation

Password access controlokAccess to the questionnaire can be controled by a personalized password. In that case, each person owns a personnel record in the data base and can complete the data collection in several sessions. This type of access control is required when the system uses prepopulated data. Also, the system can automatically provide each participant with a unique access code such that the administrator does not have to dispatch individual codes at the inception of the field work.
Validation of the number of responses offeredokThe questionnaire designer can determine the exact number of answers expected in response to each question or the range of numbers of answers that is acceptable (e.g., "Check up to three categories"). The system validated the responses offered and lets the user know, if need be, that more or fewer answers are required.
Validation of limits of a numerical valueokFor open or semi-open muneric questions, the system can control the range of values judged to be acceptable. For example, in response to a question on the number of people living in the household, the system could demand that the response be between 1 and 12. Eventually, the user would be advised that the answer is outside the acceptable range.
Validation of open ended questionsokWhen a user selects an open category in a semi-open question, the system verifies that information has been inserted in the open ended part of the category and warns the user otherwise.
Validation of an e-mail addressokAn open or semi-open question can specifically request that the answer conforms to an e-mail address format. By default, the software does not attempt to confirm the existence of the address; it merely validates the format of the answer.
It is also possible to use the CallWeb module which intercepts bounced messages to conduct a real-time validation of an e-mail address supplied by a respondent. Addresses which pass this test are known to be valid.
Verification of the integrity of the case codeokUpon receiving each screen of information, the system verifies the integrity of the access code for that case to avoid respondent substitution and hacking.
Limits to the length of an open responseokIt is possible to predetermine the number of characters allowed in an open-ended response
Validation of Canadian postal codesokAn open or semi-open question can specifically request that the answer conforms to a Canadian postal code format, that is LnL nLn.
Any other form of simple or complex validationokA simple statement allows for the definition of any kind of data validation and for the placement of a custom error message anywhere on the CallWeb page. For example, you can validate that a column of a table totals a certain value and put an error message in the title cell of the column. At the same time, you could validate that a row of the same table averages a certain value and place an error message on the row (in the left or right cell, for example). Meanwhile, you could validate that the sum of all cells in a table equals the sum of all cells in another table and place an error message above the table. These are just examples. Your imagination (and needs) is the limit. All of this can be performed without programming and without the addition of a single dummy question to the CallWeb script.
Validation of preference ordersokThe system can validate preference orders, that is, a set of questions where responses must be mutually exclusive and be comprised between 1 and a set upper value. The system permits that the answers use a subset of possible answers which is pre-determined in the script. For example, respondents could be asked to rank order the top three reasons for purchasing a certain product while accepting that only a first choice and a second choice be provided.