Hard to do a question (of any detail/magnitude) in 120 characters, so shorthand is necessary.
Question:What is a resolution for two branches of a tree who seem to want /need lines indexed separately (have different spelling variations, thus different branches/generations), but are connected to one root ancestor with dual/differing/conflicting names -- due to new conflicts/perhaps substantiated or unsubstantiated findings of historical data.?
Can both the branches be indexed in separate lines/databases, under each different root ancestor? It would seem the only resolution, and has been suggested here. This issue seems to be a database and coding resolution, and a merge does not resolve the conflict.
Changing a family ancestor is tricky, and people don't like their branches broken off going another direction, with another ancestor's name created primarily for merges, to control the whole family, to help a website, especially when they don't agree with the new ancestor name that does not follow history completely.
Any resolution/suggestion on the tech database side to this? Thanks.