Transferring Forms Between Mobile Devices

Hello,

I am happily using ODK Collect 1.3 and ODK Aggregate 1.3.4.

I am working on a project in which there is an operational need to transfer
a partially completed form from one mobile device (A) to another (B) and
for the form to then be completed on the second device (B).

The form itself may exist on both devices, but the form data at first is
resident only on the first device. Due to operational constraints the
scenario does not allow data to be transferred directly between the two
devices.

I am seeking advice or ideas as to how to achieve this.

My thoughts are:

  1. Device A marks the form as Finalized, but also flags it as requiring
    transfer to a second device. This might be done through completing a
    dedicated field with a sentinel value.
  2. Device A then submits the form data to Aggregate.
  3. A new form is (somehow?) created based on the original form which
    device A had, but with data default values taken from the submitted data.
    This form (somehow?) becomes available for download from Aggregate.
  4. Device B downloads the "new" form from Aggregate. The questions which
    were answered on Device A now have the submitted default values.

Step 3 seems problematic.

I understand that there is an in-principle reluctance to allow the
submission of partially complete forms to Aggregate - hence the Finalize
mechanism. However in this case the intention is to enable the form to be
migrated between mobile devices during its lifetime.

Any ideas or input would be appreciated.

Thank you.

Leon

Leon,

