Digitize your offline data collection. Create your Forms online with Tangerine Editor, conduct them offline with the Tangerine Android App. All results you collect can be exported as a CSV file, easy for processing in a spreadsheet. Tangerine has been used in over 1 million assessments and surveys in over 60 countries and in 100 languages.
When just starting out with a new group, all data being uploaded is test data and so it's easy to know which form responses to delete. However, when it comes time to update forms and you are releasing a test release or even doing final QA on the live release, these test responses are being uploaded often at the same time actual Assessors are uploading. At that point it is very hard to tell the difference between test data and actual data.
Potential solutions:
Show the tablet "username" in the list of form responses in Editor. Implementing team then makes a convention that anyone testing uses a "test" username or that the person removing test responses knows of the actual user names that testing in cases where you want to test an actual device's existing account. This option is low level of effort, but if not managed carefully will result in test data not being deleted.
We allow an Editor user to define a template of what to show in the responses list, then any field in the profile could be used. This has the same issues of the first option but would not result in exposing the unreliable usernames as a sort of "ID" that may be mistaken as something that is enforced as unique.
A setting on a tablet to go into "Test Mode". This would result in all form responses being marked under the hood as "test": true. Then in the editor, we could show which form responses are marked as test responses and also have a button for "delete all test responses". This scenario is one where it's more likely all test data would get cleaned up, unless someone generating test data forgets to put their tablet into "Test Mode". The tricky part may be, where to put this setting on the client? Exposing this setting to all users may result in some of them enabling this and not realizing all of their data is going to be deleted.
When just starting out with a new group, all data being uploaded is test data and so it's easy to know which form responses to delete. However, when it comes time to update forms and you are releasing a test release or even doing final QA on the live release, these test responses are being uploaded often at the same time actual Assessors are uploading. At that point it is very hard to tell the difference between test data and actual data.
Potential solutions:
"test": true
. Then in the editor, we could show which form responses are marked as test responses and also have a button for "delete all test responses". This scenario is one where it's more likely all test data would get cleaned up, unless someone generating test data forgets to put their tablet into "Test Mode". The tricky part may be, where to put this setting on the client? Exposing this setting to all users may result in some of them enabling this and not realizing all of their data is going to be deleted.