As I said, SurveyCTO doesn't have any features for fieldwork management.
But by pre-loading data and programming logic into your survey form, you
can do some things to support your own fieldwork management.
For example, your enumerators might start each form by entering and/or
scanning their enumerator ID (from a barcode). When it comes time to
identify the respondent, you can offer a multiple-choice list that only
shows those respondents assigned to that enumerator. If the list is too
long (150 is too long), you could start by asking about the region, then
the district, then the village, then only show their respondents in the
selected village -- or however it is most natural to narrow down that list.
It would be slightly radical, but in the pre-loaded data you could even
specify a device ID for each respondent, and then the form could
automatically filter the list of possible respondents by that device ID.
Thus, each device would show a different list. This would uniquely assign
respondents to devices, but it probably wouldn't be a great system because
of its lack of flexibility; it would be hard to re-assign respondents, for
example, if a device failed or an enumerator took the day off.
In general, fieldwork management is a complex thing. It's essentially
outside the scope of what ODK (and most ODK variations) try to directly
facilitate. But you can definitely conduct a survey of 15,000 households.
You just need to work out your own field-management practices.
As for a white-label server, we haven't offered such an option to-date. We
would consider it for the right price, but it would be expensive. If you
want to discuss it, you can email me offline.
As for other languages, the only product localized to many other languages
is Collect -- which is the only product used by field supervisors,
enumerators, etc. (You simply change the language in Android's settings.)
For the moment, the SurveyCTO Server and Client are in English only, but
then a much smaller range of people use those interfaces. We are also open
to localizing those, also for the right price.
On Tue, Oct 22, 2013 at 3:09 AM, Fandy Santoso wrote:
Thanks for your response.
Several quick questions about SurveyCTO:
- Even by using Excel and mail merge function of Word, how do we appoint
specific respondent (pre-loaded form) to each enumerator? Does SurveyCTO
support credential login process into SurveyCTO Collect? Otherwise when we
are downloading the survey from the server, the system cannot determine
which enumerator is downloading which survey right?
- Since we are performing the survey for our client, is it possible if we
can do white labeling and host SurveyCTO in our own server?
- Lastly, is it possible for us to modify the language used in the
SurveyCTO Server, Collect and Client? I understand that we can use
different languages in the XML (forms), but I also need to localize the
other products as such my local enumerator and system administrator can use
the system to its fullest capability.
Greatly appreciate your help and many thanks!
On Tuesday, October 22, 2013 7:47:37 AM UTC+7, Christopher Robert wrote:
SurveyCTO (www.SurveyCTO.com) supports pre-loading data.
However, it has no built-in support for enumerator management. For
assigning specific surveys to specific enumerators, we generally use a
combination of Excel and mail merge in Word. And, much in the way of
balancing work-loads in the field ends up being handled by field
supervisors. So one approach, for example, is to assign surveys to teams by
geography, then let teams sort out who does which interviews. There's
obviously a lot to field management, though, so I'm dramatically
On Oct 21, 2013 2:16 PM, fandy.s...@gmail.com wrote:
I have a project whereby I need to survey 15,000 respondents (predefined
list of household in a city) and have 100 enumerators to perform such
Anyone here have any idea on:
- How we can preload the survey with the basic information of each
respondent (name, address, phone number), and
- Assign certain numbers of respondent to each enumerator?
For example: as I have 15,000 respondents and 100 enumerator, then I
would fairly split the load to 150 respondents for each enumerator.
Many thanks for all the kind help.
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...@**googlegroups.com.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.