ODK xform questions

Hi all -

I'm creating new xforms for a new project and am on the learning curve/
refresher. I'm leaning on these resources, they are great -
thanks!:

Questions:

  1. Is there a place for me to learn how to use the Grouping and
    Branching features? Is there a clear distinction between branching
    and skip logic ?
    1.a. Clint - is Branching working at http://build.opendatakit.org ?
    I don't intuit how to use the feature.

  2. Another build question - constraint on text length?
    using a constraint for min and max length of a data entry field. I
    was looking to constrain the response to exactly four. "Valid lengths
    for this user input of this control."

  3. In Kobo formdesigner by Neil H. , the use of Boolean is indicated.
    Is that supported in ODK Collect? I'm only seeing type="select1" for
    boolean type questions in the sample forms.

Thanks.

Hi James:

No, Build does not yet support branching. It's a feature that I want to build right from a usability perspective, and I'm still working through how best to do that. I would ballpark it at 2 or 3 months out, but I can't commit to anything just yet.

For now, you'll want to use the relevance field (which specifies the skip logic) in the advanced section of controls. This is the same thing as branching. Note, though, that your skip logic won't automatically convert to branches when the feature gets added.

For the text length, if you require the length to be at least 4 inclusive as well as at most 4 inclusive, you'll get the behavior you want.

Thanks,
—Clint
Hi all -

··· On Friday, May 6, 2011 at 2:17 PM, jpd wrote: > > I'm creating new xforms for a new project and am on the learning curve/ > refresher. I'm leaning on these resources, they are great - > thanks!: > > * http://opendatakit.org/use/build/ # getting started > * browsing examples at http://code.google.com/p/opendatakit/source/browse?repo=forms > * http://build.opendatakit.org/ # building my own examples and > deploying to a 0.9.6 instance at *appspot.com > > Questions: > 1. Is there a place for me to learn how to use the Grouping and > Branching features? Is there a clear distinction between branching > and skip logic ? > 1.a. Clint - is Branching working at http://build.opendatakit.org ? > I don't intuit how to use the feature. > > 2. Another build question - constraint on text length? > using a constraint for min and max length of a data entry field. I > was looking to constrain the response to exactly four. "Valid lengths > for this user input of this control." > constraint="(. >e; 4 and . <e; 4)"/> > > 3. In Kobo formdesigner by Neil H. , the use of Boolean is indicated. > Is that supported in ODK Collect? I'm only seeing type="select1" for > boolean type questions in the sample forms. > > Thanks. > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

Clint - Thanks.

Hi James:

No, Build does not yet support branching. It's a feature that I want to
build right from a usability perspective, and I'm still working through how
best to do that. I would ballpark it at 2 or 3 months out, but I can't
commit to anything just yet.

ok. FYI - the branch button at the bottom is confusing.

For now, you'll want to use the relevance field (which specifies the skip
logic) in the advanced section of controls. This is the same thing as
branching. Note, though, that your skip logic won't automatically convert to
branches when the feature gets added.

Ah. Ok. I'm following threads on that like
http://groups.google.com/group/opendatakit-developers/browse_thread/thread/ed26de0602295edc/952966b30e3b55a7?#952966b30e3b55a7

For the text length, if you require the length to be at least 4 inclusive
as well as at most 4 inclusive, you'll get the behavior you want.

hmm..... I don't think its behaving as expected. I don't get any warnings
when I exceed 4 characters in that field.

=4 & <= 4 should give me exactly 4. Is there another way to write that?
Does constraint apply to string.length by default?

··· On Fri, May 6, 2011 at 3:30 PM, Clint Tseng wrote:

Thanks,
—Clint

On Friday, May 6, 2011 at 2:17 PM, jpd wrote:

Hi all -

I'm creating new xforms for a new project and am on the learning curve/
refresher. I'm leaning on these resources, they are great -
thanks!:

Questions:

  1. Is there a place for me to learn how to use the Grouping and
    Branchingg features? Is there a clear distinction between branching

and skip logic ?
1.a. Clint - is Branching working at http://build.opendatakit.org ?
I don't intuit how to use the feature.

  1. Another build question - constraint on text length?
    using a constraint for min and max length of a data entry field. I
    was looking to constrain the response to exactly four. "Valid lengths
    for this user input of this control."

  2. In Kobo formdesigner by Neil H. , the use of Boolean is indicated.
    Is that supported in ODK Collect? I'm only seeing type="select1" for
    boolean type questions in the sample forms.

Thanks.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

I'm not sure string length constraints are in the version of the javarosa
libraries shipping with the current ODK Collect. I believe the constraint
should be "stringlength(.) &eq; 4"

Mitch

··· On Fri, May 6, 2011 at 4:26 PM, James Dailey wrote:

Clint - Thanks.

On Fri, May 6, 2011 at 3:30 PM, Clint Tseng cxlt@cs.washington.eduwrote:

Hi James:

No, Build does not yet support branching. It's a feature that I want to
build right from a usability perspective, and I'm still working through how
best to do that. I would ballpark it at 2 or 3 months out, but I can't
commit to anything just yet.

ok. FYI - the branch button at the bottom is confusing.

For now, you'll want to use the relevance field (which specifies the skip
logic) in the advanced section of controls. This is the same thing as
branching. Note, though, that your skip logic won't automatically convert to
branches when the feature gets added.

Ah. Ok. I'm following threads on that like
http://groups.google.com/group/opendatakit-developers/browse_thread/thread/ed26de0602295edc/952966b30e3b55a7?#952966b30e3b55a7

For the text length, if you require the length to be at least 4 inclusive
as well as at most 4 inclusive, you'll get the behavior you want.

hmm..... I don't think its behaving as expected. I don't get any warnings
when I exceed 4 characters in that field.

=4 & <= 4 should give me exactly 4. Is there another way to write that?
Does constraint apply to string.length by default?

Thanks,
—Clint

