| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| en:create:multilevel [11.01.2019 19:36] – sophie_irina | en:create:multilevel [11.01.2019 19:42] – sophie_irina |
|---|
| If one really wants to store the data for a multi-level analysis in different data rows, SoSci Survey facilitates this with the following PHP commands: | If one really wants to store the data for a multi-level analysis in different data rows, SoSci Survey facilitates this with the following PHP commands: |
| |
| * ''[[:en:create:functions:multileveldown]]'' -- Starts a sub-questionnaire (Level 1) within the main questionnaire (Level 2) for the singe element. | * ''[[:en:create:functions:multileveldown]]'' -- Starts a sub-questionnaire (Level 1) within the main questionnaire (Level 2) for the single element. |
| * ''[[:en:create:functions:multileveldata]]'' -- Provides the data, which were possibly transmitted via ''multiLevelDown()'', in sub-questionnaires. | * ''[[:en:create:functions:multileveldata]]'' -- Provides the data, which were possibly transmitted using ''multiLevelDown()'', in sub-questionnaires. |
| * ''[[:en:create:functions:multilevelreturn]]'' -- Redirects the participant from the sub-questionnaire back to the main questionnaire and passes (optionally) data, e.g. a multiple-choice question, whether further elements follow. If the command is not used, the sub-questionnaire automatically jumps back to the main questionnaire when reaching the "last page" (in the course of this, no data is transmitted). | * ''[[:en:create:functions:multilevelreturn]]'' -- Redirects the participant from the sub-questionnaire back to the main questionnaire and passes (optionally) data, e.g. a multiple-choice question, whether further elements follow. If the command is not used, the sub-questionnaire automatically jumps back to the main questionnaire when reaching the "last page" (in the course of this, no data is transmitted). |
| | |
| </code> | </code> |
| |
| No further adaptations are needed in the main questionnaire. In the sub-questionnaire, the element should be stored by ''[[:en:create:function:put]]'' in a [[:en:create:questions:internal|internal variable]]. Moreover, it could be useful to define a placeholder for the naming by ''[[:en:create:function:replace]]'. | No further adaptations are needed in the main questionnaire. In the sub-questionnaire, the element should be stored by ''[[:en:create:function:put]]'' in a [[:en:create:questions:internal|internal variable]]. Moreover, it could be useful to define a placeholder for the naming by ''[[:en:create:function:replace]]''. |
| |
| <code php> | <code php> |
| ==== Example 3 ==== | ==== Example 3 ==== |
| |
| The instruction to [[:en:create:functions:randomuse#anwendungsbeispiel|randomUse()]] shows the complete PHP-Code for the case where participant has to rate 20 items randomly selected from a pool, but can also skip them. | The instruction on [[:en:create:functions:randomuse#anwendungsbeispiel|randomUse()]] shows the complete PHP-Code for the case where participant has to rate 20 items randomly selected from a pool, but can also skip them. |
| |
| |
