In reference to an existing feature in recent past: This change may have affected the feature/flexibility. https://github.com/getodk/collect/commit/640ca84dc88cb0cb005267784912eda658b44b0c
1. What is the general goal of the feature?
Re-Allow form and/or media updates if the form was sourced from Central/Aggregate even if current submission account is a Google Account/Drive in Collect.
One way is to re-allow the updates in collect as they used to be prior to Aug 2020.
An alternate could be to update forms+media based on source server of each form and not the currently selected Server/Account in collect. Furthermore, let the user decide which update mode to use: Either based on each form or Server in general settings.
Another could be to separate FormServer from Submission Account allowing Collect User flexibility to point to separate server for forms (e.g. Central or Aggregate) while submitting data via Google Account to Google Drive or other Server. This may decouple forms server from submission account and therefore Google Account may not intersect with Form/Media update settings. This ensures the forms/media continue to receive updates from Central or Aggregate without the User having to switch between servers for the sole purpose of getting form updates. This is a major new hassle and point of confusion and makes the automatic form updates not very flexible.
2. What are some example use cases for this feature?
-
CRUD operations on submitted data until this feature (partially) becomes available in Central
User may host forms in Central or Aggregate while submitting data to Google Drive for ease of viewing, editing, updating received data. This will be essential until Central offers facility to Accept/Reject/Update/editing/sharing incoming data via web forms. -
Use google app script or other 3rd party analysis tools in the cloud
Allows admins to use a vast array of Google App Scripts for minor workflows thus complementing the existing feature set offered by ODK Products. This also allows for diverse use cases be implemented with very little effort on the User side e.g. mail, notifications, workflows etc. While ODK may not support this feature explicitly - this flexibility may not be very complex from an adoption perspective. This used to be an unsaid/implicit feature in Collect/Aggregate and was expected to be carried forward. I would really appreciate if this can be re-instated.
Inline with current Collect feature where different forms are allowed to contain submission URLs pointing to multiple targets - the form update should be tied to the source server of the form and not just the currently selected server. Form Updates should still be allowed for forms that were sourced from Central even if the Submission Server account is Google based. Please note Form updates in collect that were sourced from Aggregate used to update just fine and were an expected feature in central from a user's perspective. The current workaround is to switch back and forth between Servers and that is a hassle.
3. What can you contribute to making this feature a reality?
I can enthusiastically advise and test.
Reference to an existing issue