On Friday, May 6, 2011 at 2:17 PM, jpd wrote:

Hi all -

I'm creating new xforms for a new project and am on the learning curve/
refresher. I'm leaning on these resources, they are great -
thanks!:

Questions:

  1. Is there a place for me to learn how to use the Grouping and
    Branchingg features? Is there a clear distinction between branching

and skip logic ?
1.a. Clint - is Branching working at http://build.opendatakit.org ?
I don't intuit how to use the feature.

  1. Another build question - constraint on text length?
    using a constraint for min and max length of a data entry field. I
    was looking to constrain the response to exactly four. "Valid lengths
    for this user input of this control."

  2. In Kobo formdesigner by Neil H. , the use of Boolean is indicated.
    Is that supported in ODK Collect? I'm only seeing type="select1" for
    boolean type questions in the sample forms.

Thanks.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com

You could also use a regular expression, instead. Something like: regex(.
, '[A-Za-z]{4}')

··· On Sat, May 7, 2011 at 6:53 PM, Mitch Sundt wrote:

I'm not sure string length constraints are in the version of the javarosa
libraries shipping with the current ODK Collect. I believe the constraint
should be "stringlength(.) &eq; 4"

Mitch

On Fri, May 6, 2011 at 4:26 PM, James Dailey jamespdailey@gmail.comwrote:

Clint - Thanks.

On Fri, May 6, 2011 at 3:30 PM, Clint Tseng cxlt@cs.washington.eduwrote:

Hi James:

No, Build does not yet support branching. It's a feature that I want to
build right from a usability perspective, and I'm still working through how
best to do that. I would ballpark it at 2 or 3 months out, but I can't
commit to anything just yet.

ok. FYI - the branch button at the bottom is confusing.

For now, you'll want to use the relevance field (which specifies the
skip logic) in the advanced section of controls. This is the same thing as
branching. Note, though, that your skip logic won't automatically convert to
branches when the feature gets added.

Ah. Ok. I'm following threads on that like
http://groups.google.com/group/opendatakit-developers/browse_thread/thread/ed26de0602295edc/952966b30e3b55a7?#952966b30e3b55a7

For the text length, if you require the length to be at least 4 inclusive
as well as at most 4 inclusive, you'll get the behavior you want.

hmm..... I don't think its behaving as expected. I don't get any
warnings when I exceed 4 characters in that field.

=4 & <= 4 should give me exactly 4. Is there another way to write
that? Does constraint apply to string.length by default?

Thanks,
—Clint

On Friday, May 6, 2011 at 2:17 PM, jpd wrote:

Hi all -

I'm creating new xforms for a new project and am on the learning curve/
refresher. I'm leaning on these resources, they are great -
thanks!:

Questions:

  1. Is there a place for me to learn how to use the Grouping and
    Branchingg features? Is there a clear distinction between branching

and skip logic ?
1.a. Clint - is Branching working at http://build.opendatakit.org ?
I don't intuit how to use the feature.

  1. Another build question - constraint on text length?
    using a constraint for min and max length of a data entry field. I
    was looking to constrain the response to exactly four. "Valid lengths
    for this user input of this control."

  2. In Kobo formdesigner by Neil H. , the use of Boolean is indicated.
    Is that supported in ODK Collect? I'm only seeing type="select1" for
    boolean type questions in the sample forms.

Thanks.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Thanks for all the help. I've still got a basic question here - SHORT
VERSION

constraint="regex(., '[A-Za-z0-9]{4}')" # should that work?

LONG VERSION

The Stringlength suggestion didn't give any result.
constraint="stringlength(.) &eq; 4"

So, looking at regex as preferred/versatile...

I'm using this as my xform code model from HouseholdSurvey:

In using Build.opendatakit.org, using regex in constraint field results in
:

  <bind nodeset="/data/SysNum" type="string" required="true()"

constraint="(regex(., '[A-Za-z0-9]{4}')"/>

What I am trying to filter for is actually any 4 alpha-numeric code, symbols
not allowed.
Valid:
4rtyu
Eirh
w34y

I removed the extra parans, and replaced the given phrase with :

I am not sure I am writing the regex correctly. Probably not.

In any case, its not functioning as I expect as the following invalid
strings are not caught (for example):
E56864
erjhj

The xform header is standard. Am I missing something?

<h:html xmlns="http://www.w3.org/2002/xforms" xmlns:h="
http://www.w3.org/1999/xhtml" xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:jr="
http://openrosa.org/javarosa">
<h:head>
<h:title>Test02</h:title>
...

··· On Mon, May 9, 2011 at 12:15 AM, Carl Hartung wrote:

You could also use a regular expression, instead. Something like: regex(.
, '[A-Za-z]{4}')

On Sat, May 7, 2011 at 6:53 PM, Mitch Sundt msundt@cs.washington.eduwrote:

I'm not sure string length constraints are in the version of the javarosa
libraries shipping with the current ODK Collect. I believe the constraint
should be "stringlength(.) &eq; 4"

Mitch

On Fri, May 6, 2011 at 4:26 PM, James Dailey jamespdailey@gmail.comwrote:

Clint - Thanks.

On Fri, May 6, 2011 at 3:30 PM, Clint Tseng cxlt@cs.washington.eduwrote:

Hi James:

No, Build does not yet support branching. It's a feature that I want to
build right from a usability perspective, and I'm still working through how
best to do that. I would ballpark it at 2 or 3 months out, but I can't
commit to anything just yet.

ok. FYI - the branch button at the bottom is confusing.

For now, you'll want to use the relevance field (which specifies the
skip logic) in the advanced section of controls. This is the same thing as
branching. Note, though, that your skip logic won't automatically convert to
branches when the feature gets added.

Ah. Ok. I'm following threads on that like
http://groups.google.com/group/opendatakit-developers/browse_thread/thread/ed26de0602295edc/952966b30e3b55a7?#952966b30e3b55a7

