Data changes on the fly

In a recent survey, the enumerator would first register a farmer/hh. Part
of the registration survey is asking the farmer how many cattle they have.
We followed the farmer registration survey with a cattle registration
survey that was linked the farmer registration survey to auto populate the
number of cattle. Let me explain the process. In the farmer registration
survey we asked how many cattle they have and the sex. These responses
were then linked to the more detailed cattle registration survey to provide
the baseline information to build on in that survey. Several times, when
the enumerator arrived at the pen the numbers of cattle were sometimes
different to the farmer rego survey responses. In many instances the
enumerator had already uploaded the farmer rego survey to the cloud and the
cattle registration survey was already auto populated on the tablet. My question
is; Is there a way to update the cattle registration survey while still in
the field and have this data update the farmer registration survey? Can we
add or remove cattle from the cattle rego survey and this will update the
linked cattle numbers in the farmer rego survey?
I’m aware that updating
the data in CommCare HQ is possible but not really practical in my view.
Too much room for error in communicating with field teams. I hope this
explanation is clear?!
Stuart

Hi Stewart

I assume that the farmer registration form creates a case for the farmer
and saves the number of cattle to a case property (lets call it
num_cattle). Then the cattle registration form loads this case property and
uses it as the bases for the number of repeats in the form.

The approach I’d suggest here is as follows:

  • In the cattle registration form load the ‘num_cattle’ property into a
    hidden field
  • Display the value of the hidden field to the user and ask them if it
    is correct
  • If they answer no then you can display a question asking them to enter
    the correct number
  • You can then have one more hidden field which calculates the actual
    number of cattle:
    • if(/data/number_correct = ‘yes’, /data/num_cattle_from_case,
      ’/data/corrected_num_cattle’)
  • Use this second hidden field as the basis for the repeat group count.

Best regards
Simon

··· On 19 May 2016 at 02:57, Stuart wrote:

In a recent survey, the enumerator would first register a farmer/hh. Part
of the registration survey is asking the farmer how many cattle they have.
We followed the farmer registration survey with a cattle registration
survey that was linked the farmer registration survey to auto populate the
number of cattle. Let me explain the process. In the farmer registration
survey we asked how many cattle they have and the sex. These responses
were then linked to the more detailed cattle registration survey to provide
the baseline information to build on in that survey. Several times, when
the enumerator arrived at the pen the numbers of cattle were sometimes
different to the farmer rego survey responses. In many instances the
enumerator had already uploaded the farmer rego survey to the cloud and the
cattle registration survey was already auto populated on the tablet. My question
is; Is there a way to update the cattle registration survey while still in
the field and have this data update the farmer registration survey? Can we
add or remove cattle from the cattle rego survey and this will update the
linked cattle numbers in the farmer rego survey?
I’m aware that updating
the data in CommCare HQ is possible but not really practical in my view.
Too much room for error in communicating with field teams. I hope this
explanation is clear?!
Stuart


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Simon Kelly
Senior Engineer | Dimagi South Africa

Thanks Simon. Yes , your analysis of how the case properties are linked between the two forms is correct. I understand your solution and will adopt this approach next time.

One final question. I assume the number of cattle cannot be updated in the farmer rego form based on the updated case (number of cattle) in the cattle rego form? This would have to be done through CommCare HQ?

The important thing is we have enough repeats in the cattle rego form to capture the correct amount of cattle.

Thanks for your advice. Very helpful.

Regards,

Stuart

··· From: commcare-users@googlegroups.com [mailto:commcare-users@googlegroups.com] On Behalf Of Simon Kelly Sent: Thursday, 19 May 2016 8:36 PM To: commcare-users@googlegroups.com Subject: Re: Data changes on the fly

Hi Stewart

I assume that the farmer registration form creates a case for the farmer and saves the number of cattle to a case property (lets call it num_cattle). Then the cattle registration form loads this case property and uses it as the bases for the number of repeats in the form.

The approach I’d suggest here is as follows:

  • In the cattle registration form load the ‘num_cattle’ property into a hidden field

  • Display the value of the hidden field to the user and ask them if it is correct

  • If they answer no then you can display a question asking them to enter the correct number

  • You can then have one more hidden field which calculates the actual number of cattle:

  • if(/data/number_correct = ‘yes’, /data/num_cattle_from_case, ‘/data/corrected_num_cattle’)

  • Use this second hidden field as the basis for the repeat group count.

Best regards

Simon

On 19 May 2016 at 02:57, Stuart <stuhiggins@bigpond.com mailto:stuhiggins@bigpond.com > wrote:

