ODK / SurveyCTO programmer needed

IPA is looking for a programmer to program a sanitation questionnaire using
ODK, possibly with the Survey CTO platform - a general description of the
survey is below. If interested, please respond to this post with: your
name, ODK/SurveyCTO programming experience, 2+ references, tariff
structure, availability, and an estimated timeline. Thanks in advance.

Sarah


Questionnaire

Our survey will be programmed in a local language with a few special
characters including "ñ", "ë", "é", "è", "à", etc. If it is relatively
easy to program the survey in a second language, we would request that it
also be programmed in French.

5 sections in 3 visits:

· Section 1-Intro (~120 variables) + Section 2-Demographic (~200
variables)

· Section 3-Decider (~300 variables) + Section 4-Intervention (~100
variables)

· Section 5-FinalReturn (~80 variables)

Pre-fill and automatic fill questions:

· Pre-fill: for Sections 1/2, prefill will come from a database we
created using data from our mapping phase; for Sections 3/4, prefill will
come from the mapping database, from Sections 1/2, and from a database that
assigns treatments to each household; for Section 5, prefill will come from
previous sections and mapping; for al

o Examples of pre-fill use: "What color is the wall of the house? 1.
blue, 2. yellow, 3. green", with control based on house color in mapping
database; "Was [firstname lastname] the person who was identified in the
pervious visit to be the responder?"

· Automatic fill: for Section 4, one of our treatments involves
sharing information with 5 respondents in the cluster about the responses
of their 5 neighbors in the cluster to the treatment, giving the respondent
either the names or the number of those who responded "yes" to our service
offer treatment; for the 5 who are assigned to this "name/number" treatment
group, we will need to have this variable in their survey populated by the
"yes to treatment" variable in the surveys of the 5 other neighbors

Rounds and respondents

Visits will be complete rounds of the entire sample - so we will first
administer Sections 1/2 to all households, and then Sections 3/4 to all
households, and finally Section 5; ideally, the time between rounds will be
minimized as much as possible

It is possible that there are different respondents for each visit, but all
respondents are from the same household, and so are associated with 1
unique ID of the household.

Timeline

We are hoping to have a functional survey and data flow solution to
benchtest within a month at most, as we plan to first pilot the entire
survey in 4 clusters. We consider that there could be two benchtest rounds
of a few days each, allowing for feedback from our testing team and then
the validation of a final version to launch in the field.

