| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
| en:create:personal-code [22.07.2019 20:12] – admin | en:create:personal-code [22.07.2019 20:16] – admin |
|---|
| |
| |
| ==== Open Text Input ===== | ==== Open-ended Text Input ===== |
| |
| The first variant is obvious and corresponds to the procedure in the printed questionnaire. You explain to the participant how to create the code and then use a question about [[:en:create:questions:text]] so that the participant can enter the code. | The first variant is obvious and corresponds to the procedure in the printed questionnaire. You explain to the participant how to create the code and then use a [[:en:create:questions:text]] question so that the participant can enter the code. |
| |
| To check at least the correct format, you can define a "regular expression" for the text input question. To do this, click on the input field on the left in the navigation and define a //regular expression// under //restrictions for the text input//. Regular expressions are complex search patterns with exciting possibilities ([[https://www.regular-expressions.info/|regular-expressions.info]]), but at first glance they also look somewhat complex. It's half as bad for the personal code: | To check at least the correct format, you can define a "regular expression" for the text input question. To do this, click on the input field on the left in the navigation and define a //regular expression// under //restrictions for the text input//. Regular expressions are complex search patterns with exciting possibilities ([[https://www.regular-expressions.info/|regular-expressions.info]]), but at first glance they also look somewhat complex. It's half as bad for the personal code: |
| |
| |
| ==== Separate Text Input ===== | ==== Separate Text Inputs ===== |
| |
| It is easier for the participant to query the individual components of the code separately. The format check is also easier. | It is easier for the respondent to fill in the individual components of the code separately. The format check is also easier. |
| |
| * Create a question "Open text input" and as many input fields as your code has components, e.g. an input field (item) "What is the last letter of your month of birth". | * Create a question "Open-ended Text Input" and as many input fields as your code has components, e.g. an input field (item) "What is the last letter of your month of birth". |
| * Click on the input fields on the left in the navigation to select the appropriate option, e.g. "Numbers", under // Restrictions for text input// in the selection //Defined characters//. | * Click on the input fields on the left in the navigation to select the appropriate option, e.g. "Numbers", under //Restrictions for text input// in the selection //Defined characters//. |
| |
| It is not really necessary to display the participant's personal code "en bloc" again, but if you want to do this, use a little [[:en:create:javascript|JavaScript]]. Assuming your text input question has the identifier "PC01" and contains 6 input fields, you would place the following HTML/JavaScript code under the question: | It is not really necessary to display the participant's personal code "en bloc" again, but if you want to do this, use a little [[:en:create:javascript|JavaScript]]. Assuming your text input question has the identifier "PC01" and contains 6 input fields, you would place the following HTML/JavaScript code under the question: |
