The French group has already modified its toponym database to make the
locations names consistent with our terminology.
For example, for France, we use five fields : City, City code, Department,
Region, Country.
We also developed a system to take ancient names into consideration. We use
{}.
So we have Old City Name {New City Name}, City code, Department, Region,
Country.
We also use () to add note to a location, i.e. (church name, castle name,
etc.); City (Castle name), City code, Department, Region, Country.
All of these changes have already been made for France, Belgiium and Québec
Canada.
Georges
De : LegacyUserGroup [mailto:[email protected]] De la
part de CE WOOD
Envoyé : 12 avril 2017 22:28
À : Legacy User Group <[email protected]>
Objet : Re: [LegacyUG] alternate name index
That's not what I mean. When you enter a name, you are able to enter myriad
alternate names for the same person. Click on any of those names, and you
are taken to the same person. That facility exists in Access (upon which
Legacy is based). It could just as easily be applied to Locations. It would
solve so many problems.
I have many thousands medieval persons in my database, all of whom have
multiple names, titles, et alia. Medieval documents refer to person by
titles, alternate spellings were common, etc. I can enter all of those names
as alternate names. They appear in the Index. I have "England, King of", for
instance and can instantly see all of them. Same for Earls, Counts, Dukes,
whatever. That could be done with the Location Index, if Legacy only would
do so.
CE
_____
From: LegacyUserGroup < <mailto:[email protected]>
[email protected]> on behalf of Ian Thomas <
<mailto:[email protected]> [email protected]>
Sent: Wednesday, April 12, 2017 7:01 PM
To: Legacy User Group
Subject: [LegacyUG] alternate name index
Unfortunately, I think the creation of an alternate name index would be a
never-ending task. Also, ever-changing?
Ian Thomas
Albert Park, Victoria 3206 Australia
From: LegacyUserGroup [mailto:[email protected]] On
Behalf Of Jane Linkswiler
Sent: Thursday, 13 April 2017 11:47 AM
To: 'Legacy User Group' <[email protected]
<mailto:[email protected]> >
Subject: Re: [LegacyUG] Place names - olde vs current
Sounds like a great idea for the suggestion box.
Jane in Phoenix
From: LegacyUserGroup [mailto:[email protected]] On
Behalf Of CE WOOD
Sent: Wednesday, April 12, 2017 6:35 PM
To: Legacy User Group <[email protected]
<mailto:[email protected]> >
Subject: Re: [LegacyUG] Place names - olde vs current?
It's a real shame that Legacy does not use the same Access ability and
create an alternate location index as they have done for the alternate name
index. It would be SOOOOOOOO helpful!
CE
_____
From: LegacyUserGroup <[email protected]
<mailto:[email protected]> > on behalf of Ian Thomas
<[email protected] <mailto:[email protected]> >
Sent: Wednesday, April 12, 2017 5:43 PM
To: Legacy User Group
Subject: Re: [LegacyUG] Place names - olde vs current?
Cathy
Thanks for the information; I had noticed some posts here about reverse
sorting addresses, but I didnt think it applied to my situation. And I do
occasionally correct the mapping / Bing Maps positioning for locations
that end up in the wrong continent, etc. But not for the historic place
naming.
Also, I should use the additional description you cited for
Newcastle/Toodyay the (now Toodyay) is more explicit than how I have
been doing it.
I would like to include the farm/property names - Summerhill, New Norcia,
Western Australia, Australia but I have been putting this in Notes or a
residence event, assuming that the quotes and specific property names would
guarantee that the location couldnt be found by Bing Maps.
The article you referred to is good I hadnt seen it.
Also, Brian Kellys suggestion for positioning is a very logical method for
registering the historic location name at essentially the location of the
currently-used name for the location. Thanks, Brian.
Ian Thomas
Albert Park, Victoria 3206 Australia
From: LegacyUserGroup [mailto:[email protected]] On
Behalf Of Cathy Pinner
Sent: Wednesday, 12 April 2017 7:59 PM
To: Legacy User Group <[email protected]
<mailto:[email protected]> >
Subject: Re: [LegacyUG] Place names - olde vs current?
Ian,
You can plot anything on the Bing maps in Legacy. Just highlight the
location you are mapping then right click on the map to put the pin in the
right place.
I include addresses, including farm names like your examples, in my
locations. Others don't.
Because I do this I always sort my location list from right to left when I
need places close to each other together on the list.
RE recording historical names. You might want to read this for one
suggestion.
<http://support.legacyfamilytree.com/article/AA-01014>
http://support.legacyfamilytree.com/article/AA-01014
Sometimes I simply put the current name in brackets.
Newcastle (now Toodyay), Western Australia, Australia.
Cathy
Ian Thomas wrote:
Whats the best practice for preserving the older place names while
still mapping them accurately?
An Australian example, the current t on of Toodyay near Perth in
Western Australia was known as Newcastle, and I have some people with
that connection, around the late 1800s.
Also commonly used by country people then and now, is their property
name (pastoral/grazing/cropping, etc) for example, Summerhill, New
Norcia, Western Australia, Australia (or, Pankee also close to New
Norcia). I tend to record as shown, but I lose the ability to place
them geographically via Legacy.
Ian Thomas
Albert Park, Victoria 3206 Australia
--
LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/
