Folks,
Thanks for the great discussion on sources. Sourcing is easier to define if
we remember what the purposes of source documentation are. First, and most
important, a source should be created and worded so that you can follow its
thread back to the information from which it was generated. Second, it
should be clear and concise so that others can use it to get back to the
original source material. After that, formatting and header, etc, are just
tools to support the above two purposes.
Jim Winfrey
----- Original Message -----
From: "T. Dan Wollam" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, August 19, 2001 5:14 PM
Subject: RE: [LegacyUG] Legacy 4.0 wish list
> Charles--
>
> Yes, I have changed my opinion. Comments similar to yours have
> convinced me. I am now following NGS advice and listing BOTH locations
> (as "Berkeley co., VA (now WV)"). Thanks to everyone for the
> discussion. I guess I'm NOT too old to learn something better. (Now I
> just have to convince my wife....)
>
> T. Dan Wollam
> Port Hadlock, WA
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of
> Charles Aubin
> Sent: Sunday, August 19, 2001 11:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [LegacyUG] Legacy 4.0 wish list
>
>
> Dan:
> I completely disagree with you. We are not only genealogists but also
> historians, and I was taught to always use the location at the time the
> event occurred, whether it was a birth, death or burial. Then use the
> notes to explain any changes that have occurred since that time. It is
> important to know where your ancestors events occurred not where they
> would have occurred today. Just my thoughts. Charles W. Aubin
>
>
> "T. Dan Wollam" wrote:
> >
> > It has been more years than I like to remember since I took some of my
>
> > basic genealogy classes, but I was taught that all location names
> > should be in present-day terms. For example, my family that lived in
> > Berkeley County, Virginia, prior to the Civil War are recorded in my
> > work as having lived in Berkeley County, West Virginia--even though
> > West Virginia didn't exist at the time they lived there. I can't
> > imagine the confusion if I recorded them as living in Virginia....
> >
> > And the problem certainly does exist in other countries around the
> > world. I try to consistently identify the location, however, in
> > present-day terms.
> >
> > I do add a historical note, however, when there is some significant
> > change to a location's political ownership.
> >
> > Dan Wollam
> > Port Hadlock, WA
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]] On Behalf Of wfp
> > Sent: Tuesday, August 07, 2001 11:09 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [LegacyUG] Legacy 4.0 wish list
> >
> > At 22:00 2001-08-06 -0700, you wrote:
> > >This is a very admirable project to all who participate, but some
> > >immediate questions come to mind:
> > >
> > >1) How will you be handling counties with changing boundaries? This
> > >presents an immediate problem for many depending upon which era one
> > is
> > >researching.
> >
> > [and many more similar thoughtful comments]
> >
> > I had received the impression that the general practice is to use the
> > present-day designations for historical locations whenever possible
> > (e.g., the place is not a ghost town, or, as in the case of Flagstaff,
>
> > Maine, underneath a reservoir). I could be mistaken, but this appears
> > to me to be the case.
> >
> > Now, of course it would be possible to use dual names for places (the
> > name at the time of the event and the current name), or the historical
>
> > or current name could be placed in event notes. Since I've been
> > attempting to use present-day names in my database, I'm thinking a
> > separate conversion chart, so to speak, might be the thing. Especially
>
> > if such a thing could be hooked up to the Legacy database
> > - which is something databases are good at, fortunately.
> >
> > Just a few thoughts ...
> >
> > To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp
> >
> > To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp
> To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp
>
> To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp
To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp
