Actions

Survey quotas and Team meeting summaries: Difference between pages

From LimeSurvey Manual

(Difference between pages)
mNo edit summary
 
 
Line 1: Line 1:
<languages />
This page includes summaries of the internal team meetings.
<translate>
<!--T:1-->
__TOC__


=General explanation= <!--T:2-->
= 2017 =


<!--T:3-->
== 2017-07-25 ==
A quota is used to set a limit on responses from defined groups of people on an active survey. Some common attributes used in defining quotas are things like gender, age, race, province/state.  A quota can be added, edited or deleted by opening the quota window.  Select the quota [[File:button-quota.png]] button on the '''Survey''' administration toolbar.


<!--T:4-->
* Beta 1 of LS 3.0 was released last week.
An english sample survey demonstrating the use of quotas at LimeSurvey is available for download. You can import this survey at your LimeSurvey system for testing ("import" tab at survey creation page): [[Media:LimeSurvey_sample_survey_Quotas.lss|LimeSurvey_sample_survey_Quotas.lss]]


<!--T:31-->
== 2017-07-11 ==
{{Alert|Quotas are tested only when survey is activated. So if you set a quota with limit '0'  and the survey is not activated yet the quota check will not work.}}


=Quotas are not automatically exclusive= <!--T:5-->
* Release LS 3.0 beta tomorrow (12th of July)


<!--T:6-->
== 2017-07-04 ==
Quotas are not comprehensive and automatically exclusive. To explain, let's imagine a survey that has a simple "Yes or No" question at the beginning.


<!--T:7-->
* Release LS 3.0 beta tomorrow (5th of July)
You set a quota on this survey that contains a restriction of 20 users who have answered "Yes" to this question. The quota will be checked everytime somebody answers "Yes" to that question, and completes the whole survey. If the person answers the quota question but doesn't complete the survey, that answer-id is not going to be counted towards the quota. Once 20 people have done so, the quota action will be triggered by anyone else choosing "Yes".
** Need help with error report and testing
** Will be bugs
** Suggestion: Setup test.limesurvey.org for testing, which is always latest git?
* Event beforeQuestionRender broken in 3.0
** https://bugs.limesurvey.org/view.php?id=12502
** Probably need to test more for plugin compatibility.
* Problem with currency question type
** '2.10' possible to validate before but not now?
* Discussion about selling plugins.
* Tammo organizing Dutch User Group Meeting in September.
* Jelo suggests some reading about quota:
** https://www.sawtoothsoftware.com/help/lighthouse-studio/manual/hid_web_quotacontrolfunctions.html
** https://www.sawtoothsoftware.com/help/lighthouse-studio/manual/
** https://help.surveygizmo.com/help/survey-quotas


<!--T:8-->
== 2017-06-27 ==
However, if "No" is chosen, the quota system is never triggered. The survey will never restrict anyone who chooses no.


<!--T:9-->
* Release LS 3.0 beta at 3th of July (1st is a Saturday)
To set a limit on the number of "No" responses, you need to add an additional quota, restricting the number of participants who choose "No".


=Supported question types= <!--T:10-->
== 2017-06-20 ==


<!--T:11-->
* @property or @var for phpdoc? @var seems enough to generate docs, but missing variable name on homepage?
Currently only the following question types can have a quota defined for it:
* New feature: {SHOWANSWERS} placeholder to show tabular view of users answers before submit.
*Gender
** BilldaCat will make plugin.
*Multiple Choice
** Twig will not use placeholders, but files that can be included.
*Array - 5 Point Choice
* Option to use qid instead of sgqa (surveyXgroupXquestion_answer) for answer table (survey_12345)?
*Array - 10 Point Choice
** Deep change
*Language Switch
** Make a plugin that generates a SQL VIEW after survey activation?
*Yes/No
*List (Radio)
*List (Dropdown)
*List with comments


=Example of a quota= <!--T:12-->
== 2017-06-13 ==


