ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page

ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page
http://code.google.com/p/opendatakit/downloads/list

NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g., Droids),
the heavy use of javascript and CSS styles causes page transitions to be
slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and the
next page rendering). It is much faster on newer tablets and 4.x devices.

Alpha releases should never be used for production deployments.

While in alpha, every software update may result in loss of data or
incompatible changes in form designs.

Alpha releases are provided to gather user feedback and bug reports.

Please see http://code.google.com/p/opendatakit/wiki/SurveyReleaseNotes for
usage information.

Please open an issue here:
http://code.google.com/p/opendatakit/issues/list to make feature requests,
report any crashes, or describe any odd behaviors.

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

Thanks a lot Mitch and the team. We are grateful to your efforts.
I will test the software and provide feedback.

Best,
Trung.

··· On Friday, January 11, 2013 1:19:54 AM UTC+7, Mitch wrote: > > *ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page* > http://code.google.com/p/opendatakit/downloads/list > > NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g., Droids), > the heavy use of javascript and CSS styles causes page transitions to be > slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and the > next page rendering). It is much faster on newer tablets and 4.x devices. > > Alpha releases should never be used for production deployments. > > *While in alpha, every software update may result in loss of data or > incompatible changes in form designs.* > > Alpha releases are provided to gather *user feedback* and *bug reports*. > > Please see http://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information. > > *Please open an issue here:* > http://code.google.com/p/opendatakit/issues/list to make feature > requests, report any crashes, or describe any odd behaviors. > > -- > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com

Hello,

I've read:

NOTE: The converter script produces an XForms definition file (.xml)
that is unusable by ODK Collect 1.x. It only contains enough information
to support publishing of data into ODK Aggregate

So, should I create two engines, one for Collect forms(1.x) and a new
one for Survey forms(2.x), or should I have a duplicate list of forms,
one for each version? (in case I want hold the old forms for odk users)?

Thank you.

Al 10/01/2013 19:19, En/na Mitch S ha escrit:

··· > *ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page* > http://code.google.com/p/opendatakit/downloads/list > > NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g., > Droids), the heavy use of javascript and CSS styles causes page > transitions to be slower than in ODK Collect 1.x (about 1-2 seconds > between a swipe and the next page rendering). It is much faster on > newer tablets and 4.x devices. > > Alpha releases should never be used for production deployments. > > *While in alpha, every software update may result in loss of data or > incompatible changes in form designs.* > > Alpha releases are provided to gather *user feedback* and *bug reports*. > > Please see > http://code.google.com/p/opendatakit/wiki/SurveyReleaseNotes for usage > information. > > _Please open an issue here:_ > http://code.google.com/p/opendatakit/issues/list to make feature > requests, report any crashes, or describe any odd behaviors. > > -- > Mitch Sundt > Software Engineer > University of Washington > mitchellsundt@gmail.com -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en

Mitch (or anyone else who knows the answer),

Are there plans to maintain and continue development on the old Java
version of ODKCollect?

Thanks,

Karri

··· On Thursday, January 10, 2013 11:19:54 AM UTC-7, Mitch wrote:

ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page
http://code.google.com/p/opendatakit/downloads/list

NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g., Droids),
the heavy use of javascript and CSS styles causes page transitions to be
slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and the
next page rendering). It is much faster on newer tablets and 4.x devices.

Alpha releases should never be used for production deployments.

While in alpha, every software update may result in loss of data or
incompatible changes in form designs.

Alpha releases are provided to gather user feedback and bug reports.

Please see http://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information.

Please open an issue here:
http://code.google.com/p/opendatakit/issues/list to make feature
requests, report any crashes, or describe any odd behaviors.

--
Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com <javascript:>

Great stuff here and looking forward to further development here. A couple
of observation when testing.

  1. Swipe between screens/questions is not available/working, Not a
    huge problem, but many users were getting used to this and could use it
    very fast (ie to get to a specific question)
  2. One open a template, great to get the previous forms, could an extra
    button be added which was to copy/clone a form, this could be soo useful
    when surveys are entering simlar data in one site etc.
  3. Can you customize the form name from the actual form ie (use an ID
    entered by user).
  4. Finally am I sending this to the right place.

Thanks for all the hard work, looking good.

GISTIN

··· On Thursday, January 10, 2013 6:19:54 PM UTC, Mitch wrote: > > *ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page* > http://code.google.com/p/opendatakit/downloads/list > > NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g., Droids), > the heavy use of javascript and CSS styles causes page transitions to be > slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and the > next page rendering). It is much faster on newer tablets and 4.x devices. > > Alpha releases should never be used for production deployments. > > *While in alpha, every software update may result in loss of data or > incompatible changes in form designs.* > > Alpha releases are provided to gather *user feedback* and *bug reports*. > > Please see http://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information. > > *Please open an issue here:* > http://code.google.com/p/opendatakit/issues/list to make feature > requests, report any crashes, or describe any odd behaviors. > > -- > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com

