GEDCOM data confused on import [#331459]

When importing an abbreviated GEDCOM file (exported from Legacy 7.0, format Gedcom 5.5 "generic"; see attachment), some of the individuals' information is confused.

For example, if you look at the Individual entry for Adam Browne (me), you'll see:
- birth date is missing
- birth place is incorrect
- mother's name is given as father
- father's name is omitted altogether

If you look at the Groups index in general, you'll see:
- a lot of "Error!" messages
- couples entered twice
- one person entered as a couple, using the given and surnames

Comment	File	Size	Author
#1	import.inc_.txt	13.7 KB	Microbe
	Browne_20081107b.ged_.txt	6.57 KB	adam_b

Comments

Comment #1

Microbe commented 7 November 2008 at 18:17

Status	File	Size
new	import.inc_.txt	13.7 KB

- birth date is missing
- birth place is incorrect

This is caused because it carries on looking for information about the birth until it finds another entry type it recognises. Hence if there is a date or place between the birth data and and the death data (usually the next data type to be recognised) then it will use that for the birth. Alot of you people have christening dates after your birth date and so that was being entered instead. I have changed this to ignore unrecognised types. This also effected death dates and places

- a lot of "Error!" messages
- couples entered twice

This is caused by group nodes arn't being being deleted properly. I have looked at this but have no idea why it isn't working. Try using something like the delete_all module.

mother and fathers name might also be fixed by this patch but it is more likely to be the same problem as one person being entered as a couple. i am looking into this problem and hopefully will come up with solution shortly.

Peter