Import Married Names Unknown Dupe
Brought to you by:
canajun2eh,
yalnifj
For the following record
0 @I123456@ INDI
1 NAME Jane //
2 GIVN Jane
1 SEX F
who is married to
0 @I1234567@ INDI
1 NAME John//
2 GIVN John
1 SEX M
after import and selection of import married names the
record changes to:
1 NAME Jane //
2 GIVN Jane
2 _MARNM Jane /@N.N./
First of all, in this case we do not need the _MARNM at
all since it really adds no information and leads to
redundant indetical entries in the indi list. Secondly
why do we change it to /@N.N./ instead of //?
I assume but did not test that id Jane Smith married
John Smith a duplicatr record wil be entered as well,
and it really adds no value.
Logged In: YES
user_id=634811
Same issue with Jane /Doe/ marrying John //. It creates the
unnecesary Jane (unknown) in the indi list.
Logged In: YES
user_id=1061833
also, shouldn't the instructions not say "Import Married
Names" at all, but rather, "Add Married Names" ? If we
import an existing PGV managed GedCom file that already has
MARNM within it, the import uses the existing MARNM record
and adds it to the DB, but you might think, based on the
import wording, that the only way to include MARNM is to do
so at time of import.
-stephen
Logged In: YES
user_id=300048
Originator: NO
This is now fixed in the latest SVN (914). I have altered it so that // or /@N.N./ are not added.
--John