I don't think what I said was as clear as my thinking, so I'll try again.
First step is that the information born "Abt 1850" in Missouri, comes from
the 1880 census.
Then you have a chance to visit the cemetery and his headstone give a birth
of November 10, 1849.
I was wondering why the alternate birth information is November 10, 1849,
without a place. Why is it not possible to simply write over the "Abt 1850"
in the primary birth field and append the source of the cemetery. THEN, go
to the Alt Birth event, enter "Abt 1850" and append the 1880 census source.
I don't think it is reasonable for the program to know that part of the
entry you have for his birth should be retained. How would it know which
part? What if, instead of learning a more precise dob, you learned that he
was born in La Plata, Macon County, Missouri. Would you have put this more
precise place information in the alternate birth field and then asked for a
swap, expecting the "Abt 1850" to remain in the date field? Or would you
type over the Missouri entry, source the correction, then make an Alt Birth
event, entering Missouri.
I just don't see that just because the Abt information was found first, that
all subsequent information would be an alternate. If you had found the
precise birth information first, would you even make the Abt entry? For
myself, I would not bother, and in fact consider Abt 1850 and a precise date
in late 1849 to be the same. However, following this discussion, I might
make a comment in the source of the Abt 1850 information indicating the lack
of specificity.
But let me add an additional comment about my own research. Most of the
people I'm working on are not close relatives - 4C2R is not an unusual
relationship for a person and his family in my current research. I do what I
can, but I'm not visiting cemeteries, getting GPS coordinates, nor doing any
mapping. The hunt is fascinating and I still get my Aha! moments. But it
might make a difference to know why this Abt 1850 information isn't really
worth very much in my view, though I wouldn't throw away (delete) the source
information if I'd found it first.
Elizabeth
researching the descendants of William and Sarah (Patterson) Thompson
----- Original Message -----
From: "Pat Hickin" <[EMAIL PROTECTED]>
To: <LegacyUserGroup@legacyfamilytree.com>
Sent: Saturday, August 02, 2008 9:46 AM
Subject: Re: [LegacyUG] Marriage and other vital stats sourcing and possible
confusion
I was just making all that up as an example. Doing a Swap DOES put the ca
1850 into the alt birth field, but it also takes out the pob info, which
was precise.
Remember the ca 1850 was entered first, before the exact dob was found.
Thanks for your comments, though.
And of course sometimes you want to have more than one DOB listed because
you're not sure which -- if either -- is right.
Pat
Elizabeth Richardson wrote:
Is there some reason you dont' put the "Abt 1850" in the Alt Birth event
and source it? Then add the more precise information adding the
additional source. I don't know why you are trying to swap the
information since you have to make a new event anyway. Seems like putting
the Abt information in the Alt event would be easier. By the way, if I
were to come across this Abt information after I had found the precise
information, I would probably just skip entering it, unless it is more
than a year different.
Elizabeth
researching the descendants of William and Sarah (Patterson) Thompson
----- Original Message ----- From: "Pat Hickin" <[EMAIL PROTECTED]>
To: <LegacyUserGroup@legacyfamilytree.com>
Sent: Saturday, August 02, 2008 9:07 AM
Subject: Re: [LegacyUG] Marriage and other vital stats sourcing and
possible confusion
I agree with Janis, who wrote, "Separating date and place, for purposes
of sourcing, would be enough for me." .
One reason I'd like date and place separated is because so OFTEN I have
two different sources for date and place for ALL vital statistics -- not
just marriages.
Then there's the problem with "Swapping" birth, death, marriage and
ALTERNATE birth, death, marriage info.
Let's say you have a dob of "ca 1850" and a pob of town, county,
state,USA from Source A.
Then you find a tombstone (Source B) with a dob of 10 Nov 1849 and no
pob.
If you enter the Source B dob in the Event field and click Options> Swap
birth info, you now have a blank in the pob space. So then you have to
add the pob manually, be sure you've got both sources cited in the birth
source field; add notes in the detail of each source saying (for Source
B "for dob only" and, for Source A "for pob only" -- except you may
prefer to write out, rather than just use initials for pob and dob. )
If this kind of thing occurred only occasionally it wouldn't be a big
issue, but when 75% of you entries are like this it's another matter!
FURTHERMORE -- AND the following can be a SERIOUS problem that I have
brought directly to Legacy's attention.
Let's say that the existing birth info has
BORN: ca 1850, Fairfield, Essex, NY,USA
(and your source is Source A-family history)
Then you find a tombstone and enter the alternate birth info as an Event
as follows:
EVENT: Alt. birth
DESCRIPTION: Date on tombstone is difficult to make out.
LOCATION: [LEFT BLANK]
DATE: 12 Nov 1849
(and your source is Source B-tombstone)
THEN you do a SWAP (Options> Swap with birth information)
and you now have
BORN: 10 Nov 1849 [no location info]
(and your source is Source B-tombstone)
And in your events list you now have
EVENT: Alt. birth
DESCRIPTION: Date on tombstone is difficult to make out.
LOCATION: Fairfield, Essex, NY,USA
DATE: ca 1850
(and your source is shown as Source A-family history -- whereas you
actually have 2 different sources for this info as the source for the
Description field should be Source B).
Well of course you have to go in manually and get all that straightened
out. Legacy does not even WARN you that it is not really doing a swap
of ALL ,e.g., birth information or is garbling the source info.
I was not aware this was happening for YEARS and I've no idea how much
misinformation in re sources I have as a result.
I complained to Legacy once months ago about this but I see Legacy
(Beta 7.0.0.55) has not corrected it.
I suppose I'll also send this message to the Legacy Test Group also.
Pat
Janis Gilmore wrote:
Separating date and place, for purposes of sourcing, would be enough
for me.
Janis
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Wynthner
Sent: Saturday, August 02, 2008 1:19 AM
To: LegacyUserGroup@legacyfamilytree.com
Subject: Re: [LegacyUG] Marriage sourcing
To the best of my knowledge there is no softwware package that allows
individual sourcing of the day, month, and year of a date, in the same
vein
there is no package that allows individual sourcing of street number,
street, city, county, state, and country. I've never understood just
why all
packages don't allow this. It seems the most natural thing in the
world!
----- Original Message ----
From: Pat Hickin <[EMAIL PROTECTED]>
To: LegacyUserGroup@legacyfamilytree.com
Sent: Friday, August 1, 2008 10:22:56 PM
Subject: Re: [LegacyUG] Marriage sourcing
Elizabeth wrote: "Jess, you will see that Legacy does not allow you to
separately source the date and place of any event. "
That is SO true and for the life of me I do not understand why this is
the case. I wish someone would explain the reasoning behind it. I get
tired of having to write little notes --
Pat
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
E-mail message checked by Spyware Doctor (6.0.0.362)
Database version: 5.10390
http://www.pctools.com/en/spyware-doctor-antivirus/
E-mail message checked by Spyware Doctor (6.0.0.362)
Database version: 5.10390
http://www.pctools.com/en/spyware-doctor-antivirus/
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
