Like Anne I use "about" when I know the date within a year or two.
This can be a birth year based on the age stated on a census, birth year
based on declared age on a marriage record or any other dated document
which includes a declared age. When multiple documents give different
dates I use the Alt. Birth event to record each one and attach the
source document on which that date is based.
When I have data that allows me to calculate a specific date (age in
years months and days along with date of death from a gravestone for
example I use Calc. to indicate that the date is based on a calculation.
Brian Kelly
On 28-Sep-17 11:09 AM, Anne Hildrum wrote:
I don't know what others consider about as, but use it when I for example
see an age
given in a census. In the 1801 census I use for Norway age is often given
and if it say someone
is x years old, it migt often mean they were born x+1 or x-1 year so I use
about.
Also if I in the marriage record find the age of bride and groom, the groom
I have the birthdate for,
and it fits with the age at marriage and the wife is x years older or
younger than the grrom, but I have no ideas of when she was born,
except for example that she is 3 years younger than the grom, I would use
about for her age.
Anne
-----Original Message-----
From: LegacyUserGroup [mailto:[email protected]] On
Behalf Of JV Leavitt
Sent: Thursday, September 28, 2017 4:38 PM
To: Legacy User Group <[email protected]>
Subject: Re: [LegacyUG] Legacy 8 - date change after latest update
Does anyone know what the term "About" means when used with a date?
Everyone seems to have a different idea about the level of credibility to
give it. Many think it must be within a few years, and don't think of it as
being a wild guess (which so often turns out to be the case), but I'm not
alone in thinking of it as a wild guess, which means it might be 10 to 50
years off. I never use the term About for a date, but would rather use the
term Estimated or Est. Better than that, of course, when only an age is
given in a source, is to use the term Calculated, or cal. Calculated as a
term for a date can properly be seen as having much more credibility than
the term Estimated.
Unfortunately, the term Estimated is sometimes being used for a date when it
was derived from a calculation based on age. I sincerely wish they wouldn't
do that.
I'm very disappointed that the term Estimated or Est is not included in
Legacy's Date Prefix options.
Joseph Leavitt
On 7/7/2017 1:00 PM, Lucy Abbott wrote:
OK, had not thought of setting up the Gedcom from Ancestry, changing
all the Est to Abt, doing the same with my existing Legacy file before
doing the merge. Not exactly what I want but it would work and save time.
Never done a search and replace but going to make a duplicate file and
try this on existing Legacy file.
Your comments on making my Gedcom a Text file have me confused. I
normally just ask Ancestry to make a Gedcom, did not know I should
make some adjustment to it or that I could even do something
different. Feel free to email me directly with some help on this if
you would.
Thx for the solution for the changing of the files, really appreciate.
Lucy Abbott
Mill Creek, WA, USA
On Monday, July 3, 2017 4:28 PM, "J.M. "Jay" Ingalls"
<[email protected]> wrote:
Lucy Abbott,
Remember to save the file as PLAIN text with the ".ged" file
extension, or it will include "garbage" you do not want from what I
have been told in the past.
Jay Ingalls
On 7/3/2017 3:51 PM, Jenny M Benson wrote:
On 03-Jul-17 07:59 PM, Lucy Abbott wrote:
Give me an option here that I can use. I want to stay with Est
because there is no way that I know of to change all the ones on
Ancestry and I had planned on downloading a Gedcom and merging that
file with my Legacy file once I have done all the research at that
site. Without this correction, many more hours will need to be used
on the merge. My merge is scottish names and 60% are duplicate type
names due to naming conventions so hours and hours are needed for
the merge and this has me frustrated thinking of how many more
hours will be needed to change the dates headings.
If it turns out that you DO have to change "est" to something else,
it needn't take hours. If you open your Gedcom as a Legacy file you
could use the Search & Replace function to change all the instances
of "est" in each Date field. Granted, not a single-step option, but
wouldn't take too long. In fact, a Gedcom being text file I think
you could probably do the Search & Replace in the Gedcom with WP
program.)
--
LegacyUserGroup mailing list
[email protected]
<mailto:[email protected]>
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.co
m
Archives at:
http://www.mail-archive.com/[email protected]/
--
LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/