For the text length, if you require the length to be at least 4
inclusive as well as at most 4 inclusive, you'll get the behavior you want.

hmm..... I don't think its behaving as expected. I don't get any
warnings when I exceed 4 characters in that field.

=4 & <= 4 should give me exactly 4. Is there another way to write
that? Does constraint apply to string.length by default?

Thanks,
—Clint

On Friday, May 6, 2011 at 2:17 PM, jpd wrote:

Hi all -

I'm creating new xforms for a new project and am on the learning curve/
refresher. I'm leaning on these resources, they are great -
thanks!:

Questions:

  1. Is there a place for me to learn how to use the Grouping and
    Branchingg features? Is there a clear distinction between branching

and skip logic ?
1.a. Clint - is Branching working at http://build.opendatakit.org ?
I don't intuit how to use the feature.

  1. Another build question - constraint on text length?
    using a constraint for min and max length of a data entry field. I
    was looking to constrain the response to exactly four. "Valid lengths
    for this user input of this control."

  2. In Kobo formdesigner by Neil H. , the use of Boolean is indicated.
    Is that supported in ODK Collect? I'm only seeing type="select1" for
    boolean type questions in the sample forms.

Thanks.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

I think what you want is: constraint="regex(., '[1]{4}$')"

I'm no regex wizard, but I think that without the ^ and $ that expression
means any line containing 4 alphanumeric characters, and with them it means
a line with only 4 alphanumeric characters.

··· On Mon, May 9, 2011 at 4:27 PM, James Dailey wrote:

Thanks for all the help. I've still got a basic question here - SHORT
VERSION

constraint="regex(., '[A-Za-z0-9]{4}')" # should that work?

LONG VERSION

The Stringlength suggestion didn't give any result.
constraint="stringlength(.) &eq; 4"

So, looking at regex as preferred/versatile...

I'm using this as my xform code model from HouseholdSurvey:

In using Build.opendatakit.org, using regex in constraint field results in
:

  <bind nodeset="/data/SysNum" type="string" required="true()" constraint="(regex(., '[A-Za-z0-9]{4}')"/>

What I am trying to filter for is actually any 4 alpha-numeric code,
symbols not allowed.
Valid:
4rtyu
Eirh
w34y

I removed the extra parans, and replaced the given phrase with :

I am not sure I am writing the regex correctly. Probably not.

In any case, its not functioning as I expect as the following invalid
strings are not caught (for example):
E56864
erjhj

The xform header is standard. Am I missing something?

<h:html xmlns="http://www.w3.org/2002/xforms" xmlns:h="
http://www.w3.org/1999/xhtml" xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:jr="
http://openrosa.org/javarosa">
<h:head>
<h:title>Test02</h:title>
...

On Mon, May 9, 2011 at 12:15 AM, Carl Hartung carlhartung@gmail.comwrote:

You could also use a regular expression, instead. Something like:
regex(. , '[A-Za-z]{4}')

On Sat, May 7, 2011 at 6:53 PM, Mitch Sundt msundt@cs.washington.eduwrote:

I'm not sure string length constraints are in the version of the javarosa
libraries shipping with the current ODK Collect. I believe the constraint
should be "stringlength(.) &eq; 4"

Mitch

On Fri, May 6, 2011 at 4:26 PM, James Dailey jamespdailey@gmail.comwrote:

Clint - Thanks.

On Fri, May 6, 2011 at 3:30 PM, Clint Tseng cxlt@cs.washington.eduwrote:

Hi James:

No, Build does not yet support branching. It's a feature that I want to
build right from a usability perspective, and I'm still working through how
best to do that. I would ballpark it at 2 or 3 months out, but I can't
commit to anything just yet.

ok. FYI - the branch button at the bottom is confusing.

For now, you'll want to use the relevance field (which specifies the
skip logic) in the advanced section of controls. This is the same thing as
branching. Note, though, that your skip logic won't automatically convert to
branches when the feature gets added.

Ah. Ok. I'm following threads on that like
http://groups.google.com/group/opendatakit-developers/browse_thread/thread/ed26de0602295edc/952966b30e3b55a7?#952966b30e3b55a7

For the text length, if you require the length to be at least 4
inclusive as well as at most 4 inclusive, you'll get the behavior you want.

hmm..... I don't think its behaving as expected. I don't get any
warnings when I exceed 4 characters in that field.

=4 & <= 4 should give me exactly 4. Is there another way to write
that? Does constraint apply to string.length by default?

Thanks,
—Clint

On Friday, May 6, 2011 at 2:17 PM, jpd wrote:

Hi all -

I'm creating new xforms for a new project and am on the learning curve/
refresher. I'm leaning on these resources, they are great -
thanks!:

Questions:

  1. Is there a place for me to learn how to use the Grouping and
    Branchingg features? Is there a clear distinction between branching

and skip logic ?
1.a. Clint - is Branching working at http://build.opendatakit.org ?
I don't intuit how to use the feature.

  1. Another build question - constraint on text length?
    using a constraint for min and max length of a data entry field. I
    was looking to constrain the response to exactly four. "Valid lengths
    for this user input of this control."

  2. In Kobo formdesigner by Neil H. , the use of Boolean is indicated.
    Is that supported in ODK Collect? I'm only seeing type="select1" for
    boolean type questions in the sample forms.

Thanks.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


  1. a-zA-Z0-9 ↩︎

Hi - More questions on the same form. Clint-Thanks for the update to ODK
Build.

*GPS Location *
I noticed that it is possible to make the LOCATION field "read only" in ODK
Build. I think this should be avoided in UI. I thought it meant you would
allow the lat long to be machine determined and then allow the user to edit
the location. Removing "read only" enables the device to read GPS location.

