I am just trying to figure out what the best approach is regarding my
look-up tables.
As part of the one project we have a cross-sectional study and a cohort
study.
Both studies are in a similar area however the cohort is going to be
visiting some villages that the cross-sectional doesn't .
Now we have almost finished data collection for the cross-sectional
baseline, and we now want to prepare the look-up table for the cohort.
Is it easier to just use the existing look-up table from the
cross-sectional and add the additional villages to that table and just
filer by User/Group
Or is it an option/better to add an additional separate look-up table for
the cohort?
Can someone please advise which is the best approach.
I don't have the exact details of how this would work in your app, but one
possibility would be to use the same lookup table but add a "study-arm"
property that is set to different values (cross-sectional/cohort), and then
filter the single lookup table in the app depending on the user's
information (you could either hard code this into the app if they are
different or use custom user data if they're the same).
···
On Thu, Feb 26, 2015 at 11:36 PM, Jessica Hall wrote:
Hi,
I am just trying to figure out what the best approach is regarding my
look-up tables.
As part of the one project we have a cross-sectional study and a cohort
study.
Both studies are in a similar area however the cohort is going to be
visiting some villages that the cross-sectional doesn't .
Now we have almost finished data collection for the cross-sectional
baseline, and we now want to prepare the look-up table for the cohort.
Is it easier to just use the existing look-up table from the
cross-sectional and add the additional villages to that table and just
filer by User/Group
Or is it an option/better to add an additional separate look-up table for
the cohort?
Can someone please advise which is the best approach.
I will have a a look at the links you posted and get back to you if I have
any further questions regarding the look-up tables.
I do have another issue regarding case management though.
I want to be able to save the previous answer to a question from the last
time I visited the mother in one form so that the next time you visit and
use the same form certain questions don't appear. Can you please clarify
how to do this. Despite following the help site I keep having difficulties
with this.
Many thanks,
Jess
···
On Saturday, February 28, 2015 at 12:47:31 AM UTC+11, Cory Zue wrote:
>
> Hey Jessica,
>
> I don't have the exact details of how this would work in your app, but one
> possibility would be to use the same lookup table but add a "study-arm"
> property that is set to different values (cross-sectional/cohort), and then
> filter the single lookup table in the app depending on the user's
> information (you could either hard code this into the app if they are
> different or use custom user data if they're the same).
>
> There's information on filtering here:
> https://help.commcarehq.org/display/commcarepublic/Setup+a+Form+with+Conditional+Select+Options
> And custom user data here:
> https://confluence.dimagi.com/display/commcarepublic/Custom+User+Data
>
> Cory
>
>
>
>
> On Thu, Feb 26, 2015 at 11:36 PM, Jessica Hall <jhal...@gmail.com > wrote:
>
>> Hi,
>>
>> I am just trying to figure out what the best approach is regarding my
>> look-up tables.
>> As part of the one project we have a cross-sectional study and a cohort
>> study.
>> Both studies are in a similar area however the cohort is going to be
>> visiting some villages that the cross-sectional doesn't .
>> Now we have almost finished data collection for the cross-sectional
>> baseline, and we now want to prepare the look-up table for the cohort.
>>
>> Is it easier to just use the existing look-up table from the
>> cross-sectional and add the additional villages to that table and just
>> filer by User/Group
>>
>> Or is it an option/better to add an additional separate look-up table for
>> the cohort?
>>
>> Can someone please advise which is the best approach.
>>
>> Many thanks,
>> Jess
>>
>> --
>> 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-user...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
To accomplish this you could have a Hidden Value in your form that takes
the value '1' when the form is filled out (its calculate condition is just
'1'). Then you'd save this value to the case in some property. You'd also
load this same property into the form into a second Hidden Variable, called
say "already_visited". You could then add the logic "not(already_visited =
1)" to the relevancy conditions of the questions you don't want to show up
in successive visits.
Hope this makes sense!
Best,
Will
···
On Sun, Mar 1, 2015 at 6:19 PM, Jessica Hall wrote:
Thanks Cory,
I will have a a look at the links you posted and get back to you if I have
any further questions regarding the look-up tables.
I do have another issue regarding case management though.
I want to be able to save the previous answer to a question from the last
time I visited the mother in one form so that the next time you visit and
use the same form certain questions don't appear. Can you please clarify
how to do this. Despite following the help site I keep having difficulties
with this.
Many thanks,
Jess
On Saturday, February 28, 2015 at 12:47:31 AM UTC+11, Cory Zue wrote:
Hey Jessica,
I don't have the exact details of how this would work in your app, but
one possibility would be to use the same lookup table but add a "study-arm"
property that is set to different values (cross-sectional/cohort), and then
filter the single lookup table in the app depending on the user's
information (you could either hard code this into the app if they are
different or use custom user data if they're the same).
On Thu, Feb 26, 2015 at 11:36 PM, Jessica Hall jhal...@gmail.com wrote:
Hi,
I am just trying to figure out what the best approach is regarding my
look-up tables.
As part of the one project we have a cross-sectional study and a cohort
study.
Both studies are in a similar area however the cohort is going to be
visiting some villages that the cross-sectional doesn't .
Now we have almost finished data collection for the cross-sectional
baseline, and we now want to prepare the look-up table for the cohort.
Is it easier to just use the existing look-up table from the
cross-sectional and add the additional villages to that table and just
filer by User/Group
Or is it an option/better to add an additional separate look-up table
for the cohort?
Can someone please advise which is the best approach.
Many thanks,
Jess
--
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-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.