Family Search added a duplicate new person.
Go to the record for Henry Hill Male 13 June 1932 – 2 November 2017 •GPCW-LDY. You will see that the record has been deleted by a merge. But when you look at the detail page for this person, and then look at his Latest Changes, and click SHOW ALL, you will see that a new person was added to the data base, 31 Jan 2024, by FamilySearch. Under what conditions would this happen? When a new person is created, there is usually a test for Possible Duplicates, and especially when the new person is added by FamilySearch.
Now, when you look at the Latest Changes for the merged person, and click SHOW ALL, you see the merge done on 4 Feb, but you do not see any indication that a new person was added to the data base, 31 Jan 2024, by FamilySearch. When a merge is done, the Latest Changes for one of the parties to the merge apparently gets lost. Is there possibly a Knowledge Article that might explain how Latest Changes works with a merge?
Answers
-
Often, when I see that particular notice
it is on a profile that has suffered abuse at the hands of a contributor. I won't say the issue has always been malicious, but it often has been. FS Staff then has to clean up some of the problems.
0 -
@jlwestra said: "Now, when you look at the Latest Changes for the merged person, and click SHOW ALL, you see the merge done on 4 Feb, but you do not see any indication that a new person was added to the data base, 31 Jan 2024, by FamilySearch. When a merge is done, the Latest Changes for one of the parties to the merge apparently gets lost."
Nothing is lost, but you need to look in the right place. In any merge, there is a surviving person and a deleted person. The deleted person is not truly deleted, but is still available for you to see their change log, as you clearly have done in this case. The surviving person's change log contains everything it had prior to the merge, as well as entries related to the merge. Specifically, there will always be an entry for the merge itself, which includes the reason for the merge and most importantly (for this question) a link to the deleted person. The deleted person's change log contains everything about that person, up to and including the merge.
You seem to be hoping that the entire change history for every person merged into the surviving person would get incorporated into the change history of the surviving person. That seems like it would be very unwieldy and confusing. If that were the case, when you are looking at an entry in the change history, you would have no idea whether it was done to the surviving person or one of the persons merged into that person, and the change history would be dramatically longer in many cases. I much prefer the current system where changes are kept with the person the changes were made to; I can use the links to persons deleted in the merge anytime I want to see changes that were made to those persons.
2
