Currently, the import of a GED file into Family produces a problem of some of the nodes displaying the wrong order of parent 2 before parent 1, when the reverse should be true.

This may have to do with the way the module handles duplicate or alternate name data, I'm not sure. I have also seen how the import produces an incorrect prioritization of alternate name for a person, like for a married name for example, which seems to throw off the module. This seems like an important bug to address since GED files often have extra information attached to people. Genealogy programs can generally handle these discrepancies as a lot of additional information can and should be attached to a person.

Comments

edfaught’s picture

edfaught commented

Were you using the patch at http://drupal.org/node/405170 ? Would you be willing to supply an example gedcom file?

michael.k’s picture

michael.k commented

I had not applied your patch since it didn't appear to address my specific issues, and given your caution in comment #7. But there was obviously a more important "fairly large change to the import.inc file" that I neglected to consider, so I apologize for the oversight.

Now I'm happy to report that after installing the patch at http://drupal.org/node/405170#comment-3303770, many of my issues are resolved!

Unfortunately, there are still issues that remain with GED import (like incorrectly sourcing the alternate name for an individual), but your patch is definitely a huge improvement.

Regarding whether to provide a GED file, yes I could email you a download url, let me know. I'm testing with two GED files, one with about 5500 nodes (1.6 MB), the other with about 1200 (300 KB) that I'm merging into the database.

Many thanks edfaught.