Tony Rolfe wrote >If you have a marriage (or birth or death) certificate and want to use >it as a source for various data, should you create one source for each >certificate? Or is it better to have a single source "Marriage >Certificate" and put each certificate's data as detail for the main >source?
As with so many things, it boils down to individual choice. On this list we tend to refer to the two options as Splitting (many Master Sources) or Lumping (one Master Source). Personally, I am a Lumper because I believe this is good database practice. Having numerous Masters for the same type of Source leads to much needless repetition and the scope for more mistakes. Someone will be along in a minute to give you all the reasons why Splitting is a good thing! > >Individual sources means a lot of source entries, but a single source >means you can't list everyone who refereces a particular certificate. I've never found this to be a problem as I've never needed to create such a list. There aren't *that* many people named on a Certificate and if I want to know who is I look at the Certificate. -- Jenny M Benson 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
