Advanced survey logic

[avaidyam]

These features may require splitting out lamp.survey into lamp.advanced_survey, as this will now mimic SurveyMonkey/RedCap/etc. surveys more than the EMA-style surveys that LAMP was built to support.

1. Conditional/branching logic between questions of a survey.
2. Additional advanced question types (examples here).
3. Ability to test out the survey before creating it (or delete trial entries).

[lukeoftheshire]

• Specific question ids that give us a way to match without exact string matching is critical, e.g. 'phq9-1'.

• This may be covered by 1, but if we ever want to have multiple questions on a page, the ability to adjust visibility based on the responses to other questions (e.g. don't show question 4 if the participant said yes to 2)

• The abililty to pipe in responses from other questions (possibly with some adjustments made). E.g. ( "You said a source of stress in your life was {{QUESTION 2 ANSWER}}, to what degree is it a source of stress?"). Or, if a user put "March 24 2011" on a date picker, we could display "the 24th of March" (this aspect is more difficult).

• Optional "Back" button - i.e. force participants to continue forward or allow them go back on a survey-dependent basis.

• Fix the duration calculation which is inaccurate. Possible implementations could include:

  1. Time spent on page the question is on (cumulative)
  2. Time spent between previous choice and current choice (cumulative)

• An option to have the survey page automatically advance if all questions on it are answered.

[lukeoftheshire]

• Validation based on previous answers. For example, if we ask a participant how long they were in bed and then how long they slept on a single night, the second number should not be able to be larger than the first