Re: [LegacyUG] Location names for Pennsylvania

sarrazingeorges Wed, 07 Aug 2019 12:37:27 -0700

In the French group, we faced this kind of problem many years ago. In addition, 
there was the problem of GPS location errors for France and the indication of 
departments were missing. Only administrative regions were indicated and these 
regions were erroneous since the restructuring of the regions by the French 
government.

We redid everything for France, Belgium and Québec (Our approach has also been
used by the Portuguese group) and took the opportunity to use indicators after
the name of a place to clarify what it was.

For example, we use parentheses after the name of a place to indicate a parish.

Tilbury East {Chatham-Kent} (Saint-Pierre), Kent, Ontario, Canada

We use location names as they exist in the old documents. Curley brackets are
added to indicate the current name.

Tilbury East {Chatham-Kent} (Saint-Pierre), Kent, Ontario, Canada

The list of places therefore contains two or more entries for certain places -
A reference with the old name and another with the new name.

In some cases, it is necessary to specify the nature of a place - island, cape,
etc. Brackets are used.

Texas [State], United States

Sarthe [Département], Pays de la Loire, France

This system works very well for us and meets the criteria for referencing a
place.

I mention our experience as an example, hoping that some of our solutions can
serve as suggestions.

Georges

De : LegacyUserGroup <legacyusergroup-boun...@legacyusers.com> De la part de
Christopher Seward Sr.
Envoyé : 7 août 2019 08:42
À : legacyusergroup@legacyusers.com
Objet : Re: [LegacyUG] Location names for Pennsylvania

Just an interjection - the standard is that the last 4 fields of the location
are "city, county, state, country". It s also standard to use other data in
front of those 4 (e.g. neighborhood, school district, etc). It's the last 4
that location services look at.

On 8/6/2019 10:26 PM, Jerry wrote:

In my opinion, we should be cognizant of the fact our records are going to be
seen all over the globe. Therefore, IN would never be acceptable to me - just
my opinion. And by utilizing

, , Indiana, United States ****(of America not needed, but USA is also
an abbreviation and should be avoided, in my opinion, and easy to fix with a
FIND AND REPLACE in Legacy.)

This allows the index system to PERFECTLY sort your records by every criteria
(city, county, state, country) or equivalent. Without this consistency, you
will never get well designed indices (indexes) for your records, particularly
if you have a website. Thanks for listening!

Jerry Boor
https://www.MerriamFamilyTree.org

On 08/03/2019 15:07, James G. Hermsen via LegacyUserGroup wrote:

What does not make sense is seeing something like: , , , Indiana, United
States of America. when a simple IN would do. Or: , , , Berlin, Democratic
Republic of Germany. You can find whatever available record in Berlin today
regardless if it was Prussia, Imperial Germany, Natzi Germany, East Germany or
West Germany or Occupied American Sector, French Sector, or British Sector, or
Federal Rpublic of Germany. This junk belongs in the notes not in the primary
entry.

Hoosierly yours,

James G. Hermsen

8108 Laura Lynne Lane

Indianapolis, IN 46217

317-679-1466 cell

317-881-4600 land line

On ‎Saturday‎, ‎August‎ ‎03‎, ‎2019‎ ‎09‎:‎22‎:‎00‎ ‎AM‎ ‎EDT, Christopher
Seward Sr <mailto:csewar...@gmail.com> <csewar...@gmail.com> wrote:

James, I understand where you're coming from. I just think that handling data
in a manner that deviates from the standard is inviting data integrity issues.
As I said, the choice is yours. Just be aware of the lasting issues it will
cause for those who come after.

Christopher

On Sat, Aug 3, 2019, 4:59 AM James G. Hermsen via LegacyUserGroup
<legacyusergroup@legacyusers.com <mailto:legacyusergroup@legacyusers.com> >
wrote:

Exactly my point. Putting historical location in the notes maintains all the
information one needs and still be sensible and useful to family members. If
people import information without looking at the notes, then they are not being
a good genealogist. It tells me that they just copy things for numbers, not
for reliable and useful information to share.

Hoosierly yours,

James G. Hermsen

8108 Laura Lynne Lane

Indianapolis, IN 46217

317-679-1466 cell

317-881-4600 land line

On ‎Friday‎, ‎August‎ ‎02‎, ‎2019‎ ‎08‎:‎51‎:‎50‎ ‎AM‎ ‎EDT, Bill Hoff
<bh...@mchsi.com <mailto:bh...@mchsi.com> > wrote:

Then one cannot find on a map if historic locations used. With many relatives
in West Virginia I have this problem. WV did not become a state until June 20,
1863. On top of that many counties within the state were divided over many
years, far too many for me to recall them all. Then there is the problem of
knowing locations but not dates so one cannot be certain of entries

Bill

Sent from my iPhone

On Aug 1, 2019, at 8:15 PM, Christopher Seward Sr. <csewar...@gmail.com
<mailto:csewar...@gmail.com> > wrote:

You are free to record as you choose, but keep in mind that if you publish &
share this information, your method goes against the standard, and can cause
issues.

An example for me was importing a person's info into my file. I kept getting
import errors stating the the location (birth place) did not exist on that date
(birth date). Now I have an issue, since this place not only didn't exist when
this person was born, but when it did exist, it was in a different country than
when he was born, thus making him appear to be of one heritage, but was
actually another.