In a recent survey, the enumerator would first register a farmer/hh. Part of the registration survey is asking the farmer how many cattle they have. We followed the farmer registration survey with a cattle registration survey that was linked the farmer registration survey to auto populate the number of cattle. Let me explain the process. In the farmer registration survey we asked how many cattle they have and the sex. These responses were then linked to the more detailed cattle registration survey to provide the baseline information to build on in that survey. Several times, when the enumerator arrived at the pen the numbers of cattle were sometimes different to the farmer rego survey responses. In many instances the enumerator had already uploaded the farmer rego survey to the cloud and the cattle registration survey was already auto populated on the tablet. My question is; Is there a way to update the cattle registration survey while still in the field and have this data update the farmer registration survey? Can we add or remove cattle from the cattle rego survey and this will update the linked cattle numbers in the farmer rego survey? I’m aware that updating the data in CommCare HQ is possible but not really practical in my view. Too much room for error in communicating with field teams. I hope this explanation is clear?!

Stuart


You received this message because you are subscribed to the Google Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-users+unsubscribe@googlegroups.com mailto:commcare-users+unsubscribe@googlegroups.com .
For more options, visit https://groups.google.com/d/optout.

Simon Kelly

Senior Engineer | Dimagi South Africa


You received this message because you are subscribed to the Google Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-users+unsubscribe@googlegroups.com mailto:commcare-users+unsubscribe@googlegroups.com .
For more options, visit https://groups.google.com/d/optout.

Hi Stuart

Correct, you won’t be able to update the value in the farmer registration
form but you can update the value in the case.

I’m sure you know this already but you can make the changes to the
application you are currently using and then update the application on the
mobile user’s phone without loosing any data or anything like that.

Glad that I could be service.
Simon

··· On 19 May 2016 at 13:21, Stuart Higgins < s.higgins@agriculturaldevelopment.org> wrote:

Thanks Simon. Yes , your analysis of how the case properties are linked
between the two forms is correct. I understand your solution and will adopt
this approach next time.

One final question. I assume the number of cattle cannot be updated in the
farmer rego form based on the updated case (number of cattle) in the cattle
rego form? This would have to be done through CommCare HQ?

The important thing is we have enough repeats in the cattle rego form to
capture the correct amount of cattle.

Thanks for your advice. Very helpful.

Regards,

Stuart

From: commcare-users@googlegroups.com [mailto:
commcare-users@googlegroups.com] *On Behalf Of *Simon Kelly
Sent: Thursday, 19 May 2016 8:36 PM
To: commcare-users@googlegroups.com
Subject: Re: Data changes on the fly

Hi Stewart

I assume that the farmer registration form creates a case for the farmer
and saves the number of cattle to a case property (lets call it
num_cattle). Then the cattle registration form loads this case property and
uses it as the bases for the number of repeats in the form.

The approach I’d suggest here is as follows:

  • In the cattle registration form load the ‘num_cattle’ property into
    a hidden field

  • Display the value of the hidden field to the user and ask them if it
    is correct

  • If they answer no then you can display a question asking them to
    enter the correct number

  • You can then have one more hidden field which calculates the actual
    number of cattle:

  • if(/data/number_correct = ‘yes’, /data/num_cattle_from_case,
    ’/data/corrected_num_cattle’)

  • Use this second hidden field as the basis for the repeat group count.

Best regards

Simon

On 19 May 2016 at 02:57, Stuart stuhiggins@bigpond.com wrote:

In a recent survey, the enumerator would first register a farmer/hh. Part
of the registration survey is asking the farmer how many cattle they have.
We followed the farmer registration survey with a cattle registration
survey that was linked the farmer registration survey to auto populate the
number of cattle. Let me explain the process. In the farmer registration
survey we asked how many cattle they have and the sex. These responses
were then linked to the more detailed cattle registration survey to provide
the baseline information to build on in that survey. Several times, when
the enumerator arrived at the pen the numbers of cattle were sometimes
different to the farmer rego survey responses. In many instances the
enumerator had already uploaded the farmer rego survey to the cloud and the
cattle registration survey was already auto populated on the tablet. My question
is; Is there a way to update the cattle registration survey while still in
the field and have this data update the farmer registration survey? Can we
add or remove cattle from the cattle rego survey and this will update the
linked cattle numbers in the farmer rego survey?
I’m aware that updating
the data in CommCare HQ is possible but not really practical in my view.
Too much room for error in communicating with field teams. I hope this
explanation is clear?!

Stuart


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Simon Kelly

Senior Engineer | Dimagi South Africa


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Simon Kelly
Senior Engineer | Dimagi South Africa

