Hello @LAFS,
I am very sorry, I tested it. You are right, the order of the selection on UI level is NOT stored! As far as I can see, this is a change to the KoBo behaviour from 2021, which I had in mind (see screenshot example above). I updated both postings above.
Based on this, you have 3 options to get the select sequence / ranking:
- As @hakan_cetinkaya wrote Do 3 separate questions step-by-step. They can exclude the already selected item(s) by choice_filter. (Also, a repeat_group would be possible.)
- Add a ranking question after the initial multiple select, filtering only the selected items for the ranking. This would be my favorite (see example attached)
- Directly use a rank type question (disadvantage complex UI and all items appear).
- Using something like a likert scale for the items group, asking for the relevance of all (or optional) items with the same scale, e.g. very important … not at all important.
You might also think about the analytical relevance of this select (click) order as it may not be done with clear intention of ranking - and a ranking may even not be clear.
Rank for Multiple Choices 03.xlsx (50.1 KB)
The screenshot shows a MANUAL ranking done after a multiple selection before (in any order of the visible list).
The (code) names for the items are mixed here (see choice list, e.g. 2 for Avocado), only to illustrate the automatic re-ordering of KoBo in the select_multiple.
Text formatting is a bit tricky, against some automatic “optimisation” of KoBo.
Kind regards
