Excerpt from that noting that values cannot contain whitespace (in
A limitation of the XML Schema list datatypes is that white space
characters in the storage values (the value element) are always interpreted
as separators between individual data values. Therefore, authors should
avoid using white space characters within storage values with list
On Fri, Nov 4, 2011 at 2:55 PM, Matteo Sisti Sette < email@example.com> wrote:
I've noticed that the values of a multi select are placed in a single xml
node separated by spaces. Is this something dictated by the OpenRosa
standard or is this a design choice of ODK?
What am I missing that makes this more reasonable than putting each
selected value into a child node?
What should I do if I have values that contain spaces, so that I can
distinguish whether the answering user has selected the options "a", "b"
and "c" or a single option whose value is "a b c"?
We have the same issue in that we use a lot of MULTI select questions, and
it is hard to analyze them when they are in the format 1 2 3 4
It's better if they are separated into sub-nodes. My solution was to build
an app that divides MULTI nodes while synching to your computer. There is a
caveat that the java app requires you to indicate which nodes are
multi-select by naming them with a suffix, like this: <node_MULTI_> .
Anyway, you can use KoBoSync http://www.kobotoolbox.org/products/kobosyncto do it, it's perfectly
compatible with ODK and you will end up with a
nice aggregated CSV of all your collected data. Your multi will end up as
seperate columns with a 1 or 0.