Groups > soc.genealogy.computing > #6534

Re: FamilySearch introducing errors

Subject	Re: FamilySearch introducing errors
Newsgroups	soc.genealogy.computing
References	<gganngtc0omadq2a46sdtkfsmi7gsu8i8m@4ax.com> <2YGdnbFl0vaRKOb8nZ2dnUU78VPNnZ2d@brightview.co.uk> <tcjpngdgpf5bbtv4ss5aslqnp25tqhbcl0@4ax.com> <sljf4l$iuh$1@dont-email.me>
From	Richard Damon <Richard@Damon-Family.org>
Message-ID	<VNbfJ.1663$bn2.474@fx12.iad> (permalink)
Organization	Forte - www.forteinc.com
Date	2021-10-30 09:30 -0400

Show all headers | View raw

On 10/30/21 8:51 AM, knuttle wrote:

> In my opinion, the location is so that I can go to any current map and 
> locate where the family lived. In this way when in the area I can easily 
> travel to that location.   If I use the name of community that no longer 
> exist, I may never find the family farm.  The historical location is put 
> in the description, or a note if the information on the historical 
> location is to large for the description.

The problem with trying to record what a place is called 'now' is that 
'now' changes. Do you really work hard to keep up on how EVERY place 
might get adjusted. For some places, that may be fairly stable, but for 
others (like eastern Europe) it is quite fluid.

That is why MY standard (and I will allow that others may do it 
differently) is to record the place as it was at that time, with 
comments of how that might have changed in more modern times.

Back to soc.genealogy.computing | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

FamilySearch introducing errors Steve Hayes <hayesstw@telkomsa.net> - 2021-10-29 10:07 +0200
  Re: FamilySearch introducing errors Ian Goddard <ianng@austonley.org.uk> - 2021-10-29 09:48 +0100
    Re: FamilySearch introducing errors Steve Hayes <hayesstw@telkomsa.net> - 2021-10-30 06:54 +0200
      Re: FamilySearch introducing errors Graeme Wall <rail@greywall.demon.co.uk> - 2021-10-30 08:38 +0100
        Re: FamilySearch introducing errors Steve Hayes <hayesstw@telkomsa.net> - 2021-10-31 20:32 +0200
      Re: FamilySearch introducing errors knuttle <keith_nuttle@sbcglobal.net> - 2021-10-30 08:51 -0400
        Re: FamilySearch introducing errors Richard Damon <Richard@Damon-Family.org> - 2021-10-30 09:30 -0400
          Re: FamilySearch introducing errors Ian Goddard <ianng@austonley.org.uk> - 2021-10-31 17:06 +0000
        Locations (was: Re: FamilySearch introducing errors) "J. P. Gilliver (John)" <G6JPG@255soft.uk> - 2021-10-30 15:38 +0100
          Re: Locations (was: Re: FamilySearch introducing errors) knuttle <keith_nuttle@sbcglobal.net> - 2021-10-30 18:06 -0400
      Re: FamilySearch introducing errors Ian Goddard <ianng@austonley.org.uk> - 2021-10-30 16:02 +0100
        Re: FamilySearch introducing errors "J. P. Gilliver (John)" <G6JPG@255soft.uk> - 2021-10-30 16:23 +0100
          Re: FamilySearch introducing errors Steve Hayes <hayesstw@telkomsa.net> - 2021-10-31 20:34 +0200
        Re: FamilySearch introducing errors Steve Hayes <hayesstw@telkomsa.net> - 2021-10-31 20:26 +0200
      Re: FamilySearch introducing errors Ian Goddard <ianng@austonley.org.uk> - 2021-10-31 17:25 +0000
    Re: FamilySearch introducing errors Ian Goddard <ianng@austonley.org.uk> - 2022-02-14 23:23 +0000
      Re: FamilySearch introducing errors Daniel65 <daniel47@eternal-september.org> - 2022-02-15 22:42 +1100
      Re: FamilySearch introducing errors Steve Hayes <hayesstw@telkomsa.net> - 2022-02-16 07:45 +0200
      Re: FamilySearch introducing errors Nigel Reed <sysop@endofthelinebbs.com> - 2022-02-22 14:15 -0600
        Re: FamilySearch introducing errors Ian Goddard <ianng@austonley.org.uk> - 2022-02-23 15:45 +0000
          Re: FamilySearch introducing errors Steve Hayes <hayesstw@telkomsa.net> - 2022-02-24 12:55 +0200
          Re: FamilySearch introducing errors Nigel Reed <sysop@endofthelinebbs.com> - 2022-02-24 17:34 -0600

csiph-web