Dear Team,
we are looking for an optimal design strcuture to maintain references, even deletes or changes, between two parts of a survey, esp. household roster and individual questionnaire.
We would like to allow the user to first do the listing of household members and than to continue with individual questionnaires. But also allowing to go back and make corrections, like delete (not “usual” member) or correct age (>> no more old enough to be head or no more relevnt for the already entered labour questions)
There seem to be several design options:
-
2 different repeat groups (HH roster, Individual) , linked by foreign keys, like person index (and HH ID), showing name … to proof. (2nd repeat with count_repeat spec.)
begin_repeat roster
…
end_repeat
(…)
begin_repeat individual
…
end_repeat -
Only one repeat group and comprising inside the roster as 1st group and the individual questions as 2nd group, following each other.
begin_repeat
(…)
begin_ group roster
…
end_group
…)
begin_group individual
…
end_group
(…)
end_repeat -
Similar to 2), with one repeat, but wrapping the grouping inside, e.g: the whole repeat group is wrapped as group inside (or outside?), with roster and individual questions as sub-groups.
begin_repeat
begin_ group person
(…)
begin_group roster
…
end_group
(…)
begin_group individual
…
end_group
(…)
end_group
end_repeat -
Different forms, 1st for roster, 2nd for Individual, (3rd for household questions)
-
Other solutions?
What do you RECOMMEND? (And why?)
Can you provide an advanced example?
We would prefer option 1). We think, it’s cleaer for user/questionnaire navigation. But encountered some problems for maintaining the referencing of records and values…
And how should we best wrapp with groups here, e.g.
- the whole items inside the repeat?
- even an additional group directly wrapping the repeat outside?
- just several groups inside the repeat?
- just single questions inside the repeat (no groups at all).
We know about the general advantage of grouping, and we scanned through a lot of community posting. The question here is more on your expert advice for overall structuring, i.e. a well working design and flexible/easy user navigation.
Thanks in advance!
Kind regards