Thanks Simon. Am aware we can update the application. The background to this is I am working closely with Anthony Connor preparing for a MasterClass on CommCare in Australia in a few weeks. The scenario I described was what we encountered during a pilot between CommCare and SurveyCTO late last year. I just wanted to see if there is a solution to what we encountered during our pilot last year. You’ve outlined the solution which is great.

I may be back in touch with some additional questions in the coming weeks.

Cheers

Stuart

··· From: commcare-users@googlegroups.com [mailto:commcare-users@googlegroups.com] On Behalf Of Simon Kelly Sent: Thursday, 19 May 2016 9:26 PM To: commcare-users@googlegroups.com Subject: Re: Data changes on the fly

Hi Stuart

Correct, you won’t be able to update the value in the farmer registration form but you can update the value in the case.

I’m sure you know this already but you can make the changes to the application you are currently using and then update the application on the mobile user’s phone without loosing any data or anything like that.

Glad that I could be service.

Simon

On 19 May 2016 at 13:21, Stuart Higgins <s.higgins@agriculturaldevelopment.org mailto:s.higgins@agriculturaldevelopment.org > wrote:

Thanks Simon. Yes , your analysis of how the case properties are linked between the two forms is correct. I understand your solution and will adopt this approach next time.

One final question. I assume the number of cattle cannot be updated in the farmer rego form based on the updated case (number of cattle) in the cattle rego form? This would have to be done through CommCare HQ?

The important thing is we have enough repeats in the cattle rego form to capture the correct amount of cattle.

Thanks for your advice. Very helpful.

Regards,

Stuart

From: commcare-users@googlegroups.com mailto:commcare-users@googlegroups.com [mailto:commcare-users@googlegroups.com mailto:commcare-users@googlegroups.com ] On Behalf Of Simon Kelly
Sent: Thursday, 19 May 2016 8:36 PM
To: commcare-users@googlegroups.com mailto:commcare-users@googlegroups.com
Subject: Re: Data changes on the fly

Hi Stewart

I assume that the farmer registration form creates a case for the farmer and saves the number of cattle to a case property (lets call it num_cattle). Then the cattle registration form loads this case property and uses it as the bases for the number of repeats in the form.

The approach I’d suggest here is as follows:

  • In the cattle registration form load the ‘num_cattle’ property into a hidden field

  • Display the value of the hidden field to the user and ask them if it is correct

  • If they answer no then you can display a question asking them to enter the correct number

  • You can then have one more hidden field which calculates the actual number of cattle:

  • if(/data/number_correct = ‘yes’, /data/num_cattle_from_case, ‘/data/corrected_num_cattle’)

  • Use this second hidden field as the basis for the repeat group count.

Best regards

Simon

On 19 May 2016 at 02:57, Stuart <stuhiggins@bigpond.com mailto:stuhiggins@bigpond.com > wrote:

In a recent survey, the enumerator would first register a farmer/hh. Part of the registration survey is asking the farmer how many cattle they have. We followed the farmer registration survey with a cattle registration survey that was linked the farmer registration survey to auto populate the number of cattle. Let me explain the process. In the farmer registration survey we asked how many cattle they have and the sex. These responses were then linked to the more detailed cattle registration survey to provide the baseline information to build on in that survey. Several times, when the enumerator arrived at the pen the numbers of cattle were sometimes different to the farmer rego survey responses. In many instances the enumerator had already uploaded the farmer rego survey to the cloud and the cattle registration survey was already auto populated on the tablet. My question is; Is there a way to update the cattle registration survey while still in the field and have this data update the farmer registration survey? Can we add or remove cattle from the cattle rego survey and this will update the linked cattle numbers in the farmer rego survey? I’m aware that updating the data in CommCare HQ is possible but not really practical in my view. Too much room for error in communicating with field teams. I hope this explanation is clear?!

Stuart


You received this message because you are subscribed to the Google Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-users+unsubscribe@googlegroups.com mailto:commcare-users+unsubscribe@googlegroups.com .
For more options, visit https://groups.google.com/d/optout.

Simon Kelly

Senior Engineer | Dimagi South Africa


You received this message because you are subscribed to the Google Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-users+unsubscribe@googlegroups.com mailto:commcare-users+unsubscribe@googlegroups.com .
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-users+unsubscribe@googlegroups.com mailto:commcare-users+unsubscribe@googlegroups.com .
For more options, visit https://groups.google.com/d/optout.

Simon Kelly

Senior Engineer | Dimagi South Africa


You received this message because you are subscribed to the Google Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-users+unsubscribe@googlegroups.com mailto:commcare-users+unsubscribe@googlegroups.com .
For more options, visit https://groups.google.com/d/optout.