Also, my users are reporting that the GPS location feature is not working
reliably. They restart the phone and it works, so I'm not sure what this
means. They do have GSP status app and report that is working and giving
good results even as the ODK Collect fails on location. What other info
should I collect from them. I believe they're using Android 2.2 on HTC
devices.

Do you see any issue with the form at http://dpaste.com/549936/ .
http://dpaste.com/549936/

Cyrillic font
In ODK Build, if you enter Cyrillic characters it seems to save it
incorrectly in terms of encoding. i.e. when I Export to Download or when I
Export to Aggregate I get garbage in the form_.xml and ODK Collect. I tried
working around this by editing the XML form in text editor and then saving
that as UTF-8. Still when I upload to Aggregate and then download to
Collect, I get garbage in the strings.

Байршлын тэмдэглэл (Record Location)
Бүтээгдэхүүн байгаа эсэх? (Device Present?)
Үгүй (No)
Тийм (Yes)

Valid xform
The ODK Validator when applied to the downloaded xml tells me the xform is
valid but gives a warning about the Id.

*Translation framework in Collect *
Translation of Collect menu and navigation to Mongolian Cyrillic - is this
possible? I mean the menu and instructions like "To navigate, swipe..."
and buttons like "Save Data and Exit" at the end.

  • James
··· On Mon, May 9, 2011 at 6:28 PM, Carl Hartung wrote:

I think what you want is: constraint="regex(., '[1]{4}$')"

I'm no regex wizard, but I think that without the ^ and $ that expression
means any line containing 4 alphanumeric characters, and with them it means
a line with only 4 alphanumeric characters.

On Mon, May 9, 2011 at 4:27 PM, James Dailey jamespdailey@gmail.comwrote:

Thanks for all the help. I've still got a basic question here - SHORT
VERSION

constraint="regex(., '[A-Za-z0-9]{4}')" # should that work?

LONG VERSION

The Stringlength suggestion didn't give any result.
constraint="stringlength(.) &eq; 4"

So, looking at regex as preferred/versatile...

I'm using this as my xform code model from HouseholdSurvey:

In using Build.opendatakit.org, using regex in constraint field results
in :

  <bind nodeset="/data/SysNum" type="string" required="true()" constraint="(regex(., '[A-Za-z0-9]{4}')"/>

What I am trying to filter for is actually any 4 alpha-numeric code,
symbols not allowed.
Valid:
4rtyu
Eirh
w34y

I removed the extra parans, and replaced the given phrase with :

I am not sure I am writing the regex correctly. Probably not.

In any case, its not functioning as I expect as the following invalid
strings are not caught (for example):
E56864
erjhj

The xform header is standard. Am I missing something?

<h:html xmlns="http://www.w3.org/2002/xforms" xmlns:h="
http://www.w3.org/1999/xhtml" xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:jr="
http://openrosa.org/javarosa">
<h:head>
<h:title>Test02</h:title>
...

On Mon, May 9, 2011 at 12:15 AM, Carl Hartung carlhartung@gmail.comwrote:

You could also use a regular expression, instead. Something like:
regex(. , '[A-Za-z]{4}')

On Sat, May 7, 2011 at 6:53 PM, Mitch Sundt msundt@cs.washington.eduwrote:

I'm not sure string length constraints are in the version of the
javarosa libraries shipping with the current ODK Collect. I believe the
constraint should be "stringlength(.) &eq; 4"

Mitch

On Fri, May 6, 2011 at 4:26 PM, James Dailey jamespdailey@gmail.comwrote:

Clint - Thanks.

On Fri, May 6, 2011 at 3:30 PM, Clint Tseng cxlt@cs.washington.eduwrote:

Hi James:

No, Build does not yet support branching. It's a feature that I want
to build right from a usability perspective, and I'm still working through
how best to do that. I would ballpark it at 2 or 3 months out, but I can't
commit to anything just yet.

ok. FYI - the branch button at the bottom is confusing.

For now, you'll want to use the relevance field (which specifies the
skip logic) in the advanced section of controls. This is the same thing as
branching. Note, though, that your skip logic won't automatically convert to
branches when the feature gets added.

Ah. Ok. I'm following threads on that like
http://groups.google.com/group/opendatakit-developers/browse_thread/thread/ed26de0602295edc/952966b30e3b55a7?#952966b30e3b55a7

For the text length, if you require the length to be at least 4
inclusive as well as at most 4 inclusive, you'll get the behavior you want.

hmm..... I don't think its behaving as expected. I don't get any
warnings when I exceed 4 characters in that field.

=4 & <= 4 should give me exactly 4. Is there another way to write
that? Does constraint apply to string.length by default?

Thanks,
—Clint

On Friday, May 6, 2011 at 2:17 PM, jpd wrote:

Hi all -

I'm creating new xforms for a new project and am on the learning
curve/
refresher. I'm leaning on these resources, they are great -
thanks!:

Questions:

  1. Is there a place for me to learn how to use the Grouping and
    Branchingg features? Is there a clear distinction between branching

and skip logic ?
1.a. Clint - is Branching working at http://build.opendatakit.org ?
I don't intuit how to use the feature.

  1. Another build question - constraint on text length?
    using a constraint for min and max length of a data entry field. I
    was looking to constrain the response to exactly four. "Valid lengths
    for this user input of this control."

  2. In Kobo formdesigner by Neil H. , the use of Boolean is indicated.
    Is that supported in ODK Collect? I'm only seeing type="select1" for
    boolean type questions in the sample forms.

Thanks.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile


  1. a-zA-Z0-9 ↩︎

A quick follow up. Digging into the community posts, I found the link to
http://rishida.net/tools/conversion/ which allowed me to take my relatively
simple form (only 12 strings needed translation) and translate them into
ascii (Decimal NCR). That's not a long term solution for anyone, but does
work.

··· On Thu, Jun 2, 2011 at 9:30 PM, James Dailey wrote:

Hi - More questions on the same form. Clint-Thanks for the update to ODK
Build.

*GPS Location *
I noticed that it is possible to make the LOCATION field "read only" in ODK
Build. I think this should be avoided in UI. I thought it meant you would
allow the lat long to be machine determined and then allow the user to edit
the location. Removing "read only" enables the device to read GPS location.

Also, my users are reporting that the GPS location feature is not working
reliably. They restart the phone and it works, so I'm not sure what this
means. They do have GSP status app and report that is working and giving
good results even as the ODK Collect fails on location. What other info
should I collect from them. I believe they're using Android 2.2 on HTC
devices.

Do you see any issue with the form at http://dpaste.com/549936/ . http://dpaste.com/549936/

Cyrillic font
In ODK Build, if you enter Cyrillic characters it seems to save it
incorrectly in terms of encoding. i.e. when I Export to Download or when I
Export to Aggregate I get garbage in the form_.xml and ODK Collect. I tried
working around this by editing the XML form in text editor and then saving
that as UTF-8. Still when I upload to Aggregate and then download to
Collect, I get garbage in the strings.

Байршлын тэмдэглэл (Record Location)
Бүтээгдэхүүн байгаа эсэх? (Device Present?)
Үгүй (No)
Тийм (Yes)

Valid xform
The ODK Validator when applied to the downloaded xml tells me the xform is
valid but gives a warning about the Id.

*Translation framework in Collect *
Translation of Collect menu and navigation to Mongolian Cyrillic - is this
possible? I mean the menu and instructions like "To navigate, swipe..."
and buttons like "Save Data and Exit" at the end.

  • James

On Mon, May 9, 2011 at 6:28 PM, Carl Hartung carlhartung@gmail.comwrote:

I think what you want is: constraint="regex(., '[1]{4}$')"

I'm no regex wizard, but I think that without the ^ and $ that expression
means any line containing 4 alphanumeric characters, and with them it means
a line with only 4 alphanumeric characters.

On Mon, May 9, 2011 at 4:27 PM, James Dailey jamespdailey@gmail.comwrote:

Thanks for all the help. I've still got a basic question here - SHORT
VERSION

constraint="regex(., '[A-Za-z0-9]{4}')" # should that work?

LONG VERSION

The Stringlength suggestion didn't give any result.
constraint="stringlength(.) &eq; 4"

So, looking at regex as preferred/versatile...

I'm using this as my xform code model from HouseholdSurvey:

In using Build.opendatakit.org, using regex in constraint field results
in :

  <bind nodeset="/data/SysNum" type="string" required="true()" constraint="(regex(., '[A-Za-z0-9]{4}')"/>

What I am trying to filter for is actually any 4 alpha-numeric code,
symbols not allowed.
Valid:
4rtyu
Eirh
w34y

I removed the extra parans, and replaced the given phrase with :

I am not sure I am writing the regex correctly. Probably not.

In any case, its not functioning as I expect as the following invalid
strings are not caught (for example):
E56864
erjhj

The xform header is standard. Am I missing something?

<h:html xmlns="http://www.w3.org/2002/xforms" xmlns:h="
http://www.w3.org/1999/xhtml" xmlns:ev="
http://www.w3.org/2001/xml-events" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:jr="http://openrosa.org/javarosa
">
<h:head>
<h:title>Test02</h:title>
...

On Mon, May 9, 2011 at 12:15 AM, Carl Hartung carlhartung@gmail.comwrote:

You could also use a regular expression, instead. Something like:
regex(. , '[A-Za-z]{4}')

On Sat, May 7, 2011 at 6:53 PM, Mitch Sundt msundt@cs.washington.eduwrote:

I'm not sure string length constraints are in the version of the
javarosa libraries shipping with the current ODK Collect. I believe the
constraint should be "stringlength(.) &eq; 4"

Mitch

On Fri, May 6, 2011 at 4:26 PM, James Dailey jamespdailey@gmail.comwrote:

Clint - Thanks.

On Fri, May 6, 2011 at 3:30 PM, Clint Tseng cxlt@cs.washington.eduwrote:

Hi James:

No, Build does not yet support branching. It's a feature that I want
to build right from a usability perspective, and I'm still working through
how best to do that. I would ballpark it at 2 or 3 months out, but I can't
commit to anything just yet.

ok. FYI - the branch button at the bottom is confusing.

For now, you'll want to use the relevance field (which specifies
the skip logic) in the advanced section of controls. This is the same thing
as branching. Note, though, that your skip logic won't automatically convert
to branches when the feature gets added.

Ah. Ok. I'm following threads on that like
http://groups.google.com/group/opendatakit-developers/browse_thread/thread/ed26de0602295edc/952966b30e3b55a7?#952966b30e3b55a7

For the text length, if you require the length to be at least 4
inclusive as well as at most 4 inclusive, you'll get the behavior you want.

hmm..... I don't think its behaving as expected. I don't get any
warnings when I exceed 4 characters in that field.

=4 & <= 4 should give me exactly 4. Is there another way to write
that? Does constraint apply to string.length by default?

Thanks,
—Clint

On Friday, May 6, 2011 at 2:17 PM, jpd wrote:

Hi all -

I'm creating new xforms for a new project and am on the learning
curve/
refresher. I'm leaning on these resources, they are great -
thanks!:

Questions:

  1. Is there a place for me to learn how to use the Grouping and
    Branchingg features? Is there a clear distinction between branching

and skip logic ?
1.a. Clint - is Branching working at http://build.opendatakit.org ?
I don't intuit how to use the feature.

  1. Another build question - constraint on text length?
    using a constraint for min and max length of a data entry field. I
    was looking to constrain the response to exactly four. "Valid lengths
    for this user input of this control."

  2. In Kobo formdesigner by Neil H. , the use of Boolean is indicated.
    Is that supported in ODK Collect? I'm only seeing type="select1" for
    boolean type questions in the sample forms.

Thanks.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile

--
James Dailey
skype: jdailey
+1 206 234 8435 mobile


  1. a-zA-Z0-9 ↩︎

hi james,

i've put my responses inline.

I noticed that it is possible to make the LOCATION field "read only" in ODK Build. I think this should be avoided in UI. I thought it meant you would allow the lat long to be machine determined and then allow the user to edit the location. Removing "read only" enables the device to read GPS location.

i can see how this is confusing. that said, read only is the same idea in all prompts -- it's a prompt where you cannot change the stored value.

Also, my users are reporting that the GPS location feature is not working reliably. They restart the phone and it works, so I'm not sure what this means. They do have GSP status app and report that is working and giving good results even as the ODK Collect fails on location. What other info should I collect from them. I believe they're using Android 2.2 on HTC devices.

is it stock android or cyanogenmod? does it just take a long time to get lock? what is the accuracy? does it fail in a reliable way?

Cyrillic font
In ODK Build, if you enter Cyrillic characters it seems to save it incorrectly in terms of encoding. i.e. when I Export to Download or when I Export to Aggregate I get garbage in the form_.xml and ODK Collect. I tried working around this by editing the XML form in text editor and then saving that as UTF-8. Still when I upload to Aggregate and then download to Collect, I get garbage in the strings.

Байршлын тэмдэглэл (Record Location)
Бүтээгдэхүүн байгаа эсэх? (Device Present?)
Үгүй (No)
Тийм (Yes)

please file a bug report and clint will add it to his queue.

Valid xform
The ODK Validator when applied to the downloaded xml tells me the xform is valid but gives a warning about the Id.

that is correct behavior. if the warning bothers you, use xmlns instead of id in the form.

Translation framework in Collect
Translation of Collect menu and navigation to Mongolian Cyrillic - is this possible? I mean the menu and instructions like "To navigate, swipe..." and buttons like "Save Data and Exit" at the end.

it is likely possible. you'll have to translate all the strings and store it in the source. http://developer.android.com/guide/topics/resources/localization.html. if android doesn't support the language, you'll need to install something like customlocale. http://android.stackexchange.com/questions/6736/how-can-i-set-the-locale-and-language has tips.

Yaw - thanks for your help.

Also, my users are reporting that the GPS location feature is not
working reliably. They restart the phone and it works, so I'm not sure
what this means. They do have GSP status app and report that is working and
giving good results even as the ODK Collect fails on location. What other
info should I collect from them. I believe they're using Android 2.2 on HTC
devices.

is it stock android or cyanogenmod? does it just take a long time to get
lock? what is the accuracy? does it fail in a reliable way?

We're still having problems with generating a Location in the field. My
users are reporting a consistent failure when clicking on Location in the
xform, even though they are getting GPS signals via GPS Status. They get
an general fault: "According to GPS status, I had at least eight satellites
locked in, however the app quit 12 times in a row each time I tried to log
in the GPS coordinates. The error message reads: 'The application ODK
Collect (process org.odk.collect.android) has stopped unexpectedly. Please
try again.' "

I am unable to reproduce the error on my device so am wondering about how to
proceed with troubleshooting.

Here is what I know:

They are using a locally purchased phone in Mongolia.

Phone: HTC Wildfire A3333
Android: 2.2.1
ODK Collect: 1.1.5

Kernel: 2.6.32.21-g6c55ee4
htc-kernel@and18-2 #1

*Potential sources of the error as I understand it: *

  1. Xform code. I used ODKBuild to create it and validator as well. Here is
    the link http://dpaste.com/556641/

<h:html xmlns="http://www.w3.org/2002/xforms" xmlns:h="
http://www.w3.org/1999/xhtml" xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:jr="
http://openrosa.org/javarosa">

  1. Android OS or Kernel ?? These ok?

  2. Version of ODK ok?

  3. Random environmental condition

On the random environmental conditions, I wondered if the towers could be
confusing the location() call by offering their own locations, which are
almost certainly to be mistakenly set (as in most developing countries).
Vodoo?

Is there a way to get the log of the error from my field worker's phone?

Regards,

James

hey james,

i don't think the sources of error you describe apply to the problem
you are seeing. a log of the error is our best option at this point.

use http://code.google.com/p/android-log-collector/downloads/list (or
https://market.android.com/details?id=org.jtb.alogcat if you are on
market) to capture the log after the app crashes and email it (or save
it). if the phone doesn't have a way to send that email, then you'll
need to install the android developer tools (adb) and run 'adb logcat'
to get the log.

yaw

··· On Mon, Jun 20, 2011 at 18:35, James Dailey wrote: > Yaw - thanks for your help. > > > Also, my users are reporting that the GPS location feature is not > working reliably. They restart the phone and it works, so I'm not sure > what this means. They do have GSP status app and report that is working and > giving good results even as the ODK Collect fails on location. What other > info should I collect from them. I believe they're using Android 2.2 on HTC > devices. >> >> is it stock android or cyanogenmod? does it just take a long time to get >> lock? what is the accuracy? does it fail in a reliable way? >> > > We're still having problems with generating a Location in the field. My > users are reporting a consistent failure when clicking on Location in the > xform, even though they are getting GPS signals via GPS Status. They get > an general fault: "According to GPS status, I had at least eight satellites > locked in, however the app quit 12 times in a row each time I tried to log > in the GPS coordinates. The error message reads: 'The application ODK > Collect (process org.odk.collect.android) has stopped unexpectedly. Please > try again.' " > > I am unable to reproduce the error on my device so am wondering about how to > proceed with troubleshooting. > > Here is what I know: > > They are using a locally purchased phone in Mongolia. > > Phone: HTC Wildfire A3333 > Android: 2.2.1 > ODK Collect: 1.1.5 > > Kernel: 2.6.32.21-g6c55ee4 > htc-kernel@and18-2 #1 > > Potential sources of the error as I understand it: > > 1. Xform code. I used ODKBuild to create it and validator as well. Here is > the link http://dpaste.com/556641/ > > xmlns:h="http://www.w3.org/1999/xhtml" > xmlns:ev="http://www.w3.org/2001/xml-events" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:jr="http://openrosa.org/javarosa"> > > relevant="not(selected(/data/dev_prsnt, '0'))" /> > > 2. Android OS or Kernel ?? These ok? > > 3. Version of ODK ok? > > 4. Random environmental condition > > On the random environmental conditions, I wondered if the towers could be > confusing the location() call by offering their own locations, which are > almost certainly to be mistakenly set (as in most developing countries). > Vodoo? > > Is there a way to get the log of the error from my field worker's phone? > > Regards, > James > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

