Increasing data safety with ODK Collect v1.4.4

Hi all,

I wanted to highlight two new features that Nafundi has added to ODK
Collect v1.4.4 to increase data safety -- delete after send and forced
form saves. If you haven't upgraded already, now is a great time!

In ODK Collect v1.4.4 , you can now automatically delete finalized
forms and accompanying multimedia after submission. This feature is
useful for campaigns collecting sensitive data (e.g., patient records)
or multimedia that uses a lot of space (e.g., high resolution video).
Delete after send is disabled by default and can be turned on in
General Settings.

ODK Collect v1.4.4 also includes support for a saveIncomplete() form
attribute that enables a forced form save on any prompt (e.g., right
at the end of a major module). To trigger this save, add the
saveIncomplete attribute to a prompt's bind and the form will save
when that prompt becomes visible. The form XML looks like this:

If you use XLSForm to design your forms, you will soon be able to add
bind::saveIncomplete as a column and enable saveIncomplete that way.

You can find out more about these features at
http://nafundi.com/blog/posts/increasing-data-safety-in-odk-collect-with-delete-after-send-and-forced-form-save

Yaw

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

Great feature, thanks!

··· On Wednesday, September 10, 2014 12:12:42 AM UTC+2, Yaw Anokwa wrote: > > Hi all, > > I wanted to highlight two new features that Nafundi has added to ODK > Collect v1.4.4 to increase data safety -- delete after send and forced > form saves. If you haven't upgraded already, now is a great time! > > In ODK Collect v1.4.4 , you can now automatically delete finalized > forms and accompanying multimedia after submission. This feature is > useful for campaigns collecting sensitive data (e.g., patient records) > or multimedia that uses a lot of space (e.g., high resolution video). > Delete after send is disabled by default and can be turned on in > General Settings. > > ODK Collect v1.4.4 also includes support for a saveIncomplete() form > attribute that enables a forced form save on any prompt (e.g., right > at the end of a major module). To trigger this save, add the > saveIncomplete attribute to a prompt's bind and the form will save > when that prompt becomes visible. The form XML looks like this: > > > > If you use XLSForm to design your forms, you will soon be able to add > bind::saveIncomplete as a column and enable saveIncomplete that way. > > You can find out more about these features at > > http://nafundi.com/blog/posts/increasing-data-safety-in-odk-collect-with-delete-after-send-and-forced-form-save > > Yaw > -- > Need ODK services? http://nafundi.com provides form design, server > setup, professional support, and software development for ODK. >

Hi Yaw,

This is indeed a very helpful feature.

I'm using XLSForm and was wondering what value goes into the cell under bind::saveIncomplete. Like, is it "true", 1, or "yes"?

Thanks.

Lingstone.

Hi everybody,

finally i managed to get tested in my survey, but i have a question....
about the deletion after send ...

As I see the deletion after send is from "Edit Saved Form" List.

Is it possible to do this for "Delete Saved Form" List ??? Where this list
is filled up with the forms.. ? Why this list is filled with send forms if
i can't do anything with them. I believe that the right procedure is to
deleted also from this list...

Is it an easy procedure to implement that ?

Waiting your comments

Best Regards
Panos

··· On Wednesday, September 10, 2014 1:12:42 AM UTC+3, Yaw Anokwa wrote: > > Hi all, > > I wanted to highlight two new features that Nafundi has added to ODK > Collect v1.4.4 to increase data safety -- delete after send and forced > form saves. If you haven't upgraded already, now is a great time! > > In ODK Collect v1.4.4 , you can now automatically delete finalized > forms and accompanying multimedia after submission. This feature is > useful for campaigns collecting sensitive data (e.g., patient records) > or multimedia that uses a lot of space (e.g., high resolution video). > Delete after send is disabled by default and can be turned on in > General Settings. > > ODK Collect v1.4.4 also includes support for a saveIncomplete() form > attribute that enables a forced form save on any prompt (e.g., right > at the end of a major module). To trigger this save, add the > saveIncomplete attribute to a prompt's bind and the form will save > when that prompt becomes visible. The form XML looks like this: > > > > If you use XLSForm to design your forms, you will soon be able to add > bind::saveIncomplete as a column and enable saveIncomplete that way. > > You can find out more about these features at > > http://nafundi.com/blog/posts/increasing-data-safety-in-odk-collect-with-delete-after-send-and-forced-form-save > > Yaw > -- > Need ODK services? http://nafundi.com provides form design, server > setup, professional support, and software development for ODK. >

