I urge everyone to look at their data conflicts.
Data conflicts seem to be dwarfing requested merges and tree conflicts across the tree. Data conflicts seem to be increasing, as requested merges and tree conflicts decrease.
Geni used to always take you to resolve conflicting data after a merge - but not any more. Now, in the race to merge, resolving conflicting data seems to be left behind.
A classic case of unresolved conflicting data happens when two profiles are merged. Say a person has Firstname Secondname Surname.
- In some cases, the profile has both Firstname and Secondname in the First Name, and blank Middle Name.
-In other cases, the profile has Firstname as the First Name, and Secondname in the Middle Name.
When they are merged, Geni takes "Firstname Secondname" as the First Name, and "Secondname" as the Middle Name, resulting in the person being called:
"Firstname Secondname Secondname Surname"
Resolving conflicting data would fix this.
Different people will have different views on priorities. But it does seem to me that resolving conflicting data is right now not getting the attention it might deserve.
Bjørn yes I understand that rationale, and I understand that is how we got to where we are now.
But the managers to whom you leave the data conflicts may not be doing their bit in the clean-up. That is why I say that resolving conflicting data is right now not getting the attention it might deserve.
Great minds think alike right David...lol