Because I combines all my GEDCOM files in to a single database I have a scary number of duplication. Im working through them but it is slow going. Is there any way I can batch identify 100% duplicate facts under a single person and under a single category? Rather than have to delete them one at a time. Below all items without ID’s need to be deleted as I have their equivilents in my records. This is a small example I have some that are 20+ items long.
2 Likes
No way to batch it. It’s one at a time.
1 Like
I am guessing that you probably have a number of duplicate individuals as well as duplicate facts for many of your individuals. I am thinking that if you think these files are worth combining, the easiest approach might be to go back to an earlier point in time.
You likely have the originals of at least some of the files you combined. It might be wise to evaluate these gedcom files before combining anything. Then perhaps you could combine two or three that appear to have information you find promising. First, try to merge duplicate individuals, and only then attempt to merge duplicate facts.
When I take information from a database not my own, I only add new persons and/or families one at a time to my primary database and then look at each edit screen for duplicates I may have added. Depending on the number of people and duplicated facts you have in your combined database, it might be better to start over.
1 Like
Yes I can start all over with one Gedcom file at a time. But I’ll loose all the work I’ve already done. LOL. So its professor plod here and one at a time me thinks. It would be nice to have a checkbox next to each duplicate in the person list and have those get merged or deleated automaticaly. Ged format files just dont lend themselves to database management tools outside of the applications.
Thanks
Peter
1 Like
To cut down on duplicate facts make sure the Place list is cleaned prior to merging. I usually clean the Addresses & Repositories, Place list and then Sources/Citations in that order before merging. Though in your example it looks like the description fields are different and there isn’t a way to prevent that.
1 Like
Duplicates are a pain point for me. Every time I do anything at all in my tree duplicates are introduced and I still fail to see where from. Then as you say, each one must be dealt with separately. It’s a massive pain.
That’s when I go to treeshare with ancestry, not to sync but it’s easier to clean up from that view