How can I remove a person/link that is currently attached to my family tree?
My 2nd Great Paternal Grandfather and the preceding tree elements are all wrong. I cannot figure out how to remove or edit the tree link. The incorrect person has only one source and it is a Marriage record. This person lived in the same state and that is all. The person that made the change is not named and the only message is this: Change made by authorized support staff or as part of an update.
It appears that this persons ancestors fit into his profile; however, hi information does not belong in mine.
Last good data: James A. Denton, 1852-1895 GMXA-XJ9. The incorrect person is: Alexander Blair Denton 1817-1860 KZ2D-LQC. The person that should be in that spot is: John Denton, 1815-1885. Born AL; Died Village Township, Jackson County, AR' Spouse Julia A. Denton
Thanks for any assistance.
David
Answers
-
In James A. Denton, 1852-1895 GMXA-XJ9 Recent Changes/Change Log - the change adding Alexander Blair Denton 1817-1860 KZ2D-LQC as father and Luiza Barger 1817-Deceased M49X-YM7occurred 6 Oct 2022 by FamilySearch username Mary2,353.
There are a few ways to proceed Non-collaboratively or collaboratively:
1. Compile your research in a 3rd party tree management solution with FamilySearch sync capability and once you have the profile complete - sync changes to Family Tree.
2. To undo this change you would detach James A. Denton, 1852-1895 GMXA-XJ9 as a child of both. There is a Help Center article about editing parent-child relationships that would be good to refer to (sorry I am on a phone and editing posts is not easy - someone else can refer to the Help Center article link). When editing the relation give your reason statement (does the family bible you referenced list other parents?).
3. You could contact user Mary2,353 and ask her to share her evidence of the parentage relation (there doesn't appear to be any attached).
4. You could start a Discussion on the collaborate tab for James' profile questioning the current parentage and giving reason for different.
You could do any combination of these.
Side-note about Idea: if the Idea of personal tree contextual login were available - none of this would bother 'your tree'. You would continue to work in 'your tree' and your collaborative acceptance/rejection of profiles would be communicated to Family Tree (the one world, one profile - unless conflated/duplicated - shared Tree which anyone can contribute to - i.e. the current Tree platform).
0 -
To correct the error, just click on the pencil "edit relationship" icon next to James in the Family Members section:
Use the Remove or Replace link in the Child section to remove James from the family:
Be sure to document why you are doing this. I see that James is also currently listed with a second pair of parents that you say are the correct ones. Add all the sources you can to support this.
(Sorry about the too large images. Resizing them is not working for me today for some reason.)
If you are particularly ambitious and want to prevent this particular error from occurring again, you could do some research on Alexander and Luiza's family. There is a five year gap between their children Nancy and Martha. Maybe that other user does have some information that shows they did have a son James born in that gap and accidentally put your James there. If you can find that they did have a son James and get that James correctly added to the family with good dates and sources, then no one will ever confuse him with your James again. Asking Mary2,353 what she knows about the family may be helpful in this.
0 -
... then no one will ever confuse him with your James again.
This is not necessarily the case and the risk that James could be confused again at some point continues - because the attachment and pending removal remain in Change Log. And who knows how Record Hints views that...
0 -
There is absolutely no reason for the Hint engine to look at the Change Log since only the current information would have any value in evaluating a record hint. That is why we correct information, to move incorrect information to the Change Log with a full reason and explanation why it should never be put back in the record so that the Hints engine will never use it.
As records for both of these families get fully documented and all correct sources attached where they should be, the risk of confusion will just drop further and further. Both my wife's relatives and my relatives are thoroughly documented in Family Tree and I find their profiles to be remarkably stable while they are being continually improved by others adding additional sources and memories.
1 -
There is absolutely no reason for the Hint engine to look at the Change Log since only the current information would have any value in evaluating a record hint.
Hopefully so - it would be nice if detach from one profile would suspend it from others involved - but until all profiles involved are detached an overactive Record Hinting engine could re-suggest a detached Source. This was the topic of a post a while ago.
As records for both of these families get fully documented and all correct sources attached where they should be, the risk of confusion will just drop further and further.
Again hopefully so - but the open-edit risk still remains.
0