I usually use true(), but I think the alternatives you've listed should work.

Yaw

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

On Thu, Sep 11, 2014 at 2:16 AM, chiume.ling@gmail.com wrote:

Hi Yaw,

This is indeed a very helpful feature.

I'm using XLSForm and was wondering what value goes into the cell under bind::saveIncomplete. Like, is it "true", 1, or "yes"?

Thanks.

Lingstone.

--

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.

Once you have the "delete sent forms" checked, then they would be deleted
after they are sent, so the only forms that would appear in the "Delete
Saved Forms" list would be the not-yet-completed forms, or the
not-yet-successfully-sent forms.

Of course, upon first configuring this, you must go through and delete the
already-successfully-sent forms manually.

This is not done automatically, and doing so is against our design
philosophy:

We always preserve data by default.

So if you do not take actions to delete data, we don't make assumptions and
infer that the software should.

··· On Wed, Nov 12, 2014 at 2:48 PM, Panos Papadatos wrote:

Hi everybody,

finally i managed to get tested in my survey, but i have a question....
about the deletion after send ...

As I see the deletion after send is from "Edit Saved Form" List.

Is it possible to do this for "Delete Saved Form" List ??? Where this list
is filled up with the forms.. ? Why this list is filled with send forms if
i can't do anything with them. I believe that the right procedure is to
deleted also from this list...

Is it an easy procedure to implement that ?

Waiting your comments

Best Regards
Panos

On Wednesday, September 10, 2014 1:12:42 AM UTC+3, Yaw Anokwa wrote:

Hi all,

I wanted to highlight two new features that Nafundi has added to ODK
Collect v1.4.4 to increase data safety -- delete after send and forced
form saves. If you haven't upgraded already, now is a great time!

In ODK Collect v1.4.4 , you can now automatically delete finalized
forms and accompanying multimedia after submission. This feature is
useful for campaigns collecting sensitive data (e.g., patient records)
or multimedia that uses a lot of space (e.g., high resolution video).
Delete after send is disabled by default and can be turned on in
General Settings.

ODK Collect v1.4.4 also includes support for a saveIncomplete() form
attribute that enables a forced form save on any prompt (e.g., right
at the end of a major module). To trigger this save, add the
saveIncomplete attribute to a prompt's bind and the form will save
when that prompt becomes visible. The form XML looks like this:

If you use XLSForm to design your forms, you will soon be able to add
bind::saveIncomplete as a column and enable saveIncomplete that way.

You can find out more about these features at
http://nafundi.com/blog/posts/increasing-data-safety-in-odk-
collect-with-delete-after-send-and-forced-form-save

Yaw

Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.

--

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

Thanks.

··· On Sep 11, 2014 3:37 PM, "Yaw Anokwa" wrote:

I usually use true(), but I think the alternatives you've listed should
work.

Yaw

Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.

On Thu, Sep 11, 2014 at 2:16 AM, chiume.ling@gmail.com wrote:

Hi Yaw,

This is indeed a very helpful feature.

I'm using XLSForm and was wondering what value goes into the cell under
bind::saveIncomplete. Like, is it "true", 1, or "yes"?

Thanks.

Lingstone.

--

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/3A4q8OTCSUo/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 Mitch,

i have done the following procedure but when i send the form, i'm still
see the instance

  1. in file explorer
  2. In "Delete Saved Forms" button
  3. In "Send Finalized Form" button (if i choose to change View and see Sent
    and Unsent)