w.r.t. running ODK Survey 2.0 and ODK Collect 1.x surveys off of the same
ODK Aggregate instance, you can certainly do that. The only ODK Survey
requirement is that the 'Default form' to have a form_id = 'default'

When running on one shared ODK Aggregate, it becomes a training and/or
naming question to let users know which forms are intended for ODK Survey.
If users download and attempt to run the ODK Survey
converter-script-generated forms from ODK Collect 1.x, running the survey
will not do any damage but may Force Close on audio/video/image capture
prompts (haven't checked, but it may trigger null pointer exceptions
because there are no question labels).

While it is possible to construct an ODK Survey 2.0 form definition that
can be uploaded into an existing XForms-defined form (including encrypted
forms -- view the .hta file so see the various xml-specific settings
options), the primary intent of the backward-compatibility conversion
script is to enable people to try out and use ODK Survey 2.0 now, while we
turn our development focus onto:
(1) ODK Tables and the new ODK Aggregate storage functionality for
bi-directional data updates,
(2) extending the ODK Survey javascript to support chained/joined forms
(the replacement for repeat groups).

Mitch

··· On Fri, Jan 11, 2013 at 1:54 AM, Trung Dang Le wrote:

Thanks a lot Mitch and the team. We are grateful to your efforts.
I will test the software and provide feedback.

Best,
Trung.

On Friday, January 11, 2013 1:19:54 AM UTC+7, Mitch wrote:

ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page
http://code.google.com/p/**opendatakit/downloads/listhttp://code.google.com/p/opendatakit/downloads/list

NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g.,
Droids), the heavy use of javascript and CSS styles causes page transitions
to be slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and
the next page rendering). It is much faster on newer tablets and 4.x devices
.

Alpha releases should never be used for production deployments.

While in alpha, every software update may result in loss of data or
incompatible changes in form designs.

Alpha releases are provided to gather user feedback and bug reports.

Please see http://code.google.com/p/**opendatakit/wiki/**
SurveyReleaseNoteshttp://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information.

Please open an issue here: http://code.google.com/p/**
opendatakit/issues/listhttp://code.google.com/p/opendatakit/issues/listto make feature requests, report any crashes, or describe any odd behaviors.

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

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

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

Mitch and Team,

Congrats to you and the team! This is wonderful news. For those who
haven't seen an early preview yet, there is a lot to be excited about with
this new release!

Matt

··· On Fri, Jan 11, 2013 at 11:33 AM, francesc wrote:

Hello,

I've read:

NOTE: The converter script produces an XForms definition file (.xml) that
is unusable by ODK Collect 1.x. It only contains enough information to
support publishing of data into ODK Aggregate

So, should I create two engines, one for Collect forms(1.x) and a new one
for Survey forms(2.x), or should I have a duplicate list of forms, one for
each version? (in case I want hold the old forms for odk users)?

Thank you.

Al 10/01/2013 19:19, En/na Mitch S ha escrit:

ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page
http://code.google.com/p/opendatakit/downloads/list

NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g., Droids),
the heavy use of javascript and CSS styles causes page transitions to be
slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and the
next page rendering). It is much faster on newer tablets and 4.x devices.

Alpha releases should never be used for production deployments.

While in alpha, every software update may result in loss of data or
incompatible changes in form designs.

Alpha releases are provided to gather user feedback and bug reports.

Please see http://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information.

Please open an issue here:
http://code.google.com/p/opendatakit/issues/list to make feature
requests, report any crashes, or describe any odd behaviors.

Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com --
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

We introduced the new name, ODK Survey, to convey that this is a separate
app, and would not stop development on ODK Collect 1.x.

That said,

(1) ODK Collect will increasingly become a community-supported software
development project -- primarily expanded through code contributions from
the community. We do not intend to change it in any fundamental way; we
expect to periodically update it with the latest jars, user-contributed UI
widgets, and perform bug fixes as needed.

(2) ODK Survey and ODK Tables will increasingly become the focus of the
core team's efforts. Quite simply, the ability for anyone to write or
incorporate Javascript libraries or CSS files to customize the appearances
of their forms is very compelling.

The ODK Collect and ODK Survey and ODK Tables apps will each have
mechanisms to communicate with ODK Aggregate and tie-ins with other tools
(ODK Briefcase, ODK FormUploader, and Build or XLSForm). While ODK Survey
will have a backward-compatible form submission process (like in the
Alpha), there will be a new bi-directional synchronization mechanism as
well, which will not look anything like the backward-compatible mechanisms.