<!--T:13-->
* Regression tests in LS started.
You might have to conduct a survey where you want to limit it to 25 male and 30 female respondents. You could then define a quota with a limit of 25 for the answer "Male" from your gender question in the survey.  Another quota for the answer "Female" with a limit of 30 could be added as well.  This will give you a maximum of 25 males who will be able to complete the survey, and a maximum of 30 females who can complete the survey.
* Need a solution to generate RTL language CSS files without using nodejs script R2.
** SASS or LESS generator in browser.
** Factor out CSS not relevant for RTL/LTR in own file, like colours. Louis: Not possible for Bootstrap.
** Louis: Use Bootstrap online generator, like http://www.lavishbootstrap.com/ or http://getbootstrap.com/customize/.
** Mazi: "Usually just logo + 2-3 main colors + font details are adjusted."
* Twig status: Release beta 1st July. More info on the forum: https://www.limesurvey.org/forum/news/111822-limesurvey-3
* Setting to enable super admin to log to database? Might not have FTP access to log files.


<!--T:14-->
== 2017-06-06 ==
A survey participant has to match all answers under the quota for it to apply to that response.


=Adding a new Quota= <!--T:15-->
* New features for EM suggested:
** Write to token attributes from survey
*** Use-cases: 1. Fill in address etc, save in token table. 2. Ask participant about disease, have it written back to user at second run.
*** {TOKEN.ATTRIBUTE_1 = Q123.shown}
** Carsten: Make EM access earlier runs of same survey (waves)
** Carsten: Make default value better (expressions)
** Write-at-submission (Denis plugin)
** Expand EM using plugin.
** Read quota from expression
** See wiki page for more info: https://manual.limesurvey.org/EM_Enhancements
* Phabricator is up at project.limesurvey.org
* Security release
* Twig status
** Work on template editor


<!--T:16-->
== 2017-05-23 ==
Adding a new quota is really adding a framework for set of quota conditions. For a fully working quota you must firstly "Add a quota", and then "Add Answers" to that quota (see next section).


<!--T:17-->
* Twig
When adding a quota, you will be asked for a "Quota Name", the "Quota Limit", and a "Quota Action".
** Possible to inherit templates, in unlimited levels.
** No manual entries yet.
*** Mazi: "From my point of view we need some documentation being ready before release because first thing testers will notice are the broken templates. Beta would be nice, wouldn't have to be alpha I'd say."
* Denis has a PR fixing earlier merge problems in qanda, will be merged.


<!--T:18-->
== 2017-05-16 ==
From version 1.85RC you will also have the option of setting your own unique quota "Quota Message", "url" and "URL Description" for each language used in your survey. You can also set "Autoload URL" so that the survey redirects users to the quota URL when the quota action is triggered.


<!--T:19-->
* Twig
All new quotas are assigned to the Survey you were viewing when you clicked "Set Survey Quotas".
** Bug fixes that needs testing.
*'''Quota Name:''' This is a name to reference the quota by, generally it should describe the quota it will represent.
** When reporting bugs, please mark them as high priority if they are blocking.
*'''Quota Limit:''' This is maximum number of completed surveys to allow for the quota. This sets a limit that will be check when quota selected questions are answered during the survey.
** Template inheritance will be implemented using XML config file.
*'''Quota Action:''' This is an action to perform when a participant is filling out a survey and lands up being part of a quota that has become full.
**'''Terminate Survey:''' This immediately terminates the survey, and closes the interview.
**'''Terminate Survey With Warning:''' This warns the participant and allows them to go back
*'''Autoload URL:''' This tells LimeSurvey to automatically redirect the participant to the URL when the quota action occurs.
*'''Quota Message:''' The text displayed to your survey participant if the quota action is triggered (ie: the quota is full).
*'''URL:''' The URL displayed to survey participants after the quota message, or the URL participants are automatically redirected to if 'Autoload URL' is turned on. You can use [[URL fields]] in this section.
*'''URL Description:''' The text displayed for the URL. (Only in Version 1.85RC)


