You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm doing fieldwork now in Ghana and we're finding that enumerators
are accidentally deleting blank forms when they intend to delete
instances of data collection.
For the short-term, we will probably just try to quickly re-train them
to avoid this. But I have two design suggestions.
In the short-to-medium term, I would recommend adding a check box,
hidden under "change settings" that says something like "Protect Blank
Forms From Deletion". It's easier as a trainer to prevent staff from
messing with the "settings" than it is to stop them from trying to
delete data instances that they've collected and want to delete.
But in the longer term, I think this is a bit of an interface design
problem with ODK Collect. When looking at the two tabs visible after
clicking: "Delete Saved Forms" it can be confusing which of the two
tabs is actually active (in bright sun, the black and white tab has
higher contrast, and looks active, when in fact it's the dark-gray on
lighter gray that is active). I've come close to accidentally
deleting blank forms myself...
Reported by yanokwa on 2012-02-11 15:30:33
The text was updated successfully, but these errors were encountered:
How about changing 'get blank forms' to 'manage blank forms' with 2 tabs, one to get
new/updated forms from the server, the other to delete the blank forms on the device.
Then 'delete saved forms' could then be just for deleting 'bad' user data.
Reported by peter@rmrkz.com on 2012-03-14 11:34:46
Migrated to getodk/collect#62 by spacetelescope/github-issues-import
Originally reported on Google Code with ID 514
Reported by
yanokwa
on 2012-02-11 15:30:33The text was updated successfully, but these errors were encountered: