Explore options for recovering deleted draft submissions

[ktuite]

If a draft form gets shared with data collectors and collects real submissions, it can lead to a number of problems:

• If the draft form gets updated (or deleted, or even published), all submissions associated with that draft version are automatically purged. The only possible option is checking to see if they are still on the devices and resending.
• There is no easy way to preserve the draft submissions or re-associate them with a published version of the form, i.e. publish the form and have the draft submissions carry over to the published form.

We are redesigning the draft form page and the draft QR code to help people avoid this situation, but is there anything else we can do on the backend to give these submissions a chance to be recovered?

Some ideas:

• mark the form draft def as soft-deleted when the draft is published, replaced, or abandoned, instead of purging it immediately
• if the draft submissions are soft deleted, can they be fetched through odata feed?
• can we eventually have a concept of a result set / submission set so you could partition results by year, location, draft/real and have tools to move between those sets?

This issue is about investigating these ideas to see if there is a quick way to use existing deletion infrastructure to keep deleted draft submissions around for a little while.