User Tools
userzone:userdoc:importing_answers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
userzone:userdoc:importing_answers [2014/05/21 15:07] Matijs |
userzone:userdoc:importing_answers [2020/03/12 12:06] (current) |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| To import answers you need of course sufficient rights to do so. Having those rights you can either select a survey in the track builder and import the answers into that survey or you can select the generic import wizard and select the survey you want to import to there. | To import answers you need of course sufficient rights to do so. Having those rights you can either select a survey in the track builder and import the answers into that survey or you can select the generic import wizard and select the survey you want to import to there. | ||
| - | After selecting a survey the wizard will show you which fields are available in the survey. Some of the fields depend on the **Translation definition** you choose, but the answers in the survey are usually the same for each translation definition as the default translation definitions only determine the method used to link a set of answers to a specific token. | + | After selecting a survey the wizard will show you which fields are available in the survey. Some of the fields depend on the **import definition** you choose, but the answers in the survey are usually the same for each import definition as the default import definitions only determine the method used to link a set of answers to a specific token. |
| You can then choose either to upload a file or use a large text field to put the import data in. GemsTracker currently supports three file formats: XML, CSV and tabbed text. The text field supports only the use of tabbed texts (e.g. a straight copy and paste from Excel). | You can then choose either to upload a file or use a large text field to put the import data in. GemsTracker currently supports three file formats: XML, CSV and tabbed text. The text field supports only the use of tabbed texts (e.g. a straight copy and paste from Excel). | ||
| Line 43: | Line 43: | ||
| When the import contains a ''completion_date'' field the completion date of the token is set to that date. Otherwise it is set to the import moment, unless the completion date was already set. | When the import contains a ''completion_date'' field the completion date of the token is set to that date. Otherwise it is set to the import moment, unless the completion date was already set. | ||
| - | This happens regardless of any other use of the ''completion_date'' by the chosen translation definition. | + | This happens regardless of any other use of the ''completion_date'' by the chosen import definition. |
userzone/userdoc/importing_answers.1400677643.txt.gz · Last modified: 2020/03/12 12:08 (external edit)
