Birth Year "Inconsistency" logic refinement suggestion
A Birth year recorded as 1918 in one person record is not inconsistent with a complete birth date of 3 Nov 1917 in another person record.
A large number of duplicate person records created by the various "Census Projects" will exhibit this "inconsistency".
Suggested logic: If one of the birth dates in a merge is complete and the other shows only a year then a year difference of 1 year is NOT an inconsistency.
Comments
-
Yes, this is true and definitely needs addressing.
0 -
I have ran in to this same problem with birth years multiple times when merging. The above merge was not recommended. The warning only mentions the inconsistency of the birth years, which were likely estimated from census records. The birth place is exactly the same, yet the warning indicates they are 2505 miles apart. The children have the exact same parents. There is no warning regarding the spelling of the surnames, which would seem to be the greatest concern in this record.
0 -
@Soccer Mom Most places in Family Search use fuzzy matching and a database of name spelling variants when comparing names. We users, years and years ago, used to have access to the variant database for first names and last names and see how they were grouped. For example Thomas, Tomas, Tom, and every other way you could possibly spell these would be in one entry. Some of these groups were pretty lengthy. Gurelick and Gorelick certainly look like just minor spelling variant that would be considered the same name. You must agree or you would not be merging these two.
The Data Quality Checker is a bit more strict with names and tends to flag inconsistencies between a profile name and that name in a source where there is no inconsistency.
The data comparison routines for place names occasionally are pointing out errors in standardization or actual errors in the Places database. One easy way to check for these is to look at the timeline map because it is the standard linked to the place name that shows on the map. Looking at Golda https://www.familysearch.org/en/tree/person/timeline/L6H9-R1L you can see that her birth place of Minsk, Russia, is linked and plots on the map to the standard "Minsk, Krasnoyarsk, Russia, Soviet Union." (The Soviet Union was not created until 1922 so this is the wrong standard for her birth place.)
For Goldie https://www.familysearch.org/en/tree/person/details/L2X8-8PB whose birth place was also listed as Minsk, Russia, I had to temporarily restore her to see what the underlying linked standard. In this case, it is Minsk, Russian Empire which plots here:
These two cities are very far apart. You can avoid these types of errors by using the full place names and by double checking the linked standard by clicking on the place name to open the data view popup:
You should go to Golda's record and edit her birth place of Minsk, Russia, so there will be no ambiguity in where she was born. If you go to the places database and put in Minsk, Russia, you get 29 different places, only two of which are in Russia today:
You need to clarify which one you mean and link the correct standard to it. The Places database is not complete so sometimes you have to make due with the closest, rather than the correct, standard. It looks like there are no time periods for the Minsk that is in Russia prior to 1922 so the current linked standard, although not historically correct is the earliest one available for now.
0