-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Add support for background locations in audit #219
Comments
Other than putting on my tinfoil hat, nothing from me... ;-) |
Looks great to me! |
Unfortunately, I'm WAAAAY too late to the #94 party, so I'll have to defer to y'alls expertise that this In regards to actual naming, I'm easy; so long at all the required parameters are defined. And as @MartijnR said, I've got far more pressing things to catch up on (repeat groups!) before I can even start to worry about background audits, sigh. |
I am not seeing this (and other audit) feature getting into Enketo due to the difficulties in mimicking the same events in web clients, coupled with the lack of demand so far, but if that is resolved and changes, these attribute names make sense. They are prefixed with |
In the XForms spec audit is placed in the meta block under the orx namespace. It uses a binary data type. See opendatakit/xforms-spec#94
I propose we add the following bind attributes in the odk namespace to the specification. All three attributes are required to enable location audits and location-age must be greater than or equal to location-interval.
We have an implementation for Collect at getodk/collect#2772
The text was updated successfully, but these errors were encountered: