Save Data node
This tutorial is OUTDATED. It applies to Concerto releases up to v5.0.beta.7.
To save a list R object into the database.
By default, data will be stored in the 'default_data_table' table.
Remember that the node expects the 'new_data' object to be a list. If you're trying to save a variable with data type character then you need to convert it to a list first:
mylist = list(myname=mycharactervariable)
When it comes to the position of the save data node in your test flow, consider it carefully. To prevent errors, the node has to come after the necessary data (e.g., the questionnaire scores) has been created, but take care not to place it so late in the test flow that participants may never reach that point - otherwise their data will not be stored! For example, it is better to place the save data node straight after the questionnaire node, but before the feedback node, rather than after the feedback node, because respondents might close their window after the feedback has been displayed.
In some older versions of Concerto 5, it is required that a session parameter is passed into the save data node to allow for new data to be stored. If your version of Concerto doesn't do this automatically, then create a start session node and for 'Authorization type' choose 'None chosen' from the drop-down box. Participants will not be required to login or register, but the start session node will create a 'session' output that you can pass to your save data node. This 'session' output will act as a URL parameter and create a unique session ID to track your respondents by. Their session ID will be stored alongside their data.