Matt: In general, I would agree with what you have said. What I have seen is one source that was assigned to everyone on the import of a GEDCOM and placed in the Unspecified field. So, there is only one Master source that is assigned to the unspecified field.
All that I described is tagging all records that have the original source and replacing it with a new source assigned to the "Name" field. Then simply delete the old Master source. It works nicely, but, when the original source is assigned to multiple fields it becomes more complex. As far as another source also being assigned to the unspecified field, what I have described should have no effect on the other source. You would have to repeat my process to remove the 2nd source assigned to the "Unspecified" field. I fully agree with the correct way to import a GEDCOM. 1. Import the GEDCOM into a completely new file by itself 2. Clean up locations, dates, sources, etc. (The RIN # assignment is a good idea here also) 3. Assign a master source to all of the people in the GEDCOM file before importing into your master database. 4. Then import to your master database & merge duplicates This method works for me and is exactly how I do it. Thanks for your comments. Chap Leon Chapman [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Henderson Sent: Monday, May 02, 2005 6:50 PM To: [email protected] Cc: [EMAIL PROTECTED] Subject: RE: [LegacyUG] Unspecified Events Leon, this works fine only if those people have no other sources assigned to them or no other alternate events to which the Unspecified Event source should be assigned. For example, if you had a Census event (in which case the source is an actual census)added after the import with the source assigned to the Unspecified field, and you did as you said in your email, then the source A - New would be assigned to the Census event, and any other information that existed before the import, or added after the import that the source New - A should not be pointing to This happened to me and I had to go through each individual used by the source and verify the data side by side with the Source file in a Split Screen View. There is no other correct way to do it if there is additional sourced information that doesn't belong to the misplaced Source. That is why before I even import a new file into my current file, I assign source in the file to everyone in the file to be imported, and that source is the name of the file itself, with its compiler, repository, etc., I also clean up the file (standardize locations, events, event defitions, Check surnames, make sure the location list does not have items that are not locations like "had three wives", "age twenty" or the like. Also, I try to assign the same User ID used on people in my file to the same person in the file to be imported and then I can merge using matched User ID numbers. Yes, this is tedious but then you will not end up with bad imports and files with mispelled duplicate locations or some peoples' strange ideas of entering Surnames. Then when I import the source I don't have to assign a source to the individuals imported. Its already there. Nice, Clean. Neat. And no hair pulling later! Matt Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