There is no easy way of doing this without writing a ton of code. You
might want to take a look at Group Complete
(http://www.groupcomplete.com). It does a bit of device to device
transfer. The product itself has been discontinued, but the source
code is at https://github.com/radicaldynamic/gcmobile and it might be
a good place to start.

Yaw

··· -- Need ODK services? http://nafundi.com provides form design, professional support, custom reporting, and software development for ODK.

On Tue, Oct 1, 2013 at 1:31 AM, Leon Wende leon.wende@gmail.com wrote:

Hello,

I am happily using ODK Collect 1.3 and ODK Aggregate 1.3.4.

I am working on a project in which there is an operational need to transfer
a partially completed form from one mobile device (A) to another (B) and for
the form to then be completed on the second device (B).

The form itself may exist on both devices, but the form data at first is
resident only on the first device. Due to operational constraints the
scenario does not allow data to be transferred directly between the two
devices.

I am seeking advice or ideas as to how to achieve this.

My thoughts are:

Device A marks the form as Finalized, but also flags it as requiring
transfer to a second device. This might be done through completing a
dedicated field with a sentinel value.
Device A then submits the form data to Aggregate.
A new form is (somehow?) created based on the original form which device A
had, but with data default values taken from the submitted data. This form
(somehow?) becomes available for download from Aggregate.
Device B downloads the "new" form from Aggregate. The questions which were
answered on Device A now have the submitted default values.

Step 3 seems problematic.

I understand that there is an in-principle reluctance to allow the
submission of partially complete forms to Aggregate - hence the Finalize
mechanism. However in this case the intention is to enable the form to be
migrated between mobile devices during its lifetime.

Any ideas or input would be appreciated.

Thank you.

Leon

--

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.

Hello Leon,

With regards to the mentioned challenge, were you able to figure a way to
get the transfer to work (for partially filled data on one instance to be
transferred first hand to another device in the field, real-time) on ODK?

Your response will be highly appreciated.

Dear Yaw,

Is there a solution that exists right now by any chance?

Many thanks guys!!! and looking forward to hear from you soon!

··· On Tuesday, October 1, 2013 at 9:31:29 AM UTC+1, Leon Wende wrote: > > Hello, > > I am happily using ODK Collect 1.3 and ODK Aggregate 1.3.4. > > I am working on a project in which there is an operational need to > transfer a partially completed form from one mobile device (A) to another > (B) and for the form to then be completed on the second device (B). > > The form itself may exist on both devices, but the form data at first is > resident only on the first device. Due to operational constraints the > scenario does not allow data to be transferred directly between the two > devices. > > I am seeking advice or ideas as to how to achieve this. > > My thoughts are: > > 1. Device A marks the form as Finalized, but also flags it as > requiring transfer to a second device. This might be done through > completing a dedicated field with a sentinel value. > 2. Device A then submits the form data to Aggregate. > 3. A new form is (somehow?) created based on the original form which > device A had, but with data default values taken from the submitted data. > This form (somehow?) becomes available for download from Aggregate. > 4. Device B downloads the "new" form from Aggregate. The questions > which were answered on Device A now have the submitted default values. > > Step 3 seems problematic. > > I understand that there is an in-principle reluctance to allow the > submission of partially complete forms to Aggregate - hence the Finalize > mechanism. However in this case the intention is to enable the form to be > migrated between mobile devices during its lifetime. > > Any ideas or input would be appreciated. > > Thank you. > > Leon >

Chinedu,

The solution exists in a fork of ODK, but it needs funding (or effort)
to merge it into trunk. Is this an effort you or a developer you know
would be able to lead?

Yaw

··· -- Need ODK consultants? Nafundi provides form design, server setup, in-field training, and software development for ODK. Go to https://nafundi.com to get started.

On Wed, Aug 31, 2016 at 2:10 PM, Chinedu Arinze chinedar@gmail.com wrote:

Hello Leon,

With regards to the mentioned challenge, were you able to figure a way to
get the transfer to work (for partially filled data on one instance to be
transferred first hand to another device in the field, real-time) on ODK?

Your response will be highly appreciated.

Dear Yaw,

Is there a solution that exists right now by any chance?

Many thanks guys!!! and looking forward to hear from you soon!

On Tuesday, October 1, 2013 at 9:31:29 AM UTC+1, Leon Wende wrote:

Hello,

I am happily using ODK Collect 1.3 and ODK Aggregate 1.3.4.

I am working on a project in which there is an operational need to
transfer a partially completed form from one mobile device (A) to another
(B) and for the form to then be completed on the second device (B).

The form itself may exist on both devices, but the form data at first is
resident only on the first device. Due to operational constraints the
scenario does not allow data to be transferred directly between the two
devices.

I am seeking advice or ideas as to how to achieve this.

My thoughts are:

Device A marks the form as Finalized, but also flags it as requiring
transfer to a second device. This might be done through completing a
dedicated field with a sentinel value.
Device A then submits the form data to Aggregate.
A new form is (somehow?) created based on the original form which device A
had, but with data default values taken from the submitted data. This form
(somehow?) becomes available for download from Aggregate.
Device B downloads the "new" form from Aggregate. The questions which were
answered on Device A now have the submitted default values.

Step 3 seems problematic.

I understand that there is an in-principle reluctance to allow the
submission of partially complete forms to Aggregate - hence the Finalize
mechanism. However in this case the intention is to enable the form to be
migrated between mobile devices during its lifetime.

Any ideas or input would be appreciated.

Thank you.

Leon

--

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.

Hello Yaw,

I am able to lead the effort and can discuss possible funding terms.

How do I reach you directly?

Many thanks.

Best Regards,
Chinedu Arinze.
Data Manager II
Ebola Emergency Operations Center|EEOC.
+2348032745375.

··· On 5 September 2016 at 12:48, Yaw Anokwa wrote:

Chinedu,

The solution exists in a fork of ODK, but it needs funding (or effort)
to merge it into trunk. Is this an effort you or a developer you know
would be able to lead?

Yaw

Need ODK consultants? Nafundi provides form design, server setup,
in-field training, and software development for ODK. Go to
https://nafundi.com to get started.

On Wed, Aug 31, 2016 at 2:10 PM, Chinedu Arinze chinedar@gmail.com wrote:

Hello Leon,

With regards to the mentioned challenge, were you able to figure a way to
get the transfer to work (for partially filled data on one instance to be
transferred first hand to another device in the field, real-time) on ODK?

Your response will be highly appreciated.

Dear Yaw,

Is there a solution that exists right now by any chance?

Many thanks guys!!! and looking forward to hear from you soon!

On Tuesday, October 1, 2013 at 9:31:29 AM UTC+1, Leon Wende wrote:

Hello,

I am happily using ODK Collect 1.3 and ODK Aggregate 1.3.4.

I am working on a project in which there is an operational need to
transfer a partially completed form from one mobile device (A) to
another

(B) and for the form to then be completed on the second device (B).

The form itself may exist on both devices, but the form data at first is
resident only on the first device. Due to operational constraints the
scenario does not allow data to be transferred directly between the two
devices.

I am seeking advice or ideas as to how to achieve this.

My thoughts are:

Device A marks the form as Finalized, but also flags it as requiring
transfer to a second device. This might be done through completing a
dedicated field with a sentinel value.
Device A then submits the form data to Aggregate.
A new form is (somehow?) created based on the original form which
device A

had, but with data default values taken from the submitted data. This
form

(somehow?) becomes available for download from Aggregate.
Device B downloads the "new" form from Aggregate. The questions which
were

answered on Device A now have the submitted default values.

Step 3 seems problematic.

I understand that there is an in-principle reluctance to allow the
submission of partially complete forms to Aggregate - hence the Finalize
mechanism. However in this case the intention is to enable the form to
be

migrated between mobile devices during its lifetime.

Any ideas or input would be appreciated.

Thank you.

Leon

--

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.

--

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 a topic in the
Google Groups "ODK Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/opendatakit/b8m6u652RKU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi Chinedu,

Send me an email off list (yanokwa at nafundi dot com) and we can find
a developer to take this on.

Yaw

··· -- Need ODK consultants? Nafundi provides form design, server setup, in-field training, and software development for ODK. Go to https://nafundi.com to get started.

On Mon, Sep 5, 2016 at 11:55 AM, Chinedu Arinze chinedar@gmail.com wrote:

Hello Yaw,

I am able to lead the effort and can discuss possible funding terms.

How do I reach you directly?

Many thanks.

Best Regards,
Chinedu Arinze.
Data Manager II
Ebola Emergency Operations Center|EEOC.
+2348032745375.

On 5 September 2016 at 12:48, Yaw Anokwa yanokwa@nafundi.com wrote:

Chinedu,

The solution exists in a fork of ODK, but it needs funding (or effort)
to merge it into trunk. Is this an effort you or a developer you know
would be able to lead?

Yaw

Need ODK consultants? Nafundi provides form design, server setup,
in-field training, and software development for ODK. Go to
https://nafundi.com to get started.

On Wed, Aug 31, 2016 at 2:10 PM, Chinedu Arinze chinedar@gmail.com wrote:

Hello Leon,

With regards to the mentioned challenge, were you able to figure a way
to
get the transfer to work (for partially filled data on one instance to
be
transferred first hand to another device in the field, real-time) on
ODK?

Your response will be highly appreciated.

Dear Yaw,

Is there a solution that exists right now by any chance?

Many thanks guys!!! and looking forward to hear from you soon!

On Tuesday, October 1, 2013 at 9:31:29 AM UTC+1, Leon Wende wrote:

Hello,

I am happily using ODK Collect 1.3 and ODK Aggregate 1.3.4.

I am working on a project in which there is an operational need to
transfer a partially completed form from one mobile device (A) to
another
(B) and for the form to then be completed on the second device (B).

The form itself may exist on both devices, but the form data at first
is
resident only on the first device. Due to operational constraints the
scenario does not allow data to be transferred directly between the two
devices.

I am seeking advice or ideas as to how to achieve this.

My thoughts are:

Device A marks the form as Finalized, but also flags it as requiring
transfer to a second device. This might be done through completing a
dedicated field with a sentinel value.
Device A then submits the form data to Aggregate.
A new form is (somehow?) created based on the original form which
device A
had, but with data default values taken from the submitted data. This
form
(somehow?) becomes available for download from Aggregate.
Device B downloads the "new" form from Aggregate. The questions which
were
answered on Device A now have the submitted default values.

Step 3 seems problematic.

I understand that there is an in-principle reluctance to allow the
submission of partially complete forms to Aggregate - hence the
Finalize
mechanism. However in this case the intention is to enable the form to
be
migrated between mobile devices during its lifetime.

Any ideas or input would be appreciated.

Thank you.

Leon

--

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.

--

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 a topic in the
Google Groups "ODK Community" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/opendatakit/b8m6u652RKU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

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.