Send filled forms to monitor

Hi,
We are planning to use ODK collect and aggregate for survey. What we expect is that our enumerator teams will collect the data from the field and our monitors will pick 5 to 10% random respondent to cross check the validity of the data. Now my question is that is there a way to send data back to monitor as filled form for verification.

Please suggest.
Looking forward.
Thanks
Majid

When you say "send data back to monitor as filled form for verification." -
do you mean that you want the monitor will see the form as it appears in
ODK collect? Rather than to see the 'final' data as it would appear in
Aggregate?

I think that may be possible but it is probably a bit of a complex task for
what could be achieved just using Aggregate. Somehow selecting some
responses in aggregate and then sending them to ODK collect as incomplete
responses, so they can be viewed (and edited again)

That's the extent of my knowledge! I would probably stick with Aggregate
for monitoring.

Hi Majid,

For this sort of baseline and follow-up form filling, I find
preloading forms via CSV http://xlsform.org/#pre-loading-csv-data
works great and your follow up form can have as much or as little data
from the baseline form as you need.

Yaw

··· On Tue, Apr 11, 2017 at 1:23 AM, Richard Fletcher wrote: > When you say "send data back to monitor as filled form for verification." - > do you mean that you want the monitor will see the form as it appears in ODK > collect? Rather than to see the 'final' data as it would appear in > Aggregate? > > I think that may be possible but it is probably a bit of a complex task for > what could be achieved just using Aggregate. Somehow selecting some > responses in aggregate and then sending them to ODK collect as incomplete > responses, so they can be viewed (and edited again) > > That's the extent of my knowledge! I would probably stick with Aggregate for > monitoring. > > -- > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@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+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.

Thanks for your response.My main objective is to verify that the enumerator has collected real information. For this purpose here is our workflow.

  1. Around 80 enumerators will collect information in different locations (Districts, Tehsils, Villages)2. We will take 5% random forms in one village for verification.3. One village will be assigned to one Monitor for verification.4. The Monitor will check each question in the form and verify if it is correct yes or no.5. Once the the verification data is with us we can calculate statistics, how many forms are fully/partially verified.
    Now as per my understanding we can extract 5% data group by village, now how to put it into verification forms(same form with additional verification attributes) and send it back to specific Monitor.
    I hope you got my workflow.Please suggest what step should I take to implement this workflow.
    Thanks,Majid

Hi Majid,

For this sort of baseline and follow-up form filling, I find
preloading forms via CSV http://xlsform.org/#pre-loading-csv-data
works great and your follow up form can have as much or as little data
from the baseline form as you need.

Yaw

··· On Friday, 14 April 2017, 10:41, Yaw Anokwa wrote:

On Tue, Apr 11, 2017 at 1:23 AM, Richard Fletcher skutbag@hotmail.com wrote:

When you say "send data back to monitor as filled form for verification." -
do you mean that you want the monitor will see the form as it appears in ODK
collect? Rather than to see the 'final' data as it would appear in
Aggregate?

I think that may be possible but it is probably a bit of a complex task for
what could be achieved just using Aggregate. Somehow selecting some
responses in aggregate and then sending them to ODK collect as incomplete
responses, so they can be viewed (and edited again)

That's the extent of my knowledge! I would probably stick with Aggregate for
monitoring.

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

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


You received this message because you are subscribed to a topic in the Google Groups "ODK Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/opendatakit/ZKawksITiZY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi Majid,

