When I merged my own gedcom from ancestry.com, I merged into my Legacy file but saved the result under another name, such as "merged files." My question: Is it any more work to clean up this merged family file (I had a lot more information in the ancestry.com gedcom because I've been working there a lot) Is it quicker to compare two family files and resolve duplicates before the merge, than it is to clean up the new merged family file? Especially since I already need/needed to do a lot of clean up on my original Legacy database? Thanks for advice!
>________________________________ > From: Leon Chapman <[email protected]> >To: [email protected] >Sent: Sunday, April 8, 2012 12:18 PM >Subject: Re: [LegacyUG] Duplicate Problem > >In your newly acquired GEDCom file, you neet to 1st import that into a >blank/empty Legacy database - create a blank database and import the >GEDCom file. > >Edit all the locations to make them like your standard (eg, 4 fields). > >As an example using the Sample Database as your master database which >has a major family as BROWN, look in your newly created database for >Asa Clark Brown. Tag the Ancestors and export to a New Legacy >database. >Now import this Asa Clark Brown ancestor file to real master database >(Sample database). > >This will minimize your duplicates to only Asa Clark Brown and his ancestors. > >If you go to your oldest ancestor and work with the GEDCom file you >converted to a Legacy file to start with this same peron, you should >be able to minimize the number of duplicates to 4-10 people (just one >family). > >You might have to do this for a couple of families, depending on what >is in the GEDCom file you started with. > >Merging can lead to a lot of problems and you should minimize the >number of duplicates when importing into Legacy. This just cuts down >on possible errors when merging and makes it a lot easier to import >the people you want to add to your database. > >Hope this helps. >Chap > > >___ >Leon Chapman >[email protected] >----- > > > >On Sun, Apr 8, 2012 at 8:55 AM, R G Strong-genes ><[email protected]> wrote: >> I agree. Are you importing the gedcom directly into your file? You should >> import it into a NEW file then do all your duplicate checking, place name >> formats etc, etc. BEFORE you merge it into your main database. This will >> eliminate most of your duplicates and will merge more smoothly plus you can >> create the source for that GEDCOM and the info will import with the new >> source. >> Russ >> >> >> From: RICHARD SCHULTHIES >> Sent: Sunday, April 08, 2012 4:52 AM >> To: [email protected] >> Subject: Re: [LegacyUG] Duplicate Problem >> >> You just have to buckle up and do the Merge/Unlink like we all do. No easy >> answer. Sorry, Rich in LA CA >> >> From: RUNION ROBERT <[email protected]> >> To: [email protected] >> Sent: Saturday, April 7, 2012 2:50 PM >> Subject: [LegacyUG] Duplicate Problem >> >> I received a GEDCOM file that I would like to add to my files (to a backup >> copy just as a safeguard). In importing the GEDCOM of approximately 2000+ >> names, I have discovered duplication of about half of the persons imported. >> Is there a recommended way to eliminate the duplications? I tried the >> duplication process and it appears that I have to address each pair >> separately. This creates a problem when looking at the names and data as to >> which one is the accurate one or even if it is a duplication. Suggestions? >> >> >> >> >> Legacy User Group guidelines: >> http://www.LegacyFamilyTree.com/Etiquette.asp >> Archived messages after Nov. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> Online technical support: http://www.LegacyFamilyTree.com/Help.asp >> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on >> our blog (http://news.LegacyFamilyTree.com). >> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > >Legacy User Group guidelines: >http://www.LegacyFamilyTree.com/Etiquette.asp >Archived messages after Nov. 21 2009: >http://www.mail-archive.com/[email protected]/ >Archived messages from old mail server - before Nov. 21 2009: >http://www.mail-archive.com/[email protected]/ >Online technical support: http://www.LegacyFamilyTree.com/Help.asp >Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on >our blog (http://news.LegacyFamilyTree.com). >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
