How big is too big with forms?

I am planning to capture data in the field with ODK Collect. Our project
has a form that is about 100 questions long. There won't be any media, just
text and number fields.

My questions are:

Is a form with 100 questions too big? If so, what is a good form design
protocol?

How will a form with 100 columns affect our quotas on Google App Engine
(for ODK Aggregate)?

Thanks!

Shouldn't be a problem. I've come across forms with 1000's of questions.

Large forms may raise data-collection-usability issues:

i.e., Are your respondents going to happily sit through such a long
interview?

App Engine costs are always proportional to datastore reads.

See the 2nd paragraph here:

Approximately 200 text answers (NOT select-one or select-multiple) -- each
255 characters long -- fit in one database table row (costing one read).
If you need to store text answers that exceed 255 characters, see

The longer the field size, the fewer fields.

··· On Thu, May 19, 2016 at 11:09 AM, Jefferson Francisco < jeffersont.francisco@gmail.com> wrote:

I am planning to capture data in the field with ODK Collect. Our project
has a form that is about 100 questions long. There won't be any media, just
text and number fields.

My questions are:

Is a form with 100 questions too big? If so, what is a good form design
protocol?

How will a form with 100 columns affect our quotas on Google App Engine
(for ODK Aggregate)?

Thanks!

--

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/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

I can confirm what Mitch said. Forms with 100 questions are not big. We
used to handle forms with 3,300 questions.

··· On Friday, May 20, 2016 at 1:44:12 AM UTC+7, Mitch Sundt wrote: > > Shouldn't be a problem. I've come across forms with 1000's of questions. > > Large forms may raise data-collection-usability issues: > > i.e., Are your respondents going to happily sit through such a long > interview? > > App Engine costs are always proportional to datastore reads. > > See the 2nd paragraph here: > https://opendatakit.org/use/aggregate/deployment-planning/#App_Engine_Usage_Fees > > Approximately 200 text answers (NOT select-one or select-multiple) -- each > 255 characters long -- fit in one database table row (costing one read). > If you need to store text answers that exceed 255 characters, see > https://opendatakit.org/help/form-design/guidelines/#datastore_string_length > The longer the field size, the fewer fields. > > > On Thu, May 19, 2016 at 11:09 AM, Jefferson Francisco < jeffersont...@gmail.com > wrote: > >> I am planning to capture data in the field with ODK Collect. Our project >> has a form that is about 100 questions long. There won't be any media, just >> text and number fields. >> >> My questions are: >> >> Is a form with 100 questions too big? If so, what is a good form design >> protocol? >> >> How will a form with 100 columns affect our quotas on Google App Engine >> (for ODK Aggregate)? >> >> Thanks! >> >> -- >> -- >> Post: opend...@googlegroups.com >> Unsubscribe: opendatakit...@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...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com >