Nothing will get fixed unless it gets in the queue. Be sure to send a
suggestion to Support to bring back a much used and needed feature - bold, et
alia.
CE
Date: Sat, 17 Oct 2015 10:20:50 -0600
Subject: [LegacyUG] Re: Census event vs source
From: kmeyer2...@gmail.com
To: legacyusergroup@LegacyU
On 17/10/2015 17:20, Kathy Meyer wrote:
> So in reading your responses, I'm understanding that you do NOT think it is
> a problem to duplicate the information in the source and the event for a
> particular census? That is my issue. I like the census event and I like
> my source to be clear in th
It seems to me that personal
preference is determined somewhat by the desired Report
results. As a test, enter Census Event as desired or in any of
the ways offered in this exchange, then run all the different
reports selecting different report options -
Try sending it in text format.
Lloyd
On 10/17/2015 5:41 PM, Elizabeth Verchio wrote:
> As an aside, I'm sorry for the added characters in my e-mail text -
> Mozilla Thurderbird for some unknown reason just adds them once the
> email is sent.
> Elizabeth Verchio,
> Illinois, USA
> Happy Legacy use
On 17 Oct 2015 10:56 PM, Jenny M Benson wrote:
> I have Census Events and Censuses as Sources but there is not a lot of
> duplication.
In my view, the Census is an Event. The Schedules (or documentation) produced
from a census, is a Source. If you can avoid using Census for both terms, there
woul
duplication and
contains all the information.
Ron Ferguson
http://www,fergys.co.uk/
-Original Message-
From: MikeFry
Sent: Saturday, October 17, 2015 11:27 PM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Re: Census event vs source
On 17 Oct 2015 10:56 PM, Jenny M Benson wrote
Message-
From: Ron Ferguson [mailto:ronfergy@tiscali.co.uk]
Sent: Tuesday, October 20, 2015 8:10 AM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Re: Census event vs source
Mike,
Whilst I agree with your basic point, I have never considered the census to be
an event, but only a
oots.com]
> Sent: Tuesday, October 20, 2015 11:57 AM
> To: legacyusergroup@LegacyUsers.com
> Subject: RE: [LegacyUG] Re: Census event vs source
>
> So a Marriage must also not be an event. The marriage
> certificate or license merely is a source for residences, ages,
> poss
On 20 Oct 2015 at 13:03, Bobby Johnson wrote:
> When I document the information found in a book, should I not create a "Book
> Event"? If not, why would I create a census event when I document the
> information contained in a census record?
A book is a thing, not an event.
But the publication o
On 20/10/2015 18:03, Bobby Johnson wrote:
> When I document the information found in a book, should I not create
> a "Book Event"? If not, why would I create a census event when I
> document the information contained in a census record?
Under some circumstances I *would* create such an Event, jus
nal Message-
> From: Jenny M Benson [mailto:ge...@cedarbank.me.uk]
> Sent: Tuesday, October 20, 2015 2:38 PM
> To: legacyusergroup@LegacyUsers.com
> Subject: Re: [LegacyUG] Re: Census event vs source
>
> On 20/10/2015 18:03, Bobby Johnson wrote:
> > When I document the infor
On 20/10/2015 20:09, Bobby Johnson wrote:
> If I use the census to indicate a person resided in a town, county, state
> according to the census and also recorded the census as an event then in a
> time line you will see something like this:
>
> Residence in 1910
> Census 1910
> Residence in 1920
Well, to be technically accurate, I would think a census would only be
an event in the life of the census taker. It would indeed be only a
source for persons listed. It's pretty hard to get people to change when
they have been doing it wrong for years, but it would be nice to
acknowledge the truth.
Sorry, the cutting and pasting came out wrong. I thought I was doing a
good thing by being brief. It was Steve who mentioned that a "census is
an event," not Bobby. My apologies for how it formatted. --Jerry
On 10/20/2015 04:42 PM, Jerry in Michigan wrote:
> Well, to be technically accurate, I wou
I don't see it as a real event because if a person listed on the census was
dead at the time the census was taken (and is listed with the family) then how
could it be an event for that person? My great grandfather was said to be
lying in a casket in the parlor when the census taker arrived. It
m]
Sent: Friday, October 23, 2015 6:02 AM
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Re: Census event vs source
I don't see it as a real event because if a person listed on the census was
dead at the time the census was taken (and is listed with the family) then how
could it
...@the-lightfoots.com]
Sent: Friday, October 23, 2015 7:36 AM
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Re: Census event vs source
You are confusing the date of the census with the date the enumerator finally
made it to that household. For example, the 1930 and 1940 US Census
ach [mailto:dia...@wavecable.com]
Sent: Friday, October 23, 2015 8:29 AM
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Re: Census event vs source
Very good point as I have found it both ways. A person living on April 1st
but not reported on the census as they had died in between as well as we
t; Subject: RE: [LegacyUG] Re: Census event vs source
> Date: Fri, 23 Oct 2015 13:03:31 -0700
>
> The census reports are replete with all sorts of incorrect and misleading
> information. Typical of most was the incorrect reporting of ages; for
> example, if a census was taken on April 1, a
have.
Howland Davis
-Original Message-
From: Diane Murach
To: legacyusergroup
Sent: Fri, Oct 23, 2015 10:30 am
Subject: RE: [LegacyUG] Re: Census event vs source
Very good point as I have found it both ways. A person living on April 1st but
not reported on the census as they had died
:br...@the-lightfoots.com]
Sent: Friday, October 23, 2015 4:04 PM
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Re: Census event vs source
The census reports are replete with all sorts of incorrect and misleading
information. Typical of most was the incorrect reporting of ages; for example,
i
21 matches
Mail list logo
