XPost: soc.genealogy
In message <
7vkq0jd4l2ne31naq1pp4cp7fislh82ucn@4ax.com> at Wed, 3 Apr
2024 15:08:21, Steve Hayes <
hayesstw@telkomsa.net> writes
[]
On 02/03/2024 10:37, J. P. Gilliver wrote:
[]
But often, in particular where I'm examining a suggested duplicate to
see if the suggested person is really the same as the person I'm looking >>> at, it shows me when both people were "Added" - presumably to their
master tree. And it's nearly always 2012 - often 1 or 2 May 2012.
Was there some sort of mass glom - of people - at/by them that year?
I suspect it might be related to the merging of the LDS/IGI databases
and database restructuring in 2011/12
Yes, they merged various sources, and there are lots of duplicates.
For example, they merged databases of baptism record transcriptions,
and if a couple had five children in a particular parish, there will
be five records relating to the same father, and a sixth for his own
baptism, and seventh for his marriage. Just make very sure before
Yes, they could do with a couple merge function. I often find, say, Fred
and Jane with a given marriage date and location (and often a child with
a given birth date and location), and it suggests another Fred and
another Jane with the same marriage date (and often a matching child). I
then merge the two Freds, but then have to go through the process of
merging the two Janes. (And the childs [I say that rather than children
as it's usually one person].)
merging them that they really are the same person and don't relate to
his first cousin who had the same name and the same grandparents.
I don't usually look as far back as grandparents. But yes, one must be
pretty sure before merging.
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
It's quickly getting to a place where privacy will be cause for suspicion.
- Mayayana in alt.windows7.general, 2018-11-6.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)