Inconsistencies from typical census record differences.
My first test of this feature was a profile of a child created from a single census record that needed to be merged into a profile based on several sources. All the inconsistencies were typical issues with census records such as estimated birth year vs full birth, nickname for a toddler, a different (but typical) first name for a father, a different last name for the mother, etc. The list of inconsistencies was daunting at first glance and I wondered what the impact would be for a less experienced user. Would this just scare them away? And, I wondered if all this "clutter" of notices would cause a user who has seen "all this" before to just skip over the list and miss a real issue. I am not sure if I have a recommendation at this point but, I wanted to highlight the possible issues.
Comments
-
@GBHammer great observation. The hope behind the notices and warnings is to prevent a bad merge. But finding that sweet spot is always a challenge. Thanks again :)
0 -
Understood. Is there a way to reduce the clutter in the visual presentation? Perhaps with pop-ups for details. Also, perhaps rate the criticality of the issues? In the above example, the estimated birth year vs the detail year is just a common census record minor FYI.
0
