What is the general goal of the feature? To be able to track if changes have been made in fields during data collection Realistically only once the user has moved on to the next question; i.e I complete Age = 20 I move forward to Gender = Male I go back to Age and change to 19 Some record is g…

This feature shipped in Collect v1.22 and the docs are at https://docs.opendatakit.org/form-audit-log/#change-tracking .

@LN Yes I agree this would be a configurable option (?set within the XLSForm as part of including the audit line so that the form designer has control over this?) 1a) Could the log be encrypted? We do this with our clinical datasets now because of these issues and also GDPR regulations within the…

@LN @yanokwa @chrissyhroberts & I would be interested in getting a sense of a ballpark figure for doing either A) Minimum or B) Ideal implementations of this as above. We have some potential money but I am bad at guaging the cost of this kind of thing

@LN @yanokwa We have money in a grant which we would be interested in putting towards this. Do yuo think we could get a cost estimate for the work? @chrissyhroberts

So looks as if we need a new column in aduit.csv file, currently we have: event, node, start, end or event, node, start, end, latitude, longitude, accuracy if location tracking is enabled. a new column could be named just answer We would need to fill that column only in case of questions. Ques…

Hi all! Seeing that this thread is coming to life again, I just wanted to point out that the TSC is discussing this feature at https://github.com/opendatakit/roadmap/issues/30 . There are two ongoing topics, in different degrees of consideration: Remember the answer to a question from the last sa…

I think it's not the same @ggalmazor this is not about any auto-filling/preloading. The user who asks about the feature just needs the history of changes.

Correct - this is an audit trail of changes not auto population.

I understand. Thanks for the clarification! :slight_smile:

@Grzesiek2010 , @LN and I have been iterating on this feature and we've made good progress! The key design decisions we've made so far are: The feature can be enabled/disabled through changes to form design Likely an attribute in the form called odk:audit-track-changes (or something similar) which…

Only event, node and that new value columns should be filled right in that new event? I don't think it makes sense to record time since it wouldn't be the time of answering a question but the time of navigating.

ODK Forum

Collect: keep history of changes to values in the form

Ideas

ggalmazor February 1, 2019, 9:07am 18

I understand. Thanks for the clarification!