Matt - you could do this.

James Dailey
+1 206 234 8435

hey james,

i don't think the sources of error you describe apply to the problem
you are seeing. a log of the error is our best option at this point.

use http://code.google.com/p/android-log-collector/downloads/list (or
https://market.android.com/details?id=org.jtb.alogcat if you are on
market) to capture the log after the app crashes and email it (or save
it). if the phone doesn't have a way to send that email, then you'll
need to install the android developer tools (adb) and run 'adb logcat'
to get the log.

yaw

Yaw - thanks for your help.

Also, my users are reporting that the GPS location feature is not
working reliably. They restart the phone and it works, so I'm not sure
what this means. They do have GSP status app and report that is working
and
giving good results even as the ODK Collect fails on location. What
other
info should I collect from them. I believe they're using Android 2.2 on
HTC
devices.

is it stock android or cyanogenmod? does it just take a long time to get
lock? what is the accuracy? does it fail in a reliable way?

We're still having problems with generating a Location in the field. My
users are reporting a consistent failure when clicking on Location in the
xform, even though they are getting GPS signals via GPS Status. They
get
an general fault: "According to GPS status, I had at least eight
satellites
locked in, however the app quit 12 times in a row each time I tried to
log
in the GPS coordinates. The error message reads: 'The application ODK
Collect (process org.odk.collect.android) has stopped unexpectedly.
Please
try again.' "

I am unable to reproduce the error on my device so am wondering about how
to
proceed with troubleshooting.

Here is what I know:

They are using a locally purchased phone in Mongolia.

Phone: HTC Wildfire A3333
Android: 2.2.1
ODK Collect: 1.1.5

Kernel: 2.6.32.21-g6c55ee4
htc-kernel@and18-2 #1

Potential sources of the error as I understand it:

  1. Xform code. I used ODKBuild to create it and validator as well. Here
    is
··· Sent from my "smart" phone. On Jun 21, 2011 3:38 AM, "Yaw Anokwa" wrote: > On Mon, Jun 20, 2011 at 18:35, James Dailey wrote: >> the link http://dpaste.com/556641/ >> >> > xmlns:h="http://www.w3.org/1999/xhtml" >> xmlns:ev="http://www.w3.org/2001/xml-events" >> xmlns:xsd="http://www.w3.org/2001/XMLSchema" >> xmlns:jr="http://openrosa.org/javarosa"> >> >> > relevant="not(selected(/data/dev_prsnt, '0'))" /> >> >> 2. Android OS or Kernel ?? These ok? >> >> 3. Version of ODK ok? >> >> 4. Random environmental condition >> >> On the random environmental conditions, I wondered if the towers could be >> confusing the location() call by offering their own locations, which are >> almost certainly to be mistakenly set (as in most developing countries). >> Vodoo? >> >> Is there a way to get the log of the error from my field worker's phone? >> >> Regards, >> James >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en

yaw -

We're getting there. Matt, (my user in Mongolia) updated the ODK to
1.1.7beta and the GPS location error went away. I still cannot reproduce
his errors on my android.

He NOW has a new error on "Send Finished Forms" .
odk_dev: FAILED: generic excpetion. great
odK_dev: FAILED: generic excpetion. great

I uploaded a portion of the log from his phone that mentions ODK plus dozens
of events after - the full log couldn't be dpasted, let me know if this is
sufficient http://dpaste.com/562043/. I'm unable to reproduce his error on
my phone using 1.1.7beta2.

In the log, the timestamps for start and finish of ODK is 07-01 22:21:31.318

through 07-01 22:35:32.138 . Mongolian time (15 hrs ahead).

Not sure if this belongs on this list or the dev list now.

I am thinking now that he needs to fully delete all data and the application
and re-install, and then download the forms again. In terms of
troubleshooting on the original Location error, I'm going to call that
closed for now.

  • James
··· On Tue, Jun 21, 2011 at 3:38 AM, Yaw Anokwa wrote:

hey james,

i don't think the sources of error you describe apply to the problem
you are seeing. a log of the error is our best option at this point.

use http://code.google.com/p/android-log-collector/downloads/list (or
https://market.android.com/details?id=org.jtb.alogcat if you are on
market) to capture the log after the app crashes and email it (or save
it). if the phone doesn't have a way to send that email, then you'll
need to install the android developer tools (adb) and run 'adb logcat'
to get the log.

yaw

On Mon, Jun 20, 2011 at 18:35, James Dailey jamespdailey@gmail.com wrote:

Yaw - thanks for your help.

Also, my users are reporting that the GPS location feature is not
working reliably. They restart the phone and it works, so I'm not sure
what this means. They do have GSP status app and report that is working
and
giving good results even as the ODK Collect fails on location. What
other
info should I collect from them. I believe they're using Android 2.2 on
HTC
devices.

is it stock android or cyanogenmod? does it just take a long time to get
lock? what is the accuracy? does it fail in a reliable way?

We're still having problems with generating a Location in the field. My
users are reporting a consistent failure when clicking on Location in the
xform, even though they are getting GPS signals via GPS Status. They
get
an general fault: "According to GPS status, I had at least eight
satellites
locked in, however the app quit 12 times in a row each time I tried to
log
in the GPS coordinates. The error message reads: 'The application ODK
Collect (process org.odk.collect.android) has stopped unexpectedly.
Please
try again.' "

