Is it possible to have comma "," or dot "." when entering numeric values so it is easier to see the digits? Or having boxes, each box recording 1 number, but enumerators will be able to enter the number into boxes continuously?
As the numeric values we expect to record have large digits, we worry that enumerators may mess up the digits, and the appearance described above can help much.
If you are using the numbers appearance of a string, you could have a
calculated field that stripped out any non-numeric characters and use that
field for your data analysis. That would allow the data collectors to enter
spaces or dashes to aid data entry.
···
On Apr 8, 2015 2:50 PM, wrote:
Hi there,
Is it possible to have comma "," or dot "." when entering numeric values
so it is easier to see the digits? Or having boxes, each box recording 1
number, but enumerators will be able to enter the number into boxes
continuously?
As the numeric values we expect to record have large digits, we worry that
enumerators may mess up the digits, and the appearance described above can
help much.
Thank you Mitch. Do you mean making the type to be "text", so the data is
in string form, but making the appearance to be "numbers"? Could you please
clarify "using the numbers appearance of a string"? Do you mean putting the
word "numbers" as "appearance"?
Thanks,
E
···
On Wednesday, April 8, 2015 at 5:55:43 PM UTC-4, Mitch Sundt wrote:
>
> If you are using the numbers appearance of a string, you could have a
> calculated field that stripped out any non-numeric characters and use that
> field for your data analysis. That would allow the data collectors to enter
> spaces or dashes to aid data entry.
> On Apr 8, 2015 2:50 PM, <ifpr...@gmail.com > wrote:
>
>> Hi there,
>>
>> Is it possible to have comma "," or dot "." when entering numeric values
>> so it is easier to see the digits? Or having boxes, each box recording 1
>> number, but enumerators will be able to enter the number into boxes
>> continuously?
>>
>> As the numeric values we expect to record have large digits, we worry
>> that enumerators may mess up the digits, and the appearance described above
>> can help much.
>>
>> Thank you!
>>
>> Best,
>> E
>>
>> --
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
···
On Wed, Apr 8, 2015 at 8:26 PM, Eva Qiu wrote:
Thank you Mitch. Do you mean making the type to be "text", so the data is
in string form, but making the appearance to be "numbers"? Could you please
clarify "using the numbers appearance of a string"? Do you mean putting the
word "numbers" as "appearance"?
Thanks,
E
On Wednesday, April 8, 2015 at 5:55:43 PM UTC-4, Mitch Sundt wrote:
If you are using the numbers appearance of a string, you could have a
calculated field that stripped out any non-numeric characters and use that
field for your data analysis. That would allow the data collectors to enter
spaces or dashes to aid data entry.
On Apr 8, 2015 2:50 PM, ifpr...@gmail.com wrote:
Hi there,
Is it possible to have comma "," or dot "." when entering numeric values
so it is easier to see the digits? Or having boxes, each box recording 1
number, but enumerators will be able to enter the number into boxes
continuously?
As the numeric values we expect to record have large digits, we worry
that enumerators may mess up the digits, and the appearance described above
can help much.
You received this message because you are subscribed to the Google
Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.