Thank you Lee - I thought as much! I reckon I will simply have to follow your lead, note the ID#s, work on them in normal fashion, and then revisit the CFDP - and do that several times over. Ah well... Tom On 15/12/2017 14:49, Lee Hoffman/KY wrote: > At 12/15/2017 07:52, Tom Coughlan wrote >> I suspect the answer is in the negative but am wondering if there is >> any way to send the output of the Duplicate Persons check to a report >> or file? And if so, is it possible to only output those suspected >> matches that I have not already 'asserted' are not duplicates? > > You are correct, there is not a way to send the Check for Duplicate > People (CFDP) to print or to file. I have wished for the feature also. > > You can mark pairs as excluded which can help some, and then those > excluded pairs can be shown or not shown. I have never found this to > be particularly useful unless the number of resulting pairs is on the > small side (a few dozen or less). Even then, I will often record the > ID#s of the pairs and work with them outside the CFDP function. This > loses some of the features of the CFDP, so I may do some checking > outside the CFDP and then re-run it to take advantage of those features. > > Lee > > The TMG archive is found here: > http://archiver.rootsweb.ancestry.com/th/index/TMG/ > Instructions on how to subscribe to TMG: > http://lists.rootsweb.ancestry.com/index/other/Software/TMG.html > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message >
Tom Coughlan wondered: > ... is it possible to only output those suspected matches > that I have not already 'asserted' are not duplicates? As Lee mentioned this is unfortunately a manual operation. While you are going through this exercise you may wish to consider defining a couple of custom TMG tag types to help record your "assertions" for later review. As described in my book: http://www.mjh-nm.net/TAGCUSTM.HTML#DuplicateTag I define two tag types: Duplicate and DupNil. I use "Duplicate" to set as Principals the two people I still "suspect" may be duplicates along with my reasoning of why I am still unsure and choose to keep separate. Then the "DupNil" sets as Principals two people who "look" like they could be duplicates, along with my reasoning of why I assert that they are not. Both tags alert me to be careful when I encounter and am about to enter new data for any such Principals to double check "which" person should get this new data or if it resolves whether they are duplicates. Since they are separate tag types I also can selectively choose whether to include these "duplicate" reasonings in reports. Hope this gives you ideas, Michael