Spec proposal: Editable submissions

Development
, , ,
1

As discussed in this thread, the ODK core team would like to make it possible to edit submissions after they have been finalized or sent in Collect. The intention here is that XForm instances that are edits of a submission will include a deprecatedId node in meta containing the ID of the original submission (along with a new unique instanceId). This is already how edits work in Central.

To avoid allowing this behaviour in projects or forms where it's not appropriate, we'd like to propose making additions to the XLSForm and XForm specs to allow opting-in on a form by form basis. The changes proposed are:

XForm

  • A new odk:editable attribute for the submission node:
    • If the value of odk:editable is "true", clients should allow sent submissions to be edited using deprecatedId as a way of linking edits together.
    • If the value of odk:editable is anything else, clients should not allow edits after submission (assuming they don't usually).

XLSForm

  • A new editable column in the settings sheet that's value will be used to define the new odk:editable attribute.
4 Likes