Good points, Brett.  Jerry

Brett McL Robinson <[email protected]> wrote:

>Hi Jerry
>
>You may not have noticed but the Events (in Legacy) has been named
>Events/Facts, to highlight that the structure can be used to record
>events and facts. It could be that some users are recording the census
>as a fact. However I would do as you - the census is a source, the
>residence is a fact.
>
>Cheers, Brett
>
>B McL Robinson
>Tel +64 7 856 6582, 0277 500 714, fax +64 7 856 6582, Skype AB1252
>PO Box 1252, Hamilton 3240, New Zealand
>
>
>On 6/11/2011 11:40 a.m., Jerry wrote:
>> I know a lot of people do treat the census as an EVENT in someone's life
>> and I guess a lot of the professional genealogists do this, but I'm
>> still puzzled by why?  To me a census is a SOURCE of information to
>> collaborate events in a person's life - birth, marriage, etc.   But I
>> never treat a census as an event.  People did not attend any census
>> meeting about themselves or conduct a census about themselves.
>> Therefore, there is another school of thought on this and that is to use
>> the census as a SOURCE and not as an EVENT.   But, again, Legacy will
>> let you do it either way - just making sure the other school of thought
>> is not lost on this....
>>
>> Jerry in Michigan / http://www.MerriamFamilyTree.org
>>
>> On 11/05/2011 05:33 PM, Wendy Howard wrote:
>>> Hi Bruce,
>>>
>>>> I am puzzling on where to put Census (or Residence) Events for a couple.
>>>> It is clear that a single person in a Census would have the Census as
>>>> an Individual Event.  But where you others put a Census Event for a
>>>> couple? Individual? Marriage? Both?
>>> This is something that can be done in a variety of ways (as you've
>>> already noticed) and the one that is "right" is the one that you like
>>> and suits your needs.  What is right for one person may not be right for
>>> another, so consider your options, and how you'd like the entries to
>>> appear in your reports.
>>>
>>> My method is to have a census event for each person.  I put a transcript
>>> of the census entry for the entire household in the source (in the
>>> Text/Comments field of the Source Detail, and check the box to include
>>> it in reports), so when I create a report where more than one person in
>>> that household appears, that transcript appears only once.
>>>
>>> I've edited the sentence structure for census events so that when all
>>> fields are filled it reads:
>>>
>>> [HeShe] appeared on the census [onDate] [inPlace] as a [Desc].
>>> [Notes][Sources]
>>>
>>> The [Desc] field is where I put their age and occupation, such as
>>> "3-year-old", or "22-year-old Ironstone Miner" - without the quotes I've
>>> shown here to distinguish the field contents.
>>>
>>> These two examples, taken from my great-great-grandfather William
>>> Boynton IRELAND, come out reading:
>>>
>>> "He appeared on the census in 1851 in Langtoft, Yorkshire, England as a
>>> 3-year-old", and
>>> "He appeared on the census in 1871 in Rosedale West Side, Lastingham,
>>> Yorkshire, England as a 22-year-old Ironstone Miner"
>>>
>>> ... each sentence followed by a superscript number referring to the
>>> source information, where a transcript of the household can be seen.
>>> When he was three, William had no occupation ascribed to him in the
>>> census, so I don't mention any.
>>>
>>> With the [Desc] field at the end of the sentence, I can add in any other
>>> peculiarities of the census entry that I want to mention, or I can use
>>> the Notes field, as I feel the need.
>>>
>>> This suits me.  I have developed it over the years, mainly from reading
>>> of other people's examples on this list.
>>>
>>> It might sound like a lot of work, but I use the Event Clipboard, once
>>> I've set up the first person, and edit the individual details for each
>>> subsequent person after copying the clipboard to a new event for them.
>>> The source information is carried along in this clipboard, so you only
>>> have to do the bulk of the work once.
>>>
>>> Hope this helps.  :-)
>>>
>>> Kind Regards,
>>> Wendy
>>>
>>>
>>> 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
>>> 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/[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
>> 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/[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
>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/[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
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