|
Hi, My team is developing a survey used by several tablets in cycles. We want to have the previous cycle's data available on the survey for only certain attributes, in order to inform our data collection crews' while not introducing bias with access to the full data set. For example, we want crews to see if a tree was previously alive or dead, but not it's previous height. This prevents error propagation across cycles and maintains objectivity. We've considered two approaches: 1) Data cloning- While we can select attributes for cloning, two issues arise: First, old data prepopulates fields which is prone to error as it requires deletion before entering new values. Second, cloned data includes all trees, not just those monitored by a specific tablet which will cause trouble when merging at the end of that cycle (as there are multiple tablets working at once, and work is dynamic, we cannot use the exact same tablets for the same trees every cycle, and have to clone fully merged datasets). 2) Data linking- This improved access to previous data without prepopulation. But, linking consumes a lot of interface space with previous-cycle dropdowns for every attribute (even when it is a key attribute or an extra property- which won't change between cycles anyway). And, it still risks introducing bias in data collection. Therefore, we wanted to ask whether there can be an option "included in linked data" for attributes? that would serve as space efficient, selective, and error-resistant method for accessing previous data. Apologies for the long question, and thank you very much! |
|
Dear User, |
