Jenny M Benson wrote: > On 07/09/2010 12:50, Adnepos_Iacobi wrote: > > It's not good database practice to have to input chunks of data > repeatedly and store multiple copies of it, but the way Legacy works > is based around the Individual, each of whom can have numerous Facts > and Events. To avoid the repetition of data such as a Will > transcription one would have to work with a program which was based > around the Event/Fact to which can be linked numerous Individuals.
Jenny, How very true, and for me the only way to minimise this effect is to include all the details in the Source, whether it is a will, Census or whatever. It is by no means perfect but it does mean only one DB entry and when reading about an individual it is not cluttered, as it would be if there was a Will Event, or a Census Event etc. It if this doesn't comply with so called standards, I don't care, it contains all the information for somebody who wishes to follow it up. BTW I don't do this myself, as I do not publish such details, but I do have the images attached to each source. Ron Ferguson _____________________________________________________ *New* Tutorial: Add Location Pins to Google Earth http://www.fergys.co.uk Includes the family tree for Alan J Grimshaw And the Fergusons of N.W. England ____________________________________________________ Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