FYI, if anybody sees the "prefill will come from a database we created
using data from our mapping phase" and worries that this sort of thing is
impossible using ODK/XLSForm, the SurveyCTO platform will support this
functionality in an imminent release (it's in beta now). Basically, you
upload .csv files with your form definitions, and then you can easily pull
data from those .csv files as your forms are being filled out. If anybody
wants more information -- or to try the functionality -- please just
contact me.

Thanks,

Chris

P.S. ODK 2.0 has a rich feature-set for interacting with existing data.
This functionality in SurveyCTO is meant to support a common need in the
short-run: the ability to easily reference data from earlier mapping,
listing, or baseline surveys.

··· On Mon, May 6, 2013 at 11:34 AM, wrote:

IPA is looking for a programmer to program a sanitation questionnaire
using ODK, possibly with the Survey CTO platform - a general description of
the survey is below. If interested, please respond to this post with: your
name, ODK/SurveyCTO programming experience, 2+ references, tariff
structure, availability, and an estimated timeline. Thanks in advance.

Sarah


Questionnaire

Our survey will be programmed in a local language with a few special
characters including "ñ", "ë", "é", "è", "à", etc. If it is relatively
easy to program the survey in a second language, we would request that it
also be programmed in French.

5 sections in 3 visits:

· Section 1-Intro (~120 variables) + Section 2-Demographic (~200
variables)

· Section 3-Decider (~300 variables) + Section 4-Intervention
(~100 variables)

· Section 5-FinalReturn (~80 variables)

Pre-fill and automatic fill questions:

· Pre-fill: for Sections 1/2, prefill will come from a database
we created using data from our mapping phase; for Sections 3/4, prefill
will come from the mapping database, from Sections 1/2, and from a database
that assigns treatments to each household; for Section 5, prefill will come
from previous sections and mapping; for al

o Examples of pre-fill use: "What color is the wall of the house? 1.
blue, 2. yellow, 3. green", with control based on house color in mapping
database; "Was [firstname lastname] the person who was identified in the
pervious visit to be the responder?"

· Automatic fill: for Section 4, one of our treatments involves
sharing information with 5 respondents in the cluster about the responses
of their 5 neighbors in the cluster to the treatment, giving the respondent
either the names or the number of those who responded "yes" to our service
offer treatment; for the 5 who are assigned to this "name/number" treatment
group, we will need to have this variable in their survey populated by the
"yes to treatment" variable in the surveys of the 5 other neighbors

Rounds and respondents

Visits will be complete rounds of the entire sample - so we will first
administer Sections 1/2 to all households, and then Sections 3/4 to all
households, and finally Section 5; ideally, the time between rounds will be
minimized as much as possible

It is possible that there are different respondents for each visit, but
all respondents are from the same household, and so are associated with 1
unique ID of the household.

Timeline

We are hoping to have a functional survey and data flow solution to
benchtest within a month at most, as we plan to first pilot the entire
survey in 4 clusters. We consider that there could be two benchtest rounds
of a few days each, allowing for feedback from our testing team and then
the validation of a final version to launch in the field.

--

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/groups/opt_out.

FYI, we have publicly launched our new version of SurveyCTO at
www.surveycto.com, including this support for pre-loading data. If you sign
up to try it out, see the How do I pre-load data into my form? help topic
within the Managing Forms help section. Several samples are available
there.

Best,

Chris

··· On Mon, May 6, 2013 at 11:57 AM, Christopher Robert wrote:

FYI, if anybody sees the "prefill will come from a database we created
using data from our mapping phase" and worries that this sort of thing is
impossible using ODK/XLSForm, the SurveyCTO platform will support this
functionality in an imminent release (it's in beta now). Basically, you
upload .csv files with your form definitions, and then you can easily pull
data from those .csv files as your forms are being filled out. If anybody
wants more information -- or to try the functionality -- please just
contact me.

Thanks,

Chris

P.S. ODK 2.0 has a rich feature-set for interacting with existing data.
This functionality in SurveyCTO is meant to support a common need in the
short-run: the ability to easily reference data from earlier mapping,
listing, or baseline surveys.

On Mon, May 6, 2013 at 11:34 AM, snehrling@poverty-action.org wrote:

IPA is looking for a programmer to program a sanitation questionnaire
using ODK, possibly with the Survey CTO platform - a general description of
the survey is below. If interested, please respond to this post with: your
name, ODK/SurveyCTO programming experience, 2+ references, tariff
structure, availability, and an estimated timeline. Thanks in advance.

Sarah


Questionnaire

Our survey will be programmed in a local language with a few special
characters including "ñ", "ë", "é", "è", "à", etc. If it is relatively
easy to program the survey in a second language, we would request that it
also be programmed in French.

5 sections in 3 visits:

· Section 1-Intro (~120 variables) + Section 2-Demographic (~200
variables)

· Section 3-Decider (~300 variables) + Section 4-Intervention
(~100 variables)

· Section 5-FinalReturn (~80 variables)

Pre-fill and automatic fill questions:

· Pre-fill: for Sections 1/2, prefill will come from a database
we created using data from our mapping phase; for Sections 3/4, prefill
will come from the mapping database, from Sections 1/2, and from a database
that assigns treatments to each household; for Section 5, prefill will come
from previous sections and mapping; for al

o Examples of pre-fill use: "What color is the wall of the house? 1.
blue, 2. yellow, 3. green", with control based on house color in mapping
database; "Was [firstname lastname] the person who was identified in the
pervious visit to be the responder?"

· Automatic fill: for Section 4, one of our treatments involves
sharing information with 5 respondents in the cluster about the responses
of their 5 neighbors in the cluster to the treatment, giving the respondent
either the names or the number of those who responded "yes" to our service
offer treatment; for the 5 who are assigned to this "name/number" treatment
group, we will need to have this variable in their survey populated by the
"yes to treatment" variable in the surveys of the 5 other neighbors

Rounds and respondents

Visits will be complete rounds of the entire sample - so we will first
administer Sections 1/2 to all households, and then Sections 3/4 to all
households, and finally Section 5; ideally, the time between rounds will be
minimized as much as possible

It is possible that there are different respondents for each visit, but
all respondents are from the same household, and so are associated with 1
unique ID of the household.

Timeline

We are hoping to have a functional survey and data flow solution to
benchtest within a month at most, as we plan to first pilot the entire
survey in 4 clusters. We consider that there could be two benchtest rounds
of a few days each, allowing for feedback from our testing team and then
the validation of a final version to launch in the field.

--

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/groups/opt_out.