The Legacy training video DVDs show the example of an Event that is used for multiple individuals; their example is a census page, but a will or other document that mentions multiple family names would work the same way.
You enter ALL of the information from that source document, beginning to end, including all of the individuals. You can then "highlight" the data that applies to the particular individual you are adding that event to (highlight it with your cursor, then mark it BOLD or underline or whatever using the little option box to the left of your event box) Then click on the little "copy event" icon over to the lower right of your event screen (if you hover your mouse over it, it will tell you what it is) Then you are ready to go to the next person; go to the "add event" screen and simply click the "paste event" icon and everything is filled in. "un"highlight the data from the first person and highlight the data for the 2nd person (and so on); you don't have to highlight the data for the individuals but it makes it easy to go right to their information instead of reading through the whole document to find them. That event will stay on your event clipboard until the next time you want to copy an event over it. I use this extensively for census data; it makes it very easy to see all the relationships, who was in the house that year, etc. If you only entered the data that applied to each individual, you wouldn't get the "big picture" of each census page and every time you wanted to see that, you'd have to pull up the census image. Kathy On Tue, Sep 7, 2010 at 7:45 AM, Jenny M Benson <ge...@cedarbank.me.uk> wrote: > On 07/09/2010 12:50, Adnepos_Iacobi wrote: >> /Legacy provides a way of sourcing evidence to support events such as >> births and christenings which can point to a father-son relationship, >> but the link between a father and son for instance does not seem to be >> capable of being supported by a source citation/ > > Ah! I'm with you now and I have addressed this point in another post > within this thread. >> > I just seems untidy to place the same >> or similar transcribed material (more pressing with the amount that >> needs to be taken from a will) in several places in the Legacy database. > > 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. > > However, Legacy very oblgigingly makes it very easy to input these > chunks of text many times over: see Event Clipboard and Source > Clipboard. And just plain old Windows Clipboard comes in useful, too! > -- > Jenny M Benson > > > > 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 > > > > -- Kathy Meyer "To reach a goal you have never before attained, you must do things you have never before done." --Richard G. Scott, "Finding the Way Back," Ensign, May 1990, 74 Insanity: doing the same thing over and over again and expecting different results. ~ Albert Einstein 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
