Translations:Expression Manager/201/en

Expression Manager provides complete or partial solutions to each of the following:

• Conditions
• Answercounts
• Advanced reporting for assessments
  • partial: Equations let one store the Assessment value in the database, and micro-tailoring can generate simple formatted reports.  Authors can access those Equation values if they have more complex reporting needs.
• Assessment reports
  • partial:  Since Equations store the Assessment score, it should be possible to use Statistics to show distributions of those scores, and Quotas to limit the number of responses with those scores.
• Store assessment results for further evaluation
  • Equations let one store the Assessment value in the database, completely solving this problem
• More advanced condition rules
• Open Answertable up so that we can alter formatting
  • partial:  All of the question attributes are available, so authors can create custom AnswerTable equivalents as a Question.  Once implatemented, they can also use the showTheseResponses() or showAllResponsesExecpt() functions
• Export survey results with full questions to include images
  • since Tailoring has access to the full question text, it can include images in the export
  • if subjects choose Print Your Answers after finishing the survey, those printouts will be fully tailored
• List of question codes and SGQA identifiers
  • The Show Survey Logic view shows that mapping (plus much more information)
  • In addition, you no longer have to use SGQA codes to refer to variables - you can use the Question code/title.
• Branch/jump to another question (earlier or later) based on current question
  • You can use the Navigation Index for this in most cases
  • Once implemented, you can use the JumpTo() function.  Like the Navigation Index, if you try to jump forward, it will stop on an intervening page if there are any of the relevant mandatory questions are unanswered, or if any relevant questions fail validation tests.
• set quota for total responses
  • If the final question is an Equation that flags a survey as completed (so is NULL if a respondant does not get to that page), you can use Quotas on that question to control the number of completed responses.
• Review all conditions
  • The Show Logic File view shows this (and much more)
• Review all questions + Review all groups
  • The Show Logic File view shows this (and much more)
• How to visualize questions, logic & conditions
  • The Show Logic File view shows this (and much more)
• Offline Surveys
  • Running a survey with all of the questions on the same page would let you do off-line data collection  (e.g. email the html page and associated JavaScript).  However, you would still want a way to submit the results so that they did not get lost.  It may be possible to use Save As HTML to save partially completed responses.
• Remove INSERTANS from question text at survey results
  • INSERTANS is no longer needed.  You can refer to a variable by its SGQA code (without prefixing it with INSERTANS:), or by its question code.
• Informed Consent and Authorization Functionality
  • You can show the informed consent on the welcome page, then ask any additional questions needed (to ensure they meet the study inclusion/exclusion criteria), and ask them a Yes/No question whether they give their consent.  Then, make all of the remaining questions conditional on that yesNo.  For example, if the question is named consent, you would set the relevance to the remaining questions to consent == "Y" (possibly anding that with whatever additional conditions you needed to support your branching needs).
• Show codes instead of of answers using INSERTANS
  • {Qcode} returns the code instead of the response text (which you can get via {INSERTANS:SGQA}, or {Qcode.shown})
• Need group mean or calculations for assessments
  • Say you have N variables of which N-X were answered, you could compute the mean of the answered variables as {sum(var1, var2, ..., varN) / count(var1, var2, ..., varN)}
  • Computing the mean across a set of respondants would require extension of the Quota functionality.
• To insert a language dependent text
  • Tailoring lets you conjugate verbs and decline nouns in each language
• Surveyors should approve their answers
  • Custom Questions with tailoring, or the showAllResponsesExcept() function will let respondants see all of the questions and responses before clicking Submit. If the Navigation Menu option is enabled, it is easy to go back and correct answers.
• Suppliment to #answernnXnnXnnn method of targetting form elements
  • You can now refer to questions and answers by their Question Code, so there is no longer a need to modify SGQA values.
• More flexibility with hidden questions
• Remove specific conditions from multiple questions
  • You can now use Relevance, which is easier to manage than Conditions.  If  needed, they can all be exported from the database, edited in a spreadsheet, and re-imported.
• Cross Survey Reporting
  • By using question codes that are unique across your surveys and versions, you can consolidate data from multiple surveys and/or compare them
• Simplifying integration with other tools
  • Expression Manager uses Question Codes instead of SGQA, making it easier to integrate with other tools.
• Expose assessment score to 3rd party app processing
  • This can be done with Equation question type
• Multiple thank you pages
  • This can be supported via conditional relevance branching and tailoring