Jean, I am a confirmed lumper but if therere are no common fields then there doesn't seem to be much point in lumping. I have no doubt there are times when splitting would not make sense either.
Ron Ferguson _____________________________________________________________________ *New Tutorial* Publish your Web Pages - Blogs http://www.fergys.co.uk View the Grimshaw Family Tree at: http://www.fergys.co.uk/Grimshaw/ For The Fergusons of N.W. England See: http://myweb.tiscali.co.uk/fergys/ _____________________________________________________________________ Date: Mon, 10 Nov 2008 18:33:21 -0600 From: [EMAIL PROTECTED] To: LegacyUserGroup@legacyfamilytree.com Subject: [LegacyUG] Question on sourcing I've been using Legacy for many years, but recently decided it was time to go back and rethink sourcing. I had been following a method that had developed ad hoc, but now I want to get serious about it. I've read some of the threads on lumping/splitting, and it's led to a couple questions I'm sure some of you more disciplined users can help me with. I'm leaning towards lumping. It makes sense for things like US Census records, SS death index, city directories, and the like. However, for things like memorial cards, what would be the advantages of having one master source called 'Memorial cards"? That's a serious question. There's no common source information that would be shared, so what other reasons are there? Many thanks, Jean Suplick _________________________________________________________________ BigSnapSearch.com - 24 prizes a day, every day - Search Now! http://clk.atdmt.com/UKM/go/117442309/direct/01/ Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
