Possible to Have a Question which is NOT Saved?

Dear all,
In my form, I have an input widget where I want the enumerator to fill
in the interviewees ID. However to avoid Transcription errors, I want
the enumerator to confirm the ID by typing it again on the following
page and if the two ID's match then the enumerator can continue, else
a message tells the enumerator to go back and double check the entered
ID. Considering that I only want the second ID entered for comparison
and do not necessarily want to save two IDs which are exactly the same
in two different columns, how can I make the second input widget NOT
save its value, only be used to make comparisons?

Thanks in advance,
Tumaini

There is a tag that lets you specify the elements you
care to have submitted the rest are ignored (think of them as
intermediate value holders).

I am personally not clear how much of it is currently implemented in
collect, others can chime in. Here was the previous email thread on
the subject.
https://groups.google.com/group/opendatakit/tree/browse_frm/month/2011-10/78e1373cb592701d

On ODK's Xform guidelines page in stricter syntax it talks about
http://opendatakit.org/help/form-design/guidelines/ in the "Stricter
Form Syntax - ODK Aggregate 1.0" item 3 talks about the submission
tag.

We should document how to do it better in the guidelines, so I filed an issue.
http://code.google.com/p/opendatakit/issues/detail?id=578

Waylon

··· On Sun, May 20, 2012 at 2:09 PM, Tumaini Kilimba wrote: > Dear all, > In my form, I have an input widget where I want the enumerator to fill > in the interviewees ID. However to avoid Transcription errors, I want > the enumerator to confirm the ID by typing it again on the following > page and if the two ID's match then the enumerator can continue, else > a message tells the enumerator to go back and double check the entered > ID. Considering that I only want the second ID entered for comparison > and do not necessarily want to save two IDs which are exactly the same > in two different columns, how can I make the second input widget NOT > save its value, only be used to make comparisons? > > Thanks in advance, > Tumaini > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en

Ok thanks, will have a look

··· On May 21, 12:34 am, "W. Brunette" wrote: > There is a tag that lets you specify the elements you > care to have submitted the rest are ignored (think of them as > intermediate value holders). > > I am personally not clear how much of it is currently implemented in > collect, others can chime in. Here was the previous email thread on > the subject.https://groups.google.com/group/opendatakit/tree/browse_frm/month/201... > > On ODK's Xform guidelines page in stricter syntax it talks abouthttp://opendatakit.org/help/form-design/guidelines/in the "Stricter > Form Syntax - ODK Aggregate 1.0" item 3 talks about the submission > tag. > > We should document how to do it better in the guidelines, so I filed an issue.http://code.google.com/p/opendatakit/issues/detail?id=578 > > Waylon > > > > > > > > On Sun, May 20, 2012 at 2:09 PM, Tumaini Kilimba wrote: > > Dear all, > > In my form, I have an input widget where I want the enumerator to fill > > in the interviewees ID. However to avoid Transcription errors, I want > > the enumerator to confirm the ID by typing it again on the following > > page and if the two ID's match then the enumerator can continue, else > > a message tells the enumerator to go back and double check the entered > > ID. Considering that I only want the second ID entered for comparison > > and do not necessarily want to save two IDs which are exactly the same > > in two different columns, how can I make the second input widget NOT > > save its value, only be used to make comparisons? > > > Thanks in advance, > > Tumaini > > > -- > > Post: opendatakit@googlegroups.com > > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > > Options:http://groups.google.com/group/opendatakit?hl=en