Is it something i'm doing wrong... ???

The same behavior i see in ODK Collect 1.4.4 (1045) from google play...

Thanks
Panos

··· On Thursday, November 13, 2014 1:28:48 AM UTC+2, Mitch Sundt wrote: > > Once you have the "delete sent forms" checked, then they would be deleted > after they are sent, so the only forms that would appear in the "Delete > Saved Forms" list would be the not-yet-completed forms, or the > not-yet-successfully-sent forms. > > Of course, upon first configuring this, you must go through and delete the > already-successfully-sent forms manually. > > This is not done automatically, and doing so is against our design > philosophy: > > We always preserve data by default. > > So if you do not take actions to delete data, we don't make assumptions > and infer that the software should. > > > > > > On Wed, Nov 12, 2014 at 2:48 PM, Panos Papadatos <ppapad...@gmail.com > wrote: > >> Hi everybody, >> >> finally i managed to get tested in my survey, but i have a >> question.... about the deletion after send ... >> >> As I see the deletion after send is from "Edit Saved Form" List. >> >> Is it possible to do this for "Delete Saved Form" List ??? Where this >> list is filled up with the forms.. ? Why this list is filled with send >> forms if i can't do anything with them. I believe that the right procedure >> is to deleted also from this list... >> >> Is it an easy procedure to implement that ? >> >> Waiting your comments >> >> Best Regards >> Panos >> >> >> >> >> On Wednesday, September 10, 2014 1:12:42 AM UTC+3, Yaw Anokwa wrote: >>> >>> Hi all, >>> >>> I wanted to highlight two new features that Nafundi has added to ODK >>> Collect v1.4.4 to increase data safety -- delete after send and forced >>> form saves. If you haven't upgraded already, now is a great time! >>> >>> In ODK Collect v1.4.4 , you can now automatically delete finalized >>> forms and accompanying multimedia after submission. This feature is >>> useful for campaigns collecting sensitive data (e.g., patient records) >>> or multimedia that uses a lot of space (e.g., high resolution video). >>> Delete after send is disabled by default and can be turned on in >>> General Settings. >>> >>> ODK Collect v1.4.4 also includes support for a saveIncomplete() form >>> attribute that enables a forced form save on any prompt (e.g., right >>> at the end of a major module). To trigger this save, add the >>> saveIncomplete attribute to a prompt's bind and the form will save >>> when that prompt becomes visible. The form XML looks like this: >>> >>> >> /> >>> >>> If you use XLSForm to design your forms, you will soon be able to add >>> bind::saveIncomplete as a column and enable saveIncomplete that way. >>> >>> You can find out more about these features at >>> http://nafundi.com/blog/posts/increasing-data-safety-in-odk- >>> collect-with-delete-after-send-and-forced-form-save >>> >>> Yaw >>> -- >>> Need ODK services? http://nafundi.com provides form design, server >>> setup, professional support, and software development for ODK. >>> >> >> -- >> -- >> 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 >

Something seems broken about the "delete after send" feature. I have this
option checked and yet the finalized form instances keep appearing. As
Panos wrote I also see the instance via

  1. file explorer
  2. "Delete Saved Forms" button
  3. "Send Finalized Form" button (be sure to use menu....Change View...Sent
    and Unsent)

I am using 1.4.5 (1048)

What could be wrong?

Jaideep

I've created a bug for this:
https://code.google.com/p/opendatakit/issues/detail?id=1144

··· On Mon, May 11, 2015 at 5:56 AM, Jaideep Baphna, CFA wrote:

Something seems broken about the "delete after send" feature. I have this
option checked and yet the finalized form instances keep appearing. As
Panos wrote I also see the instance via

  1. file explorer
  2. "Delete Saved Forms" button
  3. "Send Finalized Form" button (be sure to use menu....Change View...Sent
    and Unsent)

I am using 1.4.5 (1048)

What could be wrong?

Jaideep

--

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