Ona has been hired by a client to add support for push notifications into ODK Collect. We already have a list of requirements from the client that need to be implemented before a deadline. Since our intention is to make this feature available to everyone else, we'd appreciate feedback from the commu…

As of Collect v1.15.0 , there is a setting in Form Management to turn on automatic checks on form version. If an update is available, a notification will be shown and if automatic downloads are turned on, the new version will be downloaded [36%20PM] Furthermore, only the latest version of a form is…

I've put together a strawman issue for this on the roadmap repo: Collect: Form updates and versioning opened 12:01PM - 14 Feb 18 UTC (UTC) closed 05:57PM - 21 Aug 18 UTC (UTC) […

Great to see some movement on this again, thanks @adam.butler ! I am in strong agreement for polling to detect form updates. The polling frequency can be made configurable with a reasonable default that balances data usage and usefulness. As Adam mentions in his spec above, @Grzesiek2010 has already…

Thanks @LN . I agree with everything you say! On the form updates without version increment question, I would be tempted to do nothing. If admins are not changing version numbers, that's their lookout. Adding a form hash is duplicating functionality, and would probably lead to both user confusion an…

Cool. @LN , @adam.butler I guess polling makes sense, especially since deploying the extra broker will definitely not work for some setups. I had a few questions though: At what point do you think a device should stop polling the /formList endpoint (if that's what will be polled)? Or is it a good …

Hi @Jason_Rogena , thanks a lot for chiming in! I tend to think that a server should be able to cope with the load of sporadic polling: it's not like these requests require a lot of network traffic or disk writes. It would be good to get some real world numbers, but let's consider (what I would as…

[image] adam.butler: I tend to think that a server should be able to cope with the load of sporadic polling: it’s not like these requests require a lot of network traffic or disk writes. I'm a bit concerned because of deployments like ona.io where we expect tens of thousands of devices online…

I’m a bit concerned because of deployments like ona.io where we expect tens of thousands of devices online and polling, but I guess we should test first and see if the load is worth worrying about. Right, good point, I didn't consider multi-tenanted cloud installations. Would you be OK with runni…

In reducing what gets returned and only returning what is necessary, should we do a polling which only needs to result in new or updated forms? I understand this could mean an addition to the spec. ODK Collect and related clients would need to cache this information probably using ETag headers.

The freeform message could be, "A retraining session is scheduled for the 2nd ... at the local market. Please remember to bring the mobile power banks". The idea here is to communicate with enumerators in the field who have downloaded a specific form. It could be updated instructions on how to appr…

That's a very interesting idea @Ukang_a_Dickson . But I feel like that would be a separate piece of functionality, that would need to take into account a lot of different issues (how to display the message, how to send the message on the server, how to designate the desired recipients for a message, …

ODK Forum

Notifications about form updates

Ideas

odk-collect, odk-aggregate

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled

Looking for a better way? Try ODK Cloud, the official managed hosting service from the creators of ODK.