Jenny:

1. As I mentioned when I started my family tree I didn't source my documents (I 
never in a million years thought it would get as big as it is, and did not 
understand why it was so important).

I'm now trying to redo my tree, but this time sourcing each documents (I do 
have copies of every document, and written on the back the day I accessed it, 
etc.).

My method of splitting is taking me WAY too long to redo. I'm thinking lumping 
will save me a huge amount of time.

Can I ask you (and any other lumpers).

*I* transcribe the complete document and copy to the Master Text. I then copy 
pertinent parts of the Master Text to the Detail Text depending on what I want 
to prove. (VERY time consuming, but I liked that if forced me to analyze the 
document).

*You* transcribe the complete document, but instead of having it in the Master 
text you have the complete transcription in the Detail text. Is that right? 
Everyone using that Source has the complete transcription.

2. Comparing your method to Shared Events, your method seems more exact (and 
transferable by GEDCOM) is the only plus of Shared Events that it would be 
faster?

Thanks again for your direction,

leo

> From: ge...@cedarbank.me.uk
> To: LegacyUserGroup@LegacyUsers.com
> Subject: Re: [LegacyUG] Lumping vs. Splitting
> Date: Thu, 26 Dec 2013 16:57:02 +0000
>
> On 26/12/2013 16:16, lio . wrote:
> > 1. When you source a document, where do you put the transcription - in
> > the Master Text, or in the Detail Text?
>
> Being a lumper (which is actually correct practice for a relational
> database, although I don't always carry it to the full extent which I
> should) I put transcriptions in the Source Detail because that is where
> they are relevant.
>
> For example, I have a Master Source for  Birth Certificates from the
> GRO.  A transcription and an image of the Certificate are attached to
> the Source Detail wherever a particular Certificate is cited.  Another
> example, I have a Master Source for the Book "Monumental Inscriptions of
> the British West Indies".  I attach a transcription and image of the
> relevant entry to the Source Detail whenever an entry from that book is
> cited.
>
> > 2. Are you using the new Shared Events feature? Any issues?
>
> I haven't fully explored this feature yet, but I don't think I will be
> using it.   Using the Birth Certificate example, I have the Birth as a
> Vital Event for the child and I create an Informant Event for the person
> who registers the Birth, citing the Birth Certificate as a Source for
> both Events and for other information such as the parents' names.  For a
> Census, I create an Event which has each person's details in the Desc
> field and a listing of all the members of the household in the Notes
> field.  I am very happy with this arrangement and don't see how a Shared
> Event could improve on it.
>
>
> --
> 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/legacyusergroup@legacyfamilytree.com/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on 
> our blog (http://news.LegacyFamilyTree.com).
> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>
>



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/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our 
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Reply via email to