Using Advanced Search to Identify Duplicated Facts

Hi Folks
Some assitance please, I can remember tidying up my RM9 database late last year and am sure I was able to use the advanced search feature to identify duplicated facts i.e. when a person had 2 Birth or Death entrys, which I could then delete the ones that were either wrong or redundant duplicates

I must be getting old, but max effort has yielded no result, I just can’t find out exactly how I did it.

Guidance much appreciated

Peter

Tools > Add or modify fact types > Print > List Type > People w/ more than 1

1 Like

I’m not aware of any way to do it with Advanced Search. The way I know how to do it is in the Fact List.

In the Fact List, select your fact and click the Report button. Then choose the option that says People w/ more than 1: You can only process one fact type at a time.

This will be a static report that you can print or save as a file. As such, it will satisfy your need. But it will not be an active list that you can work with live as you can with results from an Advanced Search. Advanced Search already has an option that allows you to test whether a fact exists or not. This allows you to determine if the number of occurrences is 0 or more than 0. It would be nice if there was an option that would allow you to specify an actual number of occurrences such as you can do with Number of Spouses or Number of Sets of Parents. That way, you could work your list of duplicated facts from a live list of people instead of from a static report.

The Fact List can be a little hard to find, but there are multiple ways to find it. For example, you can find it from the Command Palette and you can also find it from the 3 Dots icon in the upper right hand corner of any person screen. There will be two 3 Dots icons, one above the other. It will be the one on the bottom.

fact_list

2 Likes

Thanks so much

Peter

Thanks very much problem solved

Hi,
I have a simular problem.

After many GEDCOM imports (My Heritage) and Familysearch I have many, many duplicate facts in places, events, birth, marriage etc.

How can I merge this facts or delete the duplicates in one time?

many thanks

Thomas

The Fact List report with List Type: People w/more than 1: can help you identify who has duplicate facts. You will need to manually delete them one at a time.

In the future cleaning up the Place List will help keep duplicate facts at a minimum. If two facts use different places in the Place list, even if identical, it will consider them separate facts and save both. Same thing happens with sources/citations and media, though they don’t create duplicate facts.

I have cleaned up places

But the duplicate facts persists anymore

Can I mark more then one facts to delete them manually?

No. They must be deleted one at a time.

I think the idea of cleaning up the place list helping with this problem is related to merging duplicate people. When doing merges, information that is identical between the two people will not be duplicated and information that is not identical will be duplicated. That’s why it is helpful to do various cleanup operations before the merges. But cleaning your place list after the merges doesn’t help with the cleanup of the facts.

I have tried this;
but the duplicate facts remain in the merged primary person

the problem is, that this persons are duplicate in Gedcom-Export

what can I do?

Once the duplicates facts are on a person you have to manually remove them. Merging won’t fix that. You can only prevent it from happen initially.

Facts that are absolutely identical will be merged when the person is merged.

Facts that are not absolutely identical will not be merged when the person is merged. No data is lost and both facts will remain.

The manual merge process is designed so that you can edit the person immediately after the merge and before leaving the merge screen. The concept is that RM has no way of knowing what data to keep and what data not to keep when the duplicate facts are not absolutely identical. Only you as the user can make that decision. Therefore, you as the user edit the person to make one of the facts include all the needed data and to delete the other fact. I think this is an excellent design.

By contrast, the merge process on FamilySearch makes decisions about what to keep and what not to keep. Data can be and often is lost during a merge. I think that is a terrible design. It drives me crazy when I’m doing merges in FamilySearch.

When doing the merges in RM, it can be tempting to do a bunch of merges very quickly and then to go back and cleanup the duplicate facts afterwards. Experience suggests that this is a poor strategy and that it’s wiser to clean up each person immediately after the merge and before leaving the merge screen.

many thanks for helping..

is it possible, to create a fact-rule for
a) number of childs
b) number of spouses
c) number of parents
and so on ?

I don’t believe so.
The secret to solving this is:

To start by importing to a SMALLER dedicated WORK database, do all the merging of placenames, sources, DataClean, Problem Search, given and surname spelling variations, then auto merging people followed by manual merging suspected duplicates before then finally dragNdrop/GEDimport to MASTER database.

my Problem ist, that this duplicates an in FamilySearch after multible s GedCOM-imports
so I search ways to identify this dups in RM

one way ist to look for more then one pair of parents scrolling the person list

after this I do this in FS-Browser ond check the in “share-data” for the same problem,
this is very slowly because RM need up to 3 minutes to display this data

Normalizing the data FIRST after each single import is less difficult than compounding the conflicts of multiple imports at once.

1 Like

thats right
but it takes long time until i realisied the in FS

to late
therefore I use RM, to correct this problem
so I am looking for powerfull tools in RM
is it really not possible to create counting-facts?

AND if you import, normalize, and then move people from WORK database to MASTER after EACH import, duplicates are less of an issue at any one editing session.

good Idea !! -)

other question:

is it possible to fill the birth-field with christening-field if empty by rule?