I am unable to reproduce the error on my device so am wondering about how
to
proceed with troubleshooting.

Here is what I know:

They are using a locally purchased phone in Mongolia.

Phone: HTC Wildfire A3333
Android: 2.2.1
ODK Collect: 1.1.5

Kernel: 2.6.32.21-g6c55ee4
htc-kernel@and18-2 #1

Potential sources of the error as I understand it:

  1. Xform code. I used ODKBuild to create it and validator as well. Here
    is
    the link http://dpaste.com/556641/

<h:html xmlns="http://www.w3.org/2002/xforms"
xmlns:h="http://www.w3.org/1999/xhtml"
xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:jr="http://openrosa.org/javarosa">

  1. Android OS or Kernel ?? These ok?

  2. Version of ODK ok?

  3. Random environmental condition

On the random environmental conditions, I wondered if the towers could be
confusing the location() call by offering their own locations, which are
almost certainly to be mistakenly set (as in most developing countries).
Vodoo?

Is there a way to get the log of the error from my field worker's phone?

Regards,
James

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
James Dailey
skype: jdailey

hi james,

the log doesn't have the relevant crash. can you email the log
directly or file a bug at
http://code.google.com/p/opendatakit/issues/list and attach the log
there.

yaw

··· On Fri, Jul 1, 2011 at 16:40, James Dailey wrote: > yaw - > > We're getting there. Matt, (my user in Mongolia) updated the ODK to > 1.1.7beta and the GPS location error went away. I still cannot reproduce > his errors on my android. > > He NOW has a new error on "Send Finished Forms" . > odk_dev: FAILED: generic excpetion. great > odK_dev: FAILED: generic excpetion. great > > I uploaded a portion of the log from his phone that mentions ODK plus dozens > of events after - the full log couldn't be dpasted, let me know if this is > sufficient http://dpaste.com/562043/. I'm unable to reproduce his error on > my phone using 1.1.7beta2. > > In the log, the timestamps for start and finish of ODK is 07-01 22:21:31.318 > through 07-01 22:35:32.138 . Mongolian time (15 hrs ahead). > > Not sure if this belongs on this list or the dev list now. > > I am thinking now that he needs to fully delete all data and the application > and re-install, and then download the forms again. In terms of > troubleshooting on the original Location error, I'm going to call that > closed for now. > > - James > > > > > On Tue, Jun 21, 2011 at 3:38 AM, Yaw Anokwa wrote: >> >> hey james, >> >> i don't think the sources of error you describe apply to the problem >> you are seeing. a log of the error is our best option at this point. >> >> use http://code.google.com/p/android-log-collector/downloads/list (or >> https://market.android.com/details?id=org.jtb.alogcat if you are on >> market) to capture the log after the app crashes and email it (or save >> it). if the phone doesn't have a way to send that email, then you'll >> need to install the android developer tools (adb) and run 'adb logcat' >> to get the log. >> >> yaw >> >> On Mon, Jun 20, 2011 at 18:35, James Dailey wrote: >> > Yaw - thanks for your help. >> > >> > > Also, my users are reporting that the GPS location feature is not >> > working reliably. They restart the phone and it works, so I'm not sure >> > what this means. They do have GSP status app and report that is working >> > and >> > giving good results even as the ODK Collect fails on location. What >> > other >> > info should I collect from them. I believe they're using Android 2.2 on >> > HTC >> > devices. >> >> >> >> is it stock android or cyanogenmod? does it just take a long time to >> >> get >> >> lock? what is the accuracy? does it fail in a reliable way? >> >> >> > >> > We're still having problems with generating a Location in the field. My >> > users are reporting a consistent failure when clicking on Location in >> > the >> > xform, even though they are getting GPS signals via GPS Status. They >> > get >> > an general fault: "According to GPS status, I had at least eight >> > satellites >> > locked in, however the app quit 12 times in a row each time I tried to >> > log >> > in the GPS coordinates. The error message reads: 'The application ODK >> > Collect (process org.odk.collect.android) has stopped unexpectedly. >> > Please >> > try again.' " >> > >> > I am unable to reproduce the error on my device so am wondering about >> > how to >> > proceed with troubleshooting. >> > >> > Here is what I know: >> > >> > They are using a locally purchased phone in Mongolia. >> > >> > Phone: HTC Wildfire A3333 >> > Android: 2.2.1 >> > ODK Collect: 1.1.5 >> > >> > Kernel: 2.6.32.21-g6c55ee4 >> > htc-kernel@and18-2 #1 >> > >> > Potential sources of the error as I understand it: >> > >> > 1. Xform code. I used ODKBuild to create it and validator as well. >> > Here is >> > the link http://dpaste.com/556641/ >> > >> > > > xmlns:h="http://www.w3.org/1999/xhtml" >> > xmlns:ev="http://www.w3.org/2001/xml-events" >> > xmlns:xsd="http://www.w3.org/2001/XMLSchema" >> > xmlns:jr="http://openrosa.org/javarosa"> >> > >> > > > relevant="not(selected(/data/dev_prsnt, '0'))" /> >> > >> > 2. Android OS or Kernel ?? These ok? >> > >> > 3. Version of ODK ok? >> > >> > 4. Random environmental condition >> > >> > On the random environmental conditions, I wondered if the towers could >> > be >> > confusing the location() call by offering their own locations, which are >> > almost certainly to be mistakenly set (as in most developing countries). >> > Vodoo? >> > >> > Is there a way to get the log of the error from my field worker's phone? >> > >> > Regards, >> > James >> > >> > -- >> > Post: opendatakit@googlegroups.com >> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> > Options: http://groups.google.com/group/opendatakit?hl=en >> > >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en > > > > -- > James Dailey > skype: jdailey > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >