I have a sub-tree GEDCOM provided by a cousin with a missing branch. No overlaps. It seems that I can either ask politely for Stephen to merge the files :) or I can manually merge the two after I check for conflicts (which shouldn't exist; the INDI numbers are totally different). If I manually merge the two, I think I would delete the top person (who is in my tree) and change references to his INDI to reflect the existing INDI that I have for him. There's only one sibling so the FAM shouldn't be hard to straighten out. I will probably just ask Stephen though!
The new branch was made in MacFamilyTree from syniumsoftware.com. There are a few issues:
1) The "NAME First/Last/" line doesn't have a space before the /Last/ and therefore the two names run together in the display. I think I can fix that, since nearly everyone has the same last name.
2) The new GEDCOM has CREA and CHAN tags that are showing as errors. For instance:
0000016 1 BIRT
0000017 2 DATE 24 DEC 1874
0000018[] invalid tag ; see INDI @I69653614@
0000019[] invalid tag ; see INDI @I69653614@
0000020[] invalid tag ; see INDI @I69653614@
0000021[] invalid tag ; see INDI @I69653614@
0000022[] invalid tag ; see INDI @I69653614@
0000023[] invalid tag ; see INDI @I69653614@
What is the best way to deal with this?
I uploaded the new GEDCOM to my site, and it can be switched to so you can see the errors in the INDIs: http://www.largiader.com/family/index.php
Largiader - main GEDCOM
Maini - new branch that will connect to my I207 (one of the oldest). Dates on the earliest INDIs are missing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd be tempted to just use a smart text editor on (a copy of) your cousin's gedcom to delete the bad records, then manually combine that with a (copy of) an exported gedcom, then reimport this. I've never tried exactly this, but when I was starting out with genealogy software I did similar things.
Or just hand enter them if there's only, say, a few dozen.
Someone else may have recent experience with other software that may help.
/George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are 87 INDIs. Most have some other data attached (OCCU, RESI, etc. I used Notepad++ to strip out the CHAN and CREA parts, and will try just appending o my existing GEDCOM and re-importing. It has other problems also; things that should be in PLACes are in DATEs and there's a DATE ? line for a death here and there. It wasn't made with an eye toward data integrity; it was made to be a printout at an upcoming reunion.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a sub-tree GEDCOM provided by a cousin with a missing branch. No overlaps. It seems that I can either ask politely for Stephen to merge the files :) or I can manually merge the two after I check for conflicts (which shouldn't exist; the INDI numbers are totally different). If I manually merge the two, I think I would delete the top person (who is in my tree) and change references to his INDI to reflect the existing INDI that I have for him. There's only one sibling so the FAM shouldn't be hard to straighten out. I will probably just ask Stephen though!
The new branch was made in MacFamilyTree from syniumsoftware.com. There are a few issues:
1) The "NAME First/Last/" line doesn't have a space before the /Last/ and therefore the two names run together in the display. I think I can fix that, since nearly everyone has the same last name.
2) The new GEDCOM has CREA and CHAN tags that are showing as errors. For instance:
0000016 1 BIRT
0000017 2 DATE 24 DEC 1874
0000018[] invalid tag ; see INDI @I69653614@
0000019[] invalid tag ; see INDI @I69653614@
0000020[] invalid tag ; see INDI @I69653614@
0000021[] invalid tag ; see INDI @I69653614@
0000022[] invalid tag ; see INDI @I69653614@
0000023[] invalid tag ; see INDI @I69653614@
What is the best way to deal with this?
I uploaded the new GEDCOM to my site, and it can be switched to so you can see the errors in the INDIs:
http://www.largiader.com/family/index.php
Largiader - main GEDCOM
Maini - new branch that will connect to my I207 (one of the oldest). Dates on the earliest INDIs are missing.
How big is the new gedcom?
I'd be tempted to just use a smart text editor on (a copy of) your cousin's gedcom to delete the bad records, then manually combine that with a (copy of) an exported gedcom, then reimport this. I've never tried exactly this, but when I was starting out with genealogy software I did similar things.
Or just hand enter them if there's only, say, a few dozen.
Someone else may have recent experience with other software that may help.
/George
There are 87 INDIs. Most have some other data attached (OCCU, RESI, etc. I used Notepad++ to strip out the CHAN and CREA parts, and will try just appending o my existing GEDCOM and re-importing. It has other problems also; things that should be in PLACes are in DATEs and there's a DATE ? line for a death here and there. It wasn't made with an eye toward data integrity; it was made to be a printout at an upcoming reunion.
Let us know how it works,
Thanks,
George