tag:blogger.com,1999:blog-1527613590529958801.post7861190592224302519..comments2015-03-30T13:35:24.273-07:00Comments on Genealogy's Star: Dealing with the Deluge of Duplicates James Tannerhttps://plus.google.com/111292106004869462088noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1527613590529958801.post-13476225991892818112013-10-22T13:19:54.955-07:002013-10-22T13:19:54.955-07:00I know exactly what you mean. I had the same exper...I know exactly what you mean. I had the same experience two times this past week with similar merging issues. In both cases the patrons were so confused at the end that I could not explain what I had done. James Tannerhttp://www.blogger.com/profile/02989059644120454647noreply@blogger.comtag:blogger.com,1999:blog-1527613590529958801.post-38796426346668735702013-10-22T09:24:26.255-07:002013-10-22T09:24:26.255-07:00I had to smile at &quot;It makes me envy those who...I had to smile at &quot;It makes me envy those who live in a genealogical wilderness where there has been no research and they have an open field to discover and cultivate&quot; - a case of, &quot;Be careful what you wish for!&quot;<br /><br />I find merging in FS FT to be tricky. The issue is not merging individuals, as such, but &quot;merging&quot; their family details. A large percentage of the duplicates I&#39;ve tried to resolve so far, have been individuals automatically generated from baptisms in parish registers. I find, for example, baptism of child C to parents M and F, followed a couple of years later by baptism of child D to parents M2 and F2, where M2 is a similar name to M and F2 is a similar name to F. <br /><br />Let&#39;s say my previous research demonstrates these are the same couple. I can use FS FT to suggest duplicates and merge the details for F2 into F. As part of the same process, child D is moved over to have a father of F. The question is - what do you do with the mother, M2 during the merge of father F and F2?<br /><br />I have, for some time, always moved mother M2 over into father F&#39;s details as part of the process of merging F and F2. I did this because I feared that leaving M2 where she was, would delete her relationships and result in an M2 with absolutely no data other than her name. <br /><br />In just trying that option of leaving M2 where she is, I have discovered that, despite the merge screen appearing to &quot;orphan&quot; her from her spouse and children, she does actually go over to become &quot;married&quot; to F, with her child D. I have no idea whether this has always happened or not. <br /><br />BUT - and I&#39;ve only tried it the once - if I then try to find duplicates for M, it will NOT suggest M2, and I have to merge the two by record-key.<br /><br />Whereas if I explicitly send M2 to be a spouse for F, then when I try to find duplicates for M, it DOES suggest M2 as a duplicate. (And this is my usual way of working..)<br /><br />I can&#39;t quite visualise what&#39;s going on. Which worries me because if the recipe goes wrong, I won&#39;t have any idea what to do - apart from everything in turn.Adrian Brucenoreply@blogger.com