Merging records

There ought to be a "merge" tab on each record. If you recognize there are two different names, or the same name but is the same person, why not have a tab at the top that you can click on the link which will bring up the current person, and then ask you for the other person's ID number to merge. I've run across several records which are duplicates which shows married to the same person, but they are duplicates.
Comments
-
Under "Tools" there is a function called "Merge By ID" that does that.
2 -
@HVJ64 by "record" do you mean a profile in Family Tree, or do you mean source (historical record)?
1 -
Profile in Family Tree.
Additional question. . . .how can we get the attention of Family Search to make a system-wide correction on a location? There is a significant number of records in Stokes County, NC which identifies the location as "Stokes, Pitt, North Carolina, USA", but this is in error. While it may be a legitimate code for Pitt County, NC, it has messed up huge number of records in Stokes County, NC. I've tried to correct as many as I can, but am not going to help FamilySearch much longer if they don't correct this obvious error. I live near Stokes County, NC and there is NO record for people who were born, died, or were married in "Stokes, Pitt, North Carolina, USA". The correct location is "Stokes, North Carolina, USA", or a prefix before Stokes which may identify the specific town names or names of townships.
0 -
This sounds like one of the many auto-standardization errors that were introduced last year. There are some long posts that go into this extensively but I'll just say here that the FamilySearch ran a routine to improve place names in the historical records that worked fine maybe 99% of the time. But when you are talking about billions of records, even a 1% error rate is huge. You can recognize these errors because the records involved will have two event places. The second of the two used to be labeled Original and is the base place name originally set for the indexed batch and is usually just fine. The first listed is the auto-standardized version that has the error. Because the event place is the same for the entire indexed batch, the error will be the same on all of them also.
If you post a specific example of one of the records you are seeing this problem with which you have not corrected in the Search category here in Community under FamilySearch Help, the right people will see it and send it off to the engineers to add to the list of corrections. We've been told it may take a long time to fix them.
Here is an example of one I posted a couple of days ago: https://community.familysearch.org/en/discussion/138713/auto-standardization-error-fjelberg-parish#latest
Do report this in an original post with a clear title.
The trouble usually arrises when the place name was incomplete and the auto-standardization misinterpreted the level of the place name. There is a Stokes in Pitt county:
So the error was that the routine took Stokes as the city name rather than the county name in the records you are seeing.
0 -
Where do I find "tools" for merge 2 duplicate persons?
0 -
@Hunt Cynthia2, the Merge By ID tool is in the Tools box at the bottom of the right-hand column of a profile's Details page.
0