<!--T:20-->
== 2017-05-09 ==
Once a quota is added, you will be able to add answers under the quota.


=Adding an answer= <!--T:21-->
* Twig
*'''Select Question:'''
** Louis wants more feedback from template designers and plugin writers.
** Dev: Template editor.
** Denis is checking possible merge problems.


<!--T:22-->
== 2017-05-02 ==
+When adding a answer under the quota, you will be shown a list of all available quota questions which are in your survey. If a question does not show up on the list, then its not yet supported with quotas. After you have chosen the question you want, press "Next" to move on to answer selection.
*'''Select Answer:'''


<!--T:23-->
* New employee: Stuart, working with marketing.
+Once selecting your question, you will be show a list of answers under that question. Here you will select an answer you would like to add to you quota, then press "Next".
* Twig still going.
** Bug fixing and testing is going on.


=Adding multiple quotas for the same question & subquestion= <!--T:24-->
== 2017-04-11 ==


<!--T:25-->
* Twig
Adding multiple quotas for the same question is surely possible - but  know that quotas are checked with a logical 'AND' operator - so to meet the quota the user has to answer both subquestion in that question like in your quota.
** Still on schedule for alpha release after Eastern
* How to stop spam on forum?


<!--T:26-->
== 2017-04-05 ==
This means also that multiple quotas for the same '''subquestion''' or the same single choice question can never come true.


=Quota and response data= <!--T:27-->
* Twig status
** Refactoring survey runtime helper
** New date for alpha: 2017-05-14 (or after Eastern)
* Local pricing for other countries
* Next step: Translate limesurvey.org
** Languages ranking: https://www.translated.net/en/languages-that-matter


<!--T:28-->
== 2017-03-28 ==
All data is saved when the participant clicks the "Next" button. Even if the quota is full, the data submitted until the survey is terminated will be recorded. Nevertheless, such id is marked as "No Completed".


=Quota and tokens= <!--T:29-->
* Spam in LimeSurvey forum
* No twig status news because of illness
* Recent security fixes
** Low-impact issues outstanding for 2.64
** XSS in file upload filename?


<!--T:30-->
== 2017-03-21 ==
When tokens are used in a survey and the user is screened out due to a quota, then the according token entry is marked with the letter "Q" in the Completed column. That way the token is invalidated and the survey participant can't re-start the survey.
 
</translate>
* Twig: Louis sick or busy with LimeService
* Markus busy with web page and forum
* Markus ''will'' be working on the admin interface later during 3.0 lifetime, so adding a generic menu event now might not be useful.
 
== 2017-03-14 ==
 
* Carsten not present
* Louis still busy with LimeService
* Generic event to add menus from plugins (no discussion yet)
 
== 2017-03-07 ==
 
* New home-page under construction
* New logo
* Twig
 
== 2017-02-28 ==
 
* No Twig status
* Some PRs
* URL limit in forum
 
== 2017-02-21 ==
 
* Logo design, have finalists.
* Twig status:
** Working on it, making layouts
** Refactoring classes
* Discussion about new plugin event: Before Save/Update Response
** Use-case: View-only plugin, nothing is saved in database.
 
== 2017-02-14 ==
 
* Logo design contest, lots of suggestions
* Twig status: Louis busy with LimeService
 
== 2017-02-07 ==
 
* New event '''afterSurveyQuestionAssessment''' PR from Gabriel: https://github.com/LimeSurvey/LimeSurvey/pull/627
** Merged
* New event '''afterSurveyFind''' PR from Tonis: https://github.com/LimeSurvey/LimeSurvey/pull/634
** Merged
* PR by Denis about fixing subquestions: https://github.com/LimeSurvey/LimeSurvey/pull/633
** Merged
* Twig status update
** Release alpha next week
 
== 2017-01-31 ==
 
