Pushing updated questionnaires to phones

Hi All

I would like a mechanism to be able to push updated versions of
questionnaires to devices without requiring the user to manually make
a request. Is this possible with the current ODK Collect client or
with minimal additional development effort?

My thinking is that a trigger can be placed on start-up (if internet
connectivity is available) or on submission.
What is the best way to deal with the older version of the
questionnaire that is already on the device? Deleting doesn't make
sense because of the possibility of an unsent submissions.

I have two different use-cases at the moment:

  1. I have a number of devices deployed in remote areas and I do not
    have direct access to enumerators in order to remind them to check for
    updated questionnaires
  2. In another project, using a customised backend, I deliver
    questionnaires that are tailored to the specific enumerator based on
    the surveys that they need to complete. These questionnaires are
    pre-filled in based on databae fields but need to be constantly
    updated. Requiring a manual re-sync is error prone.

Any advice would be appreciated.
Adi

··· -- Adi Eyal Project Manager phone: +27 78 014 2469 skype: adieyalcas www.burgercom.co.za

Adi,

You'd need to write some custom code to do what you are describing.

Yaw

··· On Sun, Jul 22, 2012 at 10:49 PM, Adi Eyal wrote: > Hi All > > I would like a mechanism to be able to push updated versions of > questionnaires to devices without requiring the user to manually make > a request. Is this possible with the current ODK Collect client or > with minimal additional development effort? > > My thinking is that a trigger can be placed on start-up (if internet > connectivity is available) or on submission. > What is the best way to deal with the older version of the > questionnaire that is already on the device? Deleting doesn't make > sense because of the possibility of an unsent submissions. > > I have two different use-cases at the moment: > > 1. I have a number of devices deployed in remote areas and I do not > have direct access to enumerators in order to remind them to check for > updated questionnaires > 2. In another project, using a customised backend, I deliver > questionnaires that are tailored to the specific enumerator based on > the surveys that they need to complete. These questionnaires are > pre-filled in based on databae fields but need to be constantly > updated. Requiring a manual re-sync is error prone. > > Any advice would be appreciated. > Adi > > > -- > Adi Eyal > Project Manager > phone: +27 78 014 2469 > skype: adieyalcas > www.burgercom.co.za

ODK Collect 1.2 displays the forms in alphabetical order, with newer
versions of a form appearing above the older versions, and if you are using
versions, the version is displayed below the form name. So your users
should just be able to select the topmost form and have the most recent one.

There are a lot of user interface, connectivity and workflow design
questions surrounding automatic syncing, and it is unclear what would or
would not make sense across different deployments.

That said, the tasks to interact with the server are already written, so
the additional code is mostly just chaining these various tasks together.

Mitch

··· On Sun, Jul 22, 2012 at 11:12 PM, Yaw Anokwa wrote:

Adi,

You'd need to write some custom code to do what you are describing.

Yaw

On Sun, Jul 22, 2012 at 10:49 PM, Adi Eyal adi@burgercom.co.za wrote:

Hi All

I would like a mechanism to be able to push updated versions of
questionnaires to devices without requiring the user to manually make
a request. Is this possible with the current ODK Collect client or
with minimal additional development effort?

My thinking is that a trigger can be placed on start-up (if internet
connectivity is available) or on submission.
What is the best way to deal with the older version of the
questionnaire that is already on the device? Deleting doesn't make
sense because of the possibility of an unsent submissions.

I have two different use-cases at the moment:

  1. I have a number of devices deployed in remote areas and I do not
    have direct access to enumerators in order to remind them to check for
    updated questionnaires
  2. In another project, using a customised backend, I deliver
    questionnaires that are tailored to the specific enumerator based on
    the surveys that they need to complete. These questionnaires are
    pre-filled in based on databae fields but need to be constantly
    updated. Requiring a manual re-sync is error prone.

Any advice would be appreciated.
Adi

--
Adi Eyal
Project Manager
phone: +27 78 014 2469
skype: adieyalcas
www.burgercom.co.za

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