I stand by my earlier recommendation. The approach I'd take is as follows.

  1. Collect the data normally, but be sure to include some unique
    identifier for each participant. Of those results, take your 5% random
    in each village.

  2. To make the verification form, take the original form, and keep the
    original questions, but add a verification question (select one,
    yes/no) for each original question.

  3. You can use CSV preloading (e.g.,
    http://xlsform.org/#pre-loading-csv-data) to load the values for those
    original questions. Make these values read-only.

  4. In the CSV, include the unique identifier for the participant and a
    unique identifier for the enumerator who is assigned to the
    participant in the CSV. These two IDs can be used to look up the
    original data and load the data into the verification form.

  5. Have the verification enumerators download the verification form.
    The verification form can then be used to check the values in the
    original form and mark it correct (e.g., yes/no). Once the data is
    submitted, you can just count the number of yes/no.

Try this process with a 2-3 question form and see how it feels.

Yaw

··· On Thu, Apr 13, 2017 at 11:49 PM, MK Swati wrote: > Thanks for your response. > My main objective is to verify that the enumerator has collected real > information. For this purpose here is our workflow. > > 1. Around 80 enumerators will collect information in different locations > (Districts, Tehsils, Villages) > 2. We will take 5% random forms in one village for verification. > 3. One village will be assigned to one Monitor for verification. > 4. The Monitor will check each question in the form and verify if it is > correct yes or no. > 5. Once the the verification data is with us we can calculate statistics, > how many forms are fully/partially verified. > > Now as per my understanding we can extract 5% data group by village, now how > to put it into verification forms(same form with additional verification > attributes) and send it back to specific Monitor. > > I hope you got my workflow. > Please suggest what step should I take to implement this workflow. > > Thanks, > Majid > > > > > > > On Friday, 14 April 2017, 10:41, Yaw Anokwa wrote: > > > Hi Majid, > > For this sort of baseline and follow-up form filling, I find > preloading forms via CSV http://xlsform.org/#pre-loading-csv-data > works great and your follow up form can have as much or as little data > from the baseline form as you need. > > Yaw > > On Tue, Apr 11, 2017 at 1:23 AM, Richard Fletcher wrote: >> When you say "send data back to monitor as filled form for verification." >> - >> do you mean that you want the monitor will see the form as it appears in >> ODK >> collect? Rather than to see the 'final' data as it would appear in >> Aggregate? >> >> I think that may be possible but it is probably a bit of a complex task >> for >> what could be achieved just using Aggregate. Somehow selecting some >> responses in aggregate and then sending them to ODK collect as incomplete >> responses, so they can be viewed (and edited again) >> >> That's the extent of my knowledge! I would probably stick with Aggregate >> for >> monitoring. >> >> -- >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@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+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en > > --- > You received this message because you are subscribed to a topic in the > Google Groups "ODK Community" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/opendatakit/ZKawksITiZY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > opendatakit+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@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+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.

Oh, and as far as more automated ways to verify accuracy, we are
working on a feature at
https://github.com/opendatakit/collect/issues/257 that will collect
timing/location/audio data in the background.

Yaw

··· On Fri, Apr 21, 2017 at 6:06 PM, Yaw Anokwa wrote: > Hi Majid, > > I stand by my earlier recommendation. The approach I'd take is as follows. > > 1. Collect the data normally, but be sure to include some unique > identifier for each participant. Of those results, take your 5% random > in each village. > > 2. To make the verification form, take the original form, and keep the > original questions, but add a verification question (select one, > yes/no) for each original question. > > 3. You can use CSV preloading (e.g., > http://xlsform.org/#pre-loading-csv-data) to load the values for those > original questions. Make these values read-only. > > 4. In the CSV, include the unique identifier for the participant and a > unique identifier for the enumerator who is assigned to the > participant in the CSV. These two IDs can be used to look up the > original data and load the data into the verification form. > > 5. Have the verification enumerators download the verification form. > The verification form can then be used to check the values in the > original form and mark it correct (e.g., yes/no). Once the data is > submitted, you can just count the number of yes/no. > > Try this process with a 2-3 question form and see how it feels. > > Yaw > > On Thu, Apr 13, 2017 at 11:49 PM, MK Swati wrote: >> Thanks for your response. >> My main objective is to verify that the enumerator has collected real >> information. For this purpose here is our workflow. >> >> 1. Around 80 enumerators will collect information in different locations >> (Districts, Tehsils, Villages) >> 2. We will take 5% random forms in one village for verification. >> 3. One village will be assigned to one Monitor for verification. >> 4. The Monitor will check each question in the form and verify if it is >> correct yes or no. >> 5. Once the the verification data is with us we can calculate statistics, >> how many forms are fully/partially verified. >> >> Now as per my understanding we can extract 5% data group by village, now how >> to put it into verification forms(same form with additional verification >> attributes) and send it back to specific Monitor. >> >> I hope you got my workflow. >> Please suggest what step should I take to implement this workflow. >> >> Thanks, >> Majid >> >> >> >> >> >> >> On Friday, 14 April 2017, 10:41, Yaw Anokwa wrote: >> >> >> Hi Majid, >> >> For this sort of baseline and follow-up form filling, I find >> preloading forms via CSV http://xlsform.org/#pre-loading-csv-data >> works great and your follow up form can have as much or as little data >> from the baseline form as you need. >> >> Yaw >> >> On Tue, Apr 11, 2017 at 1:23 AM, Richard Fletcher wrote: >>> When you say "send data back to monitor as filled form for verification." >>> - >>> do you mean that you want the monitor will see the form as it appears in >>> ODK >>> collect? Rather than to see the 'final' data as it would appear in >>> Aggregate? >>> >>> I think that may be possible but it is probably a bit of a complex task >>> for >>> what could be achieved just using Aggregate. Somehow selecting some >>> responses in aggregate and then sending them to ODK collect as incomplete >>> responses, so they can be viewed (and edited again) >>> >>> That's the extent of my knowledge! I would probably stick with Aggregate >>> for >>> monitoring. >>> >>> -- >>> -- >>> Post: opendatakit@googlegroups.com >>> Unsubscribe: opendatakit+unsubscribe@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+unsubscribe@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "ODK Community" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/opendatakit/ZKawksITiZY/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> opendatakit+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@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+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout.