From: Michael L. <mic...@ca...> - 2006-04-02 00:52:13
|
On Saturday 01 April 2006 20:56, nathan bullock wrote: > > - I imported two different Gedcom files which have a little bit of > overlap. It just imported them both and didn't complain about > duplicates. Is this normal? The duplicates had exact same name, > birthdate, and deathdate. > This is normal behaviour for gramps. It seems that some other genie apps do try to handle imports more intelligently. I recently sent a large GEDCOM to a distant relative who uses one of the many PC programs and he reported that it imported OK and merged OK with his data. I had the impression from his email that it used some sort of intelligence to do that, or at least prompted for the clashes. Perhaps we should think of the best may to handle this. I would suggest that we could set merge parameters similar to the parameters that we use to spot possible duplicates. If the records are identical (but what is identical?) then import without prompting, else prompt for a merge of events, families, etc. I'm not all that familiar with the way GEDCOMs store events and such so that may be more difficult than it seems. > - Merging duplicates. After these imports I went through and merged a > number of duplicates. I noticed that there were also duplicate family > ids. For example F14 and F205 are the same family. How do I merge > duplicate family ids? Especially once all the people in F205 have been > merged and as a result no one seems to point to F205 anymore. > If you run the database check and repair utility it will remove empty families (I think). -- ================================== Michael Lightfoot mic...@ca... http://www.tip.net.au/~michal ================================== |