Last name at birth is not necessarily the last name people are known by . . .
commented 5 hours ago by Nancy Whyte
.
This is why we have the LNAB and the Current Last Name fields.
My great grandfather changed his name for whatever reason/s he had in his head. When I created his profile I did so using the CLN, because that was what was known. He had stated that he was born in Liverpool, England. He gave his parents' names. So this information went on his profile. Some while ago I discovered none of that was true.
So he got a name change. His LNAB is now correct . . and that is what now shows on the tree. His CLN is still there, because that was the name by which he was known. Having his LNAB being accurate helped me find the rest of his family (now goes back some 200-plus years, even f I have not yet added them all in), because someone else saw my update on the matter, jumped in and started adding information I had no idea how to find. (Wave to Eva!) With only his CLN being shown, I would not have his parents, his grandparents, or any of those other generations going back to the 1600s.
I have no problem with his LNAB showing (correctly) on the tree view. If someone wants to know why that name is there, not the one by which he was known, they only need to click to view the profile. On so doing, they will see both LNAB and CLN displayed: Ola Halley (Ole) Williamson formerly Waldemarsson.
Wikitree works on accuracy, so as signatories to the Honor Code it behooves us to be as accurate as we know to be. (And, yes, I said behooves.)
.
.
@ Stu — adoptions are a different case. There are ways to deal with those, which is why Wikitree has the Adoption Angels.