* Twig summary
** Alpha version soon ready, approx one week of work left
** Remaining work: Convert question views to Twig templates
* Denis work on localization system for plugins: https://bugs.limesurvey.org/view.php?id=12086
* New design for limesurvey.org in the making: http://imgur.com/a/lyl94
 
== 2017-01-18==
 
* Louis pushed his recent development to a new branch, twig-layout
* Further explanation of the new Twig template files
* LS 3.0.0 ''will'' break backwards compatibility, so we need to warn people before upgrading.
 
= 2016 =
 
== 2016-12-20 ==
 
* More Twig discussion
** Louis made progress, but is not present at the meeting
** config.xml must be made smaller for ease of development of user templates and/or be fully documented.
** The Twig implementation must be tailored to both "casual" and "professional" use, meaning being dependent or independent of core upon choice.
 
== 2016-12-13 ==
 
* Argument about how to solve RTL-templates for users
* No news about Twig or 3.0.0
 
== 2016-12-06 ==
 
* Louis back, estimates 2-3 weeks to implement Twig template system. So release alpha in early 2017 to test? Also, we should probably write down the spec...
* The wikipage about Twig should be updated before alpha to give test instructions.
* Twig should be limited to only those features that will break backwards compatibility. Other features can wait until 3.1.0, like edit question views in template engine and parent-child templates.
 
== 2016-11-29 ==
 