··· -------- Mitch

On Thu, Jan 31, 2013 at 11:20 AM, Karri Fox karri.r.fox@gmail.com wrote:

Mitch (or anyone else who knows the answer),

Are there plans to maintain and continue development on the old Java
version of ODKCollect?

Thanks,

Karri

On Thursday, January 10, 2013 11:19:54 AM UTC-7, Mitch wrote:

ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page
http://code.google.com/p/**opendatakit/downloads/listhttp://code.google.com/p/opendatakit/downloads/list

NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g.,
Droids), the heavy use of javascript and CSS styles causes page transitions
to be slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and
the next page rendering). It is much faster on newer tablets and 4.x devices
.

Alpha releases should never be used for production deployments.

While in alpha, every software update may result in loss of data or
incompatible changes in form designs.

Alpha releases are provided to gather user feedback and bug reports.

Please see http://code.google.com/p/**opendatakit/wiki/**
SurveyReleaseNoteshttp://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information.

Please open an issue here: http://code.google.com/p/**
opendatakit/issues/listhttp://code.google.com/p/opendatakit/issues/listto make feature requests, report any crashes, or describe any odd behaviors.

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

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

Thanks.

(1) is a known issue -- particularly on a 4.0 phone, swiping is broken. On
other phones, swiping is slow.

I created a feature request issue for 2 & 3 --
http://code.google.com/p/opendatakit/issues/detail?id=775

If you have other thoughts about what should be in ODK Survey, please
create issues (with 'Survey feature request' plus a short description in
the title) for them here: http://code.google.com/p/opendatakit/issues/list

Mitch

··· On Thu, Feb 28, 2013 at 4:20 AM, gistin wrote:

Great stuff here and looking forward to further development here. A couple
of observation when testing.

  1. Swipe between screens/questions is not available/working, Not a
    huge problem, but many users were getting used to this and could use it
    very fast (ie to get to a specific question)
  2. One open a template, great to get the previous forms, could an extra
    button be added which was to copy/clone a form, this could be soo useful
    when surveys are entering simlar data in one site etc.
  3. Can you customize the form name from the actual form ie (use an ID
    entered by user).
  4. Finally am I sending this to the right place.

Thanks for all the hard work, looking good.

GISTIN

On Thursday, January 10, 2013 6:19:54 PM UTC, Mitch wrote:

ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page
http://code.google.com/p/**opendatakit/downloads/listhttp://code.google.com/p/opendatakit/downloads/list

NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g.,
Droids), the heavy use of javascript and CSS styles causes page transitions
to be slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and
the next page rendering). It is much faster on newer tablets and 4.x devices
.

Alpha releases should never be used for production deployments.

While in alpha, every software update may result in loss of data or
incompatible changes in form designs.

Alpha releases are provided to gather user feedback and bug reports.

Please see http://code.google.com/p/**opendatakit/wiki/**
SurveyReleaseNoteshttp://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information.

Please open an issue here: http://code.google.com/p/**
opendatakit/issues/listhttp://code.google.com/p/opendatakit/issues/listto make feature requests, report any crashes, or describe any odd behaviors.

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

--

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.

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

Great stuff. Hoping to get this on my tablet and see how it stands up....

··· On Thu, Feb 28, 2013 at 8:20 AM, gistin wrote:

Great stuff here and looking forward to further development here. A couple
of observation when testing.

  1. Swipe between screens/questions is not available/working, Not a
    huge problem, but many users were getting used to this and could use it
    very fast (ie to get to a specific question)
  2. One open a template, great to get the previous forms, could an extra
    button be added which was to copy/clone a form, this could be soo useful
    when surveys are entering simlar data in one site etc.
  3. Can you customize the form name from the actual form ie (use an ID
    entered by user).
  4. Finally am I sending this to the right place.

Thanks for all the hard work, looking good.

GISTIN

On Thursday, January 10, 2013 6:19:54 PM UTC, Mitch wrote:

ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page
http://code.google.com/p/**opendatakit/downloads/listhttp://code.google.com/p/opendatakit/downloads/list

NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g.,
Droids), the heavy use of javascript and CSS styles causes page transitions
to be slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and
the next page rendering). It is much faster on newer tablets and 4.x devices
.

Alpha releases should never be used for production deployments.

While in alpha, every software update may result in loss of data or
incompatible changes in form designs.

Alpha releases are provided to gather user feedback and bug reports.

Please see http://code.google.com/p/**opendatakit/wiki/**
SurveyReleaseNoteshttp://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information.