I recommend ALWAYS putting the correct location in, and putting the current
name of the location in the notes.

On 8/1/2019 4:41 PM, James G. Hermsen via LegacyUserGroup wrote:

Yes, but in the notes. Most people I share my information with want to know
where the place is now. They, like Trump, have no regard for history, and
those who know their history, already know what the original name is. Looking
for documents, the current place will know what jurisdiction they once were
governed by. It is all about being usable for current people. Otherwise, we
would all be recording everying in Latin like they once did.

Hoosierly yours,

James G. Hermsen

8108 Laura Lynne Lane

Indianapolis, IN 46217

317-679-1466 cell

317-881-4600 land line

On ‎Thursday‎, ‎August‎ ‎01‎, ‎2019‎ ‎01‎:‎22‎:‎29‎ ‎PM‎ ‎EDT,
sarrazingeor...@gmail.com <mailto:sarrazingeor...@gmail.com>
<mailto:sarrazingeor...@gmail.com> <sarrazingeor...@gmail.com> wrote:

I think one should always the name of a location the way it is indicated in the
documentation.

If the name has change or if two locations have been merge, I use curly
brackets with the new name after the old name.

Ex. Romorantin {Romorantin-Lanthenay}, 41194, Loir-et-Cher, Centre-Val de
Loire, France

(Note : I use 5 fields)

Georges

De : LegacyUserGroup <mailto:legacyusergroup-boun...@legacyusers.com>
<legacyusergroup-boun...@legacyusers.com> De la part de James G. Hermsen via
LegacyUserGroup
Envoyé : 1 août 2019 09:26
À : mvmcgrs--- via LegacyUserGroup <mailto:legacyusergroup@legacyusers.com>
<legacyusergroup@legacyusers.com>
Cc : James G. Hermsen <mailto:jherm...@yahoo.com> <jherm...@yahoo.com>
Objet : Re: [LegacyUG] Location names for Pennsylvania

I always use the current geographic location and name today in each entry and
in the notes, remark that the geographic name and country was different then
than it is today. That way when a grandchild (or anyone) wants to find the
place on a map is able to do so. Prussia is very hard to find, if you did not
know where to look. Same thing with names of cities whose name has changed.
Stalingrad, Linengrad don't make sense for someone born after the Cold War.
Peking vs. Bejing. Same thing.

Hoosierly yours,

James G. Hermsen

8108 Laura Lynne Lane

Indianapolis, IN 46217

317-679-1466 cell

317-881-4600 land line

On ‎Thursday‎, ‎August‎ ‎01‎, ‎2019‎ ‎08‎:‎43‎:‎54‎ ‎AM‎ ‎EDT, mvmcgrs--- via
LegacyUserGroup <legacyusergroup@legacyusers.com
<mailto:legacyusergroup@legacyusers.com> > wrote:

I hope you are not inserting the the added information if it is not in the
document. The jurisdictions change over time. In the US what was a county in
1850 may be another county in 1860 and still another county by 1870. The house
did not move but the boundaries did.

Marie

Marie Varrelman Melchiori, Certified Genealogist Emeritus
______________________________ ______________________________ __
CG or Certified Genealogist is a service mark of the Board for Certification of
Genealogists, used under license by Board-certified genealogists after periodic
competency evaluation, and the board name is registered in the US Patent &
Trademark Office.

In a message dated 8/1/2019 6:24:51 AM Eastern Standard Time,
wrlinh...@gmail.com <mailto:wrlinh...@gmail.com> writes:

I do agree.

My standard is: [1. local jurisdiction/repository i.e.township, village,
city, etc], 2.County, 3.State, 4.Country

and apply to other countries similarly by always using three commas for all
locations [usually each has a repository of genealogical data] . The entry
might between comma's might be null if I don't have the information. For
example born in USA might be ", , , USA". I know I have some research to do
but I only record what I have from that source.

For folder hierarchy and some naming situations I reverse the order but always
hold to 4 elements for location. I don't believe I have ever had an exception.
I am sure I will learn about one here. So far this works for me.

Bill

On Wed, Jul 31, 2019 at 12:20 AM Roberta Schwalm <robertaschw...@gmail.com
<mailto:robertaschw...@gmail.com> > wrote:

I do the same thing, Shirley. Most of my ancestors are from Scotland, Ireland,
England, Germany and a spattering of French. The only difference is I use
"province" instead of State.

On Tue, Jul 30, 2019 at 9:05 PM Shirley Crampton <scshenders...@gmail.com
<mailto:scshenders...@gmail.com> > wrote:

I use Village, County, State, Country. Hopefully there is no more than 1
village of the same name in the County. If the place is rural then I put the
name of the township in the first position.

On Tue, Jul 30, 2019 at 5:47 PM Connie Laubach <bluecorab...@gmail.com
<mailto:bluecorab...@gmail.com> > wrote:

Trying to decide how to input the location names – I have townships that are
made up of villages and boroughs. How are others handling it?

I have thought of the following:

Village, township, county, state, United States

township-village, country, state, United States (I like this as all villages
within the township would be listed together)

Thank you, Connie.

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com <mailto:LegacyUserGroup@legacyusers.com>
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>

Virus-free.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
www.avast.com

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Location names for Pennsylvania

Reply via email to