* No news about Twig, Louis has still vacation
* Went live with LimeService responses subscriptions
* Some dev discussions about clear-all button (two-page step? https://bugs.limesurvey.org/view.php?id=11862) and plugin step during installation (https://bugs.limesurvey.org/view.php?id=11962)
 
== 2016-11-22 ==
 
Louis had a deeper look on how to implement Twig into LS. Will make an extension. Estimate to two months? Tammo and possibly Denis will help test and bug check.
 
More information here: https://manual.limesurvey.org/Template_engine
 
== 2016-11-15 ==
 
Discussions about Twig, how the feature will look like. How much will be changed in replacement_helper and SurveyRuntimeHelper? What's the estimation? Do some prototyping to get a better grip.
 
== 2016-11-08 ==
 
Merge <code>answers_html</code> into dev branch. Make sure it's tested properly until next week. Tammo adds a new test survey that can be used to look for bugs. Bug reports should include screen-shots and lss file.

Revision as of 14:32, 25 July 2017

This page includes summaries of the internal team meetings.

2017

2017-07-25

  • Beta 1 of LS 3.0 was released last week.

2017-07-11

  • Release LS 3.0 beta tomorrow (12th of July)

2017-07-04

2017-06-27

  • Release LS 3.0 beta at 3th of July (1st is a Saturday)

2017-06-20

  • @property or @var for phpdoc? @var seems enough to generate docs, but missing variable name on homepage?
  • New feature: {SHOWANSWERS} placeholder to show tabular view of users answers before submit.
    • BilldaCat will make plugin.
    • Twig will not use placeholders, but files that can be included.
  • Option to use qid instead of sgqa (surveyXgroupXquestion_answer) for answer table (survey_12345)?
    • Deep change
    • Make a plugin that generates a SQL VIEW after survey activation?

2017-06-13

  • Regression tests in LS started.
  • Need a solution to generate RTL language CSS files without using nodejs script R2.
  • Twig status: Release beta 1st July. More info on the forum: https://www.limesurvey.org/forum/news/111822-limesurvey-3
  • Setting to enable super admin to log to database? Might not have FTP access to log files.

2017-06-06

  • New features for EM suggested:
    • Write to token attributes from survey
      • Use-cases: 1. Fill in address etc, save in token table. 2. Ask participant about disease, have it written back to user at second run.
      • {TOKEN.ATTRIBUTE_1 = Q123.shown}
    • Carsten: Make EM access earlier runs of same survey (waves)
    • Carsten: Make default value better (expressions)
    • Write-at-submission (Denis plugin)
    • Expand EM using plugin.
    • Read quota from expression
    • See wiki page for more info: https://manual.limesurvey.org/EM_Enhancements
  • Phabricator is up at project.limesurvey.org
  • Security release
  • Twig status
    • Work on template editor

2017-05-23

  • Twig
    • Possible to inherit templates, in unlimited levels.
    • No manual entries yet.
      • Mazi: "From my point of view we need some documentation being ready before release because first thing testers will notice are the broken templates. Beta would be nice, wouldn't have to be alpha I'd say."
  • Denis has a PR fixing earlier merge problems in qanda, will be merged.

2017-05-16

  • Twig
    • Bug fixes that needs testing.
    • When reporting bugs, please mark them as high priority if they are blocking.
    • Template inheritance will be implemented using XML config file.

2017-05-09

  • Twig
    • Louis wants more feedback from template designers and plugin writers.
    • Dev: Template editor.
    • Denis is checking possible merge problems.

2017-05-02

  • New employee: Stuart, working with marketing.
  • Twig still going.
    • Bug fixing and testing is going on.

2017-04-11

  • Twig
    • Still on schedule for alpha release after Eastern
  • How to stop spam on forum?

2017-04-05

2017-03-28

  • Spam in LimeSurvey forum
  • No twig status news because of illness
  • Recent security fixes
    • Low-impact issues outstanding for 2.64
    • XSS in file upload filename?

2017-03-21

  • Twig: Louis sick or busy with LimeService
  • Markus busy with web page and forum
  • Markus will be working on the admin interface later during 3.0 lifetime, so adding a generic menu event now might not be useful.

2017-03-14

  • Carsten not present
  • Louis still busy with LimeService
  • Generic event to add menus from plugins (no discussion yet)

2017-03-07

  • New home-page under construction
  • New logo
  • Twig

2017-02-28

  • No Twig status
  • Some PRs
  • URL limit in forum

2017-02-21

  • Logo design, have finalists.
  • Twig status:
    • Working on it, making layouts
    • Refactoring classes
  • Discussion about new plugin event: Before Save/Update Response
    • Use-case: View-only plugin, nothing is saved in database.

2017-02-14

  • Logo design contest, lots of suggestions
  • Twig status: Louis busy with LimeService

2017-02-07

2017-01-31

2017-01-18

  • Louis pushed his recent development to a new branch, twig-layout
  • Further explanation of the new Twig template files
  • LS 3.0.0 will break backwards compatibility, so we need to warn people before upgrading.

2016

2016-12-20

  • More Twig discussion
    • Louis made progress, but is not present at the meeting
    • config.xml must be made smaller for ease of development of user templates and/or be fully documented.
    • The Twig implementation must be tailored to both "casual" and "professional" use, meaning being dependent or independent of core upon choice.

2016-12-13

  • Argument about how to solve RTL-templates for users
  • No news about Twig or 3.0.0

2016-12-06

  • Louis back, estimates 2-3 weeks to implement Twig template system. So release alpha in early 2017 to test? Also, we should probably write down the spec...
  • The wikipage about Twig should be updated before alpha to give test instructions.
  • Twig should be limited to only those features that will break backwards compatibility. Other features can wait until 3.1.0, like edit question views in template engine and parent-child templates.

2016-11-29

2016-11-22

Louis had a deeper look on how to implement Twig into LS. Will make an extension. Estimate to two months? Tammo and possibly Denis will help test and bug check.

More information here: https://manual.limesurvey.org/Template_engine

2016-11-15

Discussions about Twig, how the feature will look like. How much will be changed in replacement_helper and SurveyRuntimeHelper? What's the estimation? Do some prototyping to get a better grip.

2016-11-08

Merge answers_html into dev branch. Make sure it's tested properly until next week. Tammo adds a new test survey that can be used to look for bugs. Bug reports should include screen-shots and lss file.

Retrieved from "http://manual.limesurvey.org/index.php?title=Survey_quotas&oldid=73938"