Please open an issue here: http://code.google.com/p/**
opendatakit/issues/listhttp://code.google.com/p/opendatakit/issues/listto make feature requests, report any crashes, or describe any odd behaviors.

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

--

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.

--


"Like a camera I use the negative to develop..uDig"
"Success is the ability to go from one failure to another with no loss of
enthusiasm"
---------------------------------------------------------------------------------------------------------->
Roxroy K. Bollers
OutSourceRox*
*Geographic Information Systems, IT Professional & Wed Developer
tel. 592.685.2737
.........................................................
Follow Us On
Facebook http://www.facebook.com/OutSourceRox
Google+ https://plus.google.com/114064153117817313312
Web http://twitinternational.com/outsourcerox.htm
Twitter: @drbollers http://www.twitter.com/drbollers

Portfolio:
Tropical Timber http://www.tropicaltimber.com
Adventure Guianas http://www.adventureguianas.com/
Surama Eco-Lodge http://www.suramaecolodge.com/
Forest Connect Guyana http://iwokrama.org/forestconnect/index.htm

Is the code for version 2 available publicly?

··· On 11 January 2013 13:33, Mitch S wrote:

w.r.t. running ODK Survey 2.0 and ODK Collect 1.x surveys off of the same
ODK Aggregate instance, you can certainly do that. The only ODK Survey
requirement is that the 'Default form' to have a form_id = 'default'

When running on one shared ODK Aggregate, it becomes a training and/or
naming question to let users know which forms are intended for ODK Survey.
If users download and attempt to run the ODK Survey
converter-script-generated forms from ODK Collect 1.x, running the survey
will not do any damage but may Force Close on audio/video/image capture
prompts (haven't checked, but it may trigger null pointer exceptions
because there are no question labels).

While it is possible to construct an ODK Survey 2.0 form definition that
can be uploaded into an existing XForms-defined form (including encrypted
forms -- view the .hta file so see the various xml-specific settings
options), the primary intent of the backward-compatibility conversion
script is to enable people to try out and use ODK Survey 2.0 now, while we
turn our development focus onto:
(1) ODK Tables and the new ODK Aggregate storage functionality for
bi-directional data updates,
(2) extending the ODK Survey javascript to support chained/joined forms
(the replacement for repeat groups).

Mitch

On Fri, Jan 11, 2013 at 1:54 AM, Trung Dang Le trungdangle@gmail.comwrote:

Thanks a lot Mitch and the team. We are grateful to your efforts.
I will test the software and provide feedback.

Best,
Trung.

On Friday, January 11, 2013 1:19:54 AM UTC+7, Mitch wrote:

ODK Survey 2.0 ALPHA rev 102 is now available on the downloads page
http://code.google.com/p/**opendatakit/downloads/listhttp://code.google.com/p/opendatakit/downloads/list

NOTE: while ODK Survey will operate on slower 2.2.3 phones (e.g.,
Droids), the heavy use of javascript and CSS styles causes page transitions
to be slower than in ODK Collect 1.x (about 1-2 seconds between a swipe and
the next page rendering). It is much faster on newer tablets and 4.x devices
.

Alpha releases should never be used for production deployments.

While in alpha, every software update may result in loss of data or
incompatible changes in form designs.

Alpha releases are provided to gather user feedback and bug reports.

Please see http://code.google.com/p/**opendatakit/wiki/**
SurveyReleaseNoteshttp://code.google.com/p/opendatakit/wiki/SurveyReleaseNotesfor usage information.

Please open an issue here: http://code.google.com/p/**
opendatakit/issues/listhttp://code.google.com/p/opendatakit/issues/listto make feature requests, report any crashes, or describe any odd behaviors.

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

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

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

Thank you Mitch for your extended answer. I'll test this Survey beta
a.s.a.p.

Al 11/01/2013 19:33, En/na Mitch S ha escrit:

··· > w.r.t. running ODK Survey 2.0 and ODK Collect 1.x surveys off of the > same ODK Aggregate instance, you can certainly do that. The only ODK > Survey requirement is that the 'Default form' to have a form_id = > 'default' > > When running on one shared ODK Aggregate, it becomes a training and/or > naming question to let users know which forms are intended for ODK > Survey. If users download and attempt to run the ODK Survey > converter-script-generated forms from ODK Collect 1.x, running the > survey will not do any damage but may Force Close on audio/video/image > capture prompts (haven't checked, but it may trigger null pointer > exceptions because there are no question labels). > > While it is possible to construct an ODK Survey 2.0 form definition > that can be uploaded into an existing XForms-defined form (including > encrypted forms -- view the .hta file so see the various xml-specific > settings options), the primary intent of the backward-compatibility > conversion script is to enable people to try out and use ODK Survey > 2.0 now, while we turn our development focus onto: > (1) ODK Tables and the new ODK Aggregate storage functionality for > bi-directional data updates, > (2) extending the ODK Survey javascript to support chained/joined > forms (the replacement for repeat groups). > > Mitch >

"While ODK Survey will have a backward-compatible form submission process
(like in the Alpha), there will be a new bi-directional synchronization
mechanism as well, which will not look anything like the
backward-compatible mechanisms."

Mitch, can you explain further how this bi-directional synchronization will
be?
One of my interest for Survey would be in case of for example medical
records, if a person goes to Doctor A, when they go a next time to Doctor B
at another location, Doctor B should be able to log in and download that
record. Would something like this be possible?

Nelson

Please keep in mind that ODK Survey is in Alpha; as such, it will be
treated as an unsupported ODK project.
We may radically change the code at any time.

The Javascript source is here:
http://code.google.com/p/opendatakit/source/browse?repo=collect2

The Java source is here:
http://code.google.com/p/opendatakit/source/browse?repo=survey

We expect significant changes in the Javascript to support linked/chained
forms.
We expect significant additions to the Java code for ODK Tables integration.

Mitch

··· On Fri, Jan 11, 2013 at 11:08 AM, francesc wrote:

Thank you Mitch for your extended answer. I'll test this Survey beta
a.s.a.p.

Al 11/01/2013 19:33, En/na Mitch S ha escrit:

w.r.t. running ODK Survey 2.0 and ODK Collect 1.x surveys off of the same

ODK Aggregate instance, you can certainly do that. The only ODK Survey
requirement is that the 'Default form' to have a form_id = 'default'

When running on one shared ODK Aggregate, it becomes a training and/or
naming question to let users know which forms are intended for ODK Survey.
If users download and attempt to run the ODK Survey
converter-script-generated forms from ODK Collect 1.x, running the survey
will not do any damage but may Force Close on audio/video/image capture
prompts (haven't checked, but it may trigger null pointer exceptions
because there are no question labels).

While it is possible to construct an ODK Survey 2.0 form definition that
can be uploaded into an existing XForms-defined form (including encrypted
forms -- view the .hta file so see the various xml-specific settings
options), the primary intent of the backward-compatibility conversion
script is to enable people to try out and use ODK Survey 2.0 now, while we
turn our development focus onto:
(1) ODK Tables and the new ODK Aggregate storage functionality for
bi-directional data updates,
(2) extending the ODK Survey javascript to support chained/joined forms
(the replacement for repeat groups).

Mitch

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@**googlegroups.comopendatakit%2Bunsubscribe@googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en

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

Yes. Initially, however, we expect to synchronize and download data in bulk.

It is entirely unclear how to manage which devices are allowed to get which
records, and how to get those records to the eligible devices -- whether it
be a batch download of everything (so you don't need to have wireless
connectivity during the day), or a pull model as you describe, where the
phone user (doctor) has access to everything, but downloads only what they
need when they need it.

Since ODK is intended for unconnected operations, the first (alpha)
iteration will be the download everything at the start of the day (or
whenever), and then upload changes in bulk at the end of the interval.

Mitch

··· On Fri, Feb 1, 2013 at 7:13 AM, Nelson Mambre wrote:

"While ODK Survey will have a backward-compatible form submission process
(like in the Alpha), there will be a new bi-directional synchronization
mechanism as well, which will not look anything like the
backward-compatible mechanisms."

Mitch, can you explain further how this bi-directional synchronization
will be?
One of my interest for Survey would be in case of for example medical
records, if a person goes to Doctor A, when they go a next time to Doctor B
at another location, Doctor B should be able to log in and download that
record. Would something like this be possible?

Nelson

--

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.

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

ODeeKers,

This is a very Exciting update and I'm happy to see it. I had some notes on
testing that I thought would be constructive to share with the list, and
some questions as well. If anyone wants to move this to an "Alpha Testing"
thread, that's fine.

I uninstalled all previous versions of ODK, KoBo, etc. before testing to
avoid any mishaps. FYI, testing on a Google Nexus 4.

My first attempt to connect to the Aggregate server resulted in an error
downloading the forms. This was quickly rectified as my second attempt did
connect and downloaded the default testing forms. I include the error here
for posterity:
[image: Inline image 1]

After Toggle All and Get Selected, download of 5 forms:

  1. Custom Appearance Form
  2. Example FOrm
  3. Refrigerator information update form
  4. Initial Refrigerator information
  5. Default form

Their is a great opening splash screen for a new form that includes the
option to "create a new instance" and a list of previous instances. You can
edit or delete a previous instance. Question: can you limit access to edit
and delete here? We wouldn't want enumerators to do any deleting, even of
test instances and errors.
[image: Inline image 5]

The Custom Appearance form generated an error when I hit the back button:
[image: Inline image 2]

The first question screen asks for your name and a multiple select question
for continents you have visited. I entered my name, and checked the
continents, but my name kept disappearing from the text entry box. I found
that if I answered the continents, moved to the next screen, then went
back, i was able to fill in my name and move forward.
[image: Inline image 4]

Loading this same form on my older phone, a MyTouch running Android 2.2.1
worked, but it was way slow. It took about 30 seconds to load the Custom
Appearance form, The screen to screen transition is pretty slow, too. There
is a lag when making selections and typing. I would say that on the older
devices, it would be impractical to run ODK Survey. On my nexus 4,there is
no lag at all. Screen to screen transitions are quick. In using the Range
Slider, i do see a little bit of lag.

I was able to complete a Custom Appearance Form, when I tried to load the
"Default Form" I got a crash. I wasn't running logcat at the time, so I
don't have any triage for you, sorry. I started logcat but I didn't get the
error the next time I loaded it.
So, I see Default form isn't really a form at all, there are no questions
in it. This contains support for the other forms, is that right?
There is just a note about setting the form path.
[image: Inline image 6]
I assume this means that the default form path is */formlist *and this is
a reference to the location of blank forms on the appengine server? Is that
right? This can be changed to any other folder on the server?

There are not options that can be set in Default Form, it's in the
settings: Am I doing anything with this Default Form? Is it verbotten to
open it? I know it must be present to make the other forms work.
[image: Inline image 7]

Just looking into the other settings, I see if you Select Survey>>Hierarchy
you get a blank page. If you click Next, you get an error. Hierarchy
appears to be the list of available questions in a regular form, like
Example Form.
[image: Inline image 9] [image: Inline image 8]

In The Example form, when you load Hierarchy, it works fine. You can see
all the questions and select one.
If you try and select Language, you get an odd image. I don't see how you
could choose a language here:
[image: Inline image 10]

The question "Trigger an error on the next screen?" if selected "Yes" does
just that, but when you see the message and select OK to continue, you get
an actual error "Fatal Error "Example Form." See console log.

Generally speaking, there are some errors that pop up in navigation when
you do stupid/creative/curious things like hitting the back button. If you
just keep on the straight and narrow path, we're doing allright. Hey,
that's why it's an Alpha release.

The example form questions illustrate question types, most of which are
familiar from ODK Collect. The addition of HTML in Labels and Hints is
great, we have long wanted to control the appearance of these.

Handlesbars templates allow labels to change depending on values previously
entered. This is Great! You can re-use answers from earlier questions. Just
to be a pain, I am going to ask the "does it grant wishes?" question: Can
you pull answers from OTHER surveys where you have already collected data?
Perhaps this is answered by the presence of the Regrigerator and
Refrigerator Update forms. However, When I have created a, Initial
Refrigerator instance, I don't see how I can select it in the Refrigerator
Update form. I don't see any connection between these forms. Am I missing
something.

What is the purpose of the link to another prompt? Can you give an example
of use?

The D3.js chart allows plotting of answers. This is a super cool feature.
Can you provide any more information on the use of this feature?

So, now that I have created some surveys, I want to sync them to the
server. I don't see where "Send to Server" is. Is the sync happening
automatically in the background? Is there a confirm? Can I trigger the sync
manually?

Where are forms and instances stored on the SDcard? I don't see them in the
odk/forms and odk/instances folders.

Yeesh, that's enough questions from me, again, very impressed and delighted
at the new functions and features.

☞§※☼:airplane::open_umbrella::slight_smile:
~Neil

I'm also interested in this aspect of bi-directional synchronization, and
especially in the case we want some kind of encryption. How can these 2
users share the symmetric key? the actual solution of the Encrypted Forms
seems difficult in this scenario, because there can be many users
interested in the same form data, and maybe we cannot know them in advance,
before encrypting the form.

And also, will there be differences in ODK Aggregate, depending on the new
ideas on ODK 2.0?
thanks in advance,

Daniele

··· Il giorno venerdì 1 febbraio 2013 16:13:11 UTC+1, Nelson Mambre ha scritto: > > "While ODK Survey will have a backward-compatible form submission process > (like in the Alpha), there will be a new bi-directional synchronization > mechanism as well, which will not look anything like the > backward-compatible mechanisms." > > Mitch, can you explain further how this bi-directional synchronization > will be? > One of my interest for Survey would be in case of for example medical > records, if a person goes to Doctor A, when they go a next time to Doctor B > at another location, Doctor B should be able to log in and download that > record. Would something like this be possible? > > Nelson > > >

Hi Neil, Thanks for the fantastic feedback!
I'll try to respond to a few of the items you bring up:

Question: Can you limit access to edit and delete in the instance list?

Yes, it is be possible to override the default instances list screen with
anything you want. I may be doing this for one of the deployments we're
planning and I'll plan to make the form (or at least the relevant parts)
available as an example.

The disappearing name bug is related to screens dynamically updating so
prompts can disappear/reappear/change based on the other values on the
screen. There are some technical issues we still have to work out there.

The default form contains all the core javascript. I think we're going to
be reorganizing the code to get rid of it.

W.r.t. pulling answers from other forms/data sources an inserting them in
labels, it is possible to do it with a custom templates/prompt. However, I
think we might add some features to make it easier.
One approach I like for that would be to us the queries
sheethttp://code.google.com/p/opendatakit/wiki/XLSForm2Docs#queriesto
identify the data source, and then add handlebars helper like this to
use queries in labels:
{{#withQuery query_name}} {{queryData}} {{/withQuery}}
What do you think?

Prompt links would probably be most useful in a job-aid scenario. They
would be good for allowing someone to choose between different sections of
a form based on the task they want to do. They would also be useful for
adding "more info" screens that give detailed explanations of questions.
For example, if there were a question like "Does the patient have stridor?"
one could add a link to a long explanation and video about how to assess
stridor.

The d3 prompt was done by creating a custom
templatehttp://code.google.com/p/opendatakit/wiki/XLSForm2Docs#templatePath.
You can see the template
herehttp://code.google.com/p/opendatakit/source/browse/form-files/example/ageWeightPlot.handlebars?repo=collect2
.

Forms are stored in the sdcard/odk/js/forms directory.

Added to my todo list:
disable back button on first question.
disable the language menu when there are no translations to choose from

Regards,
-Nathan

The "Send to Server" is a menu item available once you are viewing a
particular form (and you only see the unsent records that are accessed by
that particular form).

We're still figuring out the new 'Action Bar' look (the tab-like header at
the top of the screen). The 'Send to Server' menu item should appear as an
up arrow on the action bar once you've selected a form, but there seems to
be some odd issues with width-determination, so it never gets shown and is
instead visible only via the menu. Similarly, the 'Download Forms' menu
item should appear as a down arrow on the action bar when a form has not
been selected.

All forms and data are stored under /odk/js The filled-in form values are
all stored in the (one) SQLite database (not in flat xml files). When you
attempt to send the data to the server, a content provider is used to
retrieve the XML serialization of the SQLite data. If you are working with
an encrypted form, this serialization undergoes one-way encryption prior to
transmission (but the SQLite data on the device remains until you delete it
manually and that data is unencrypted). Any media attachments are also
preserved in unencrypted form until you delete them; one-way encryption is
performed prior to submitting them together with an encrypted form.

The "Trigger Error" prompt has a bug in the released version. It is
intended as a halt-and-catch-fire termination of a form. Likely of limited
use in field deployments.

For most users, form customization would be achieved by adding CSS and
Templates to the individual forms. We expect that the Default form will
continue to be downloaded from ODK Aggregate. Default form (javascript) has
a version just like in the old XForms, ODK Survey renders your survey with
the most recent version of the default form on the device (so you can
easily update the core Javascript used for form rendering across all
forms). Updating to the latest core javascript is as easy as downloading
the newest 'Default form" from your server. That said, it will eventually
be hidden from the ODK Survey forms list, and perhaps even moved to a
different location on the sdcard. The 'Default form' contains all the
common Javascript that is used across all forms. Organizations with
Javascript expertise that want very tailored presentations may wish to
modify or rewrite most of this code to suit their needs. If you take the
forms directory on the device (/sdcard/odk/js/forms) and copy it to an
Apache or IIS webserver, if you then use Chrome to browse to the default
form path (containing an index.html), you can then edit the URL setting
#formPath=... to a relative path to a 'real' form (e.g., ../exampleForm/).
Everything renders and works in Chrome except things that are not yet
doable within a browser (audio/video/image/barcode/geopoint capture), and
there is no functionality written to submit data up to a server (that is
handled by the ODK Survey app (Java) code).

W.r..t speed on slower devices: Certainly, if you strip out all JQuery
Mobile functionality and remove the Template and Backbone code, you can get
a very performant experience on a Droid. We sacrificed this performance to
give users an more easily customizable and more polished look via Templates
and JQuery Mobile CSS features. As you note, the newest 4.x phones handle
this added complexity with ease.

The Javascript is currently very conservative with respect to its
interactions with the database and value updates; as the software gets more
stable, we should be able to relax our vigilance, saving a fair amount on
garbage collections within larger forms.

Mitch

··· On Fri, Feb 1, 2013 at 11:01 AM, Nathan Breit wrote:

Hi Neil, Thanks for the fantastic feedback!
I'll try to respond to a few of the items you bring up:

Question: Can you limit access to edit and delete in the instance list?

Yes, it is be possible to override the default instances list screen with
anything you want. I may be doing this for one of the deployments we're
planning and I'll plan to make the form (or at least the relevant parts)
available as an example.

The disappearing name bug is related to screens dynamically updating so
prompts can disappear/reappear/change based on the other values on the
screen. There are some technical issues we still have to work out there.

The default form contains all the core javascript. I think we're going to
be reorganizing the code to get rid of it.

W.r.t. pulling answers from other forms/data sources an inserting them in
labels, it is possible to do it with a custom templates/prompt. However, I
think we might add some features to make it easier.
One approach I like for that would be to us the queries sheethttp://code.google.com/p/opendatakit/wiki/XLSForm2Docs#queriesto identify the data source, and then add handlebars helper like this to
use queries in labels:
{{#withQuery query_name}} {{queryData}} {{/withQuery}}
What do you think?

Prompt links would probably be most useful in a job-aid scenario. They
would be good for allowing someone to choose between different sections of
a form based on the task they want to do. They would also be useful for
adding "more info" screens that give detailed explanations of questions.
For example, if there were a question like "Does the patient have stridor?"
one could add a link to a long explanation and video about how to assess
stridor.

The d3 prompt was done by creating a custom templatehttp://code.google.com/p/opendatakit/wiki/XLSForm2Docs#templatePath.
You can see the template herehttp://code.google.com/p/opendatakit/source/browse/form-files/example/ageWeightPlot.handlebars?repo=collect2
.

Forms are stored in the sdcard/odk/js/forms directory.

Added to my todo list:
disable back button on first question.
disable the language menu when there are no translations to choose from

Regards,
-Nathan

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

Asymmetric-key encrypted forms (public key encryption), are supported in
ODK Survey alpha (and production) as part of the legacy publishing path,
but not as part of the bi-directional synchronization mechanism.

At initial release, the bi-directional synchronization mechanism will not
have any data encryption, but will rely on the use of https: protocols
between the device and server to protect the data during transmissions
(exactly like https: secures online purchasing transactions). The data will
be stored unencrypted on the device and stored unencrypted on the server.

Since the textual data will reside in a SQLite database on the device, it
is possible to replace the database with an encrypted database (
https://guardianproject.info/code/sqlcipher/ ). Since the media files,
once captured, are accessed through a FileProvider abstraction, it would
also be possible to encrypt those.

But database encryption has a few issues -- the operation of the javascript
would need to be reworked and, while the datastore might be encrypted,
securing the platform would mean imposing access restrictions on the
content providers that could access that data (e.g., the
SubmissionProvider), and careful selection and thought about the 3rd party
tools that are used to capture and play media files (to ensure that no
unencrypted copies of those files exist).

Thus, wholesale symmetric-key data encryption is doable, but will not be
present in the initial releases. Per-row (per-submission) or per-column
(per-data-field) symmetric-key encryption would be more difficult, and it
is unclear what the requirements are for that. The synchronization
mechanism considers a row (submission) as a all-or-nothing unit-of-change;
it is doubtful there would ever be a mechanism to send only certain columns
to certain devices based upon the access rights of those users.

··· -----------------

ODK Aggregate will have separate data storage, distinct from the current
1.x forms and submissions storage, for the new forms and data.

Mitch

On Fri, Mar 1, 2013 at 8:27 AM, Daniele Grasso daniele.grasso86@gmail.comwrote:

I'm also interested in this aspect of bi-directional synchronization, and
especially in the case we want some kind of encryption. How can these 2
users share the symmetric key? the actual solution of the Encrypted Forms
seems difficult in this scenario, because there can be many users
interested in the same form data, and maybe we cannot know them in advance,
before encrypting the form.

And also, will there be differences in ODK Aggregate, depending on the new
ideas on ODK 2.0?
thanks in advance,

Daniele

Il giorno venerdì 1 febbraio 2013 16:13:11 UTC+1, Nelson Mambre ha scritto:

"While ODK Survey will have a backward-compatible form submission process
(like in the Alpha), there will be a new bi-directional synchronization
mechanism as well, which will not look anything like the
backward-compatible mechanisms."

Mitch, can you explain further how this bi-directional synchronization
will be?
One of my interest for Survey would be in case of for example medical
records, if a person goes to Doctor A, when they go a next time to Doctor B
at another location, Doctor B should be able to log in and download that
record. Would something like this be possible?

Nelson

--
--
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.

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