Scott,
Since I have never used a File ID I am not sure exactly how it works
but I think I will play around with it and see if this method might work for
me. It might be because I've never used File IDs that this sounds more
complicated than it is but I do get the thought process you are using to record
information this way. Thank you.
Paulette Smith
-----Original Message-----
From: Scott Hall [mailto:seh0...@gmail.com]
Sent: Sunday, May 23, 2010 4:46 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] Two Citation Questions...
Hey smithrmp...
I, too, am learning the best way to record information in the database, and
like you, "started over" when I bought Legacy, re-entering all of the
information I had from an earlier program.
Even now, however, I still am learning on the fly thus having to update or
correct information and sources to ensure the data is recorded accurately, that
I have a clear picture of where each piece of datum came from, and that the
source citations are proper.
In regards to different sources providing different pieces of the
puzzle, I began to use detailed research notes. I assign each master
source a File ID and list where each component came from. For example, I
learned the birthdate and location of one person in my file, Egbert Pennington
Hall, from a GEDCOM file provided to me from another genealogist. Because this
file was a bit lackidasical in citing its sources, I've decided to give all
data obtained from it with a surety level 1, and aim to replace it with more
credible sources when they are discovered. The 1900 census is a more credible
source, and corroborates some of the information (specifically month, year, and
state). The Social Security Death Index is also a more credible source, and
also corroborates some of the information (inlcuding day, month, and year).
The city where Egbert was born is in neither of the the census nor the SSDI,
and so my source for that remains the GEDCOM file.
My research notes state:
Birth
CEN-1900-F: Month; Year; State
SSDI-RW: Day
GEDCOM-HAF: City/Town
The codes are my file IDs for the three sources. Alternatively, I could note
that the SSDI-RW also includes the month and year, but have not yet decided if
I wish to do this or not. I struggle between recording corroborating sources
and not wanting an index of every single place I found information about this
person when such information is identical to that obtained elsewhere. I am
curious how others handle this.
I only use Alt. events when information conflicts. Say, for example, the 1900
census says Egbert was born in Pennsylvania, but the GEDCOM says New York. In
this case I'd list the date of birth but not the location in the Birth field,
citing the census and the SSDI and listing each in the Research Notes. I'd
then create an Alt. Birth event with the information from the GEDCOM file. If
I later prove the GEDCOM file to be incorrect, I'd eliminate the event entirely
and make no mention of it (because the GEDCOM is a secondary source). If,
however, I discover the census to be incorrect, I'd move that data to the Alt.
Birth event and change the event name to "Disp. [Disproven] Birth" and maintain
it as a permanent record, although one I'd supress from reports.
Alternatively, I might also use the research notes to list the incorrect
information, as I did with this relative, who's name appears differently in
multiple censuses:
Michael Thein
Research Notes:
Name
A number of alternate spellings are found throughout the census records, all of
which are considered errors and thus excluded from this database. They are:
CEN-1850-F: Michael TINE
CEN-1860-F; Michael THEIN (accurate)
CEN-1870-F: Michael THEIM
CEN-1880-F: Michael THIN
CEN-1900-F: Michael THIEM
CEN-1910-F: Michal THEIN
I am still working out the best way to record multiple sources and conflicting
information, and have not perfected a method.
Scott
On Sun, May 23, 2010 at 3:44 PM, smithmp <smit...@hughes.net> wrote:
>
> I used to say that I was researching my genealogy. Now, after over 15 years,
> I have started over because much of what I had gathered in the beginning did
> not have a source citation attached. Nor did I know anything about putting
> notes in the research section so that when I came back to a person after a
> very long time I would know what I had already searched and where I thought I
> might search next. I guess I should have just called it "Gathering Family
> Folktales". As painful as it is, I have started over, using my old database
> as just a reference point. I have come up with a couple of problems.
>
> 1. There are times when I find in a source only the date of an event such as
> a birth date but no location. Then I'll find just the location but not the
> date or at least not the full date. How do I source it in Legacy to reflect
> that a source had half of the birth date and another source had the other
> half with out having to put an alt. birth event? Or is this the only way to
> do this? Because if this is so then reports like the Pedegree chart will
> only list half of the information.
>
> 2. I have begun using the to-do feature in Legacy and have found it a
> wonderful resource for keeping track of where I've looked and what my
> thoughts were on a specific piece of research. Even if I looked at a source
> and did not find anything in it for what I am looking for, I add it as a
> source on that particular to-do item with a notation in the source detail
> that I did not find anything concerning the item I was looking for.
> Sometimes I put why I researched a particular source if it isn't clear as to
> why I was looking at it. Sometimes I make a note in the source detail that
> there was a good description of an area where an ancestor lived or that it
> had a map that may prove handy to go back to, or even to list some of the
> sources in the bibliography as possible places to also look for certain
> information. My question on this is if there is an easier way to print what
> sources were searched for an individual person or event if it was not
> actually used as a source for that person or event. I ask this because
> Legacy has a glitch at the moment that will not print your sources for your
> to-do list. It just lists a number and nothing else. I already asked tech
> support and they are aware of this problem and will fix it on a future
> release. I'm am just hoping there might be a work around in the meanwhile.
>
> digital image by subscription
>
> Geographia - World Travel Destinations, Culture and History Guide.
> InterKnowledge Corp., Northern Ireland - History of Derry　
> (http://www.geographia.com/northern-ireland/ukider01.htm : accessed 22 May
> 2010), History of Derry [and the creation of Londonderry]. Repository:
> Geographia - World Travel Destinations, Culture and History Guide,
> i...@geographia.com, http://www.geographia.com.
>
> 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/legacyusergr...@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 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/legacyusergr...@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 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/legacyusergr...@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
