Jerry, with respect you are doing the very thing that I suggest is wrong. You are correct in the the UK is a Kingdom, an alliance, and not a country, as I said in my reply to Scott. But it is equally wrong to put a comma after a county, there isn't a layer between a county and the country. It is simply Southampton, Hampshire, England.
Yes, this causes a problem with the Global-Locator, but so be it. I prefer my locations to be accurate. If I really get stuck on a location and need to use the Global-Locator then I do put "UK" at the end - and then remove it as soon as I identified the place. However the place which I have problems with are usually too small to be on the maps, or disappeared years ago! Ron Ferguson http://www.fergys.co.uk/ From: Jerry Sent: Wednesday, September 29, 2010 4:56 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES Scott, I'm interested in what Ron will have to say on that also. But a lot of us use Legacy to maintain our database, but also use something akin to TNG - The Next Generation of Genealogy Sitebuilding to create a website. With TNG, place names are sorted according to the divisions used, separated by commas, but I believe you could use however many divisions you want. But if you were to use: Southhampton, Hampshire County, England, UK Chicago, Cook County, Illinois, USA The result would be that England would sort with Illinois in a place list. Ron, I'm just wondering why you would even want to put UK there at all? (It's a kingdom, not a country, right?)   Anyway, I've been putting: Southampton, Hampshire County, , England (Whether you actually have States in England, I don't know, but by using a blank division between commas, I force the list to put all the countries together in the alphabetical place list. Just another thought...   --Jerry On 9/29/2010 11:33 AM, Scott Hall wrote: Ron:  Good information in that blog ... thanks for linking to it. A question, though ... why is the addition of "UK" at the end of the location unacceptable? Couldn't one write, in your example, "Southampton, Hampshire, England, United Kingdom" in that the city of Southampton is in Hampshire County, in the country of England, which is part of the United Kingdom? I wonder if you're being too rigid that the the "thrid comma" must be state.  In my database, I've opted to use descriptors, for example: Muncy Borough, Lycoming County, Pennsylvania, USA as opposed to Muncy, Lycoming County, Pennsylvania, USA. I do this because, in this case there are two Muncys -- Muncy Township and Muncy Borough, so just saying "Muncy" gives you no clue as to which one I am referring. For places that have an even lower level, such as a village within a town, I sometimes use five commas like Manchester (village), Manchester (town), Ontario County, New York, USA, although I suppose one could simply eliminate the town and stick to the four comma approach.  Anyway, for Southampton, my file would show Southamption (city), Hampshire County, England, UK. This doesn't mean that England is a state, which it is not, just that it is a component of the UK.  Thoughts?  Scott On Wed, Sep 29, 2010 at 4:32 AM, Ron Ferguson <ronfergy....@tiscali.co.uk> wrote: Jerry, Please let us be clear, "fields that are really designed only for the traditional LOCATION / PLACE divisions." These fields are not traditional. They are based, as I have said previously, on an artificial convention which arranged for a location to comprise 4 fields. Whilst this works in many/most American locations it is not suitable for the UK and most of the rest of the world. In fact for constituent countries of the United Kingdom and Great Britain, as used actually gives a false output. You may wish to look at my blog at http://bit.ly/8VDqTc where I describe how to *accurately* record British locations, instead of getting them wrong by forcing them into the American 4 field convention. BTW. On LUG it has been reported several times that the convention does not work for all American locations either. The location field works perfectly well when containing a full location/address, especially if set to read from right to left. Where one may find a problem is using the Geo-Locator which uses incorrect locations for all of the UK. Ron Ferguson http://www.fergys.co.uk/ From: Jerry Sent: Wednesday, September 29, 2010 5:09 AM To: LegacyUserGroup@LegacyUsers.com Subject: [LegacyUG] PLACE NAMES For what it's worth, my opinion is to use the BURIED field only as a location field such as Detroit, Wayne Co, Michigan, USA - then add the name of the cemetery in the NOTES field next to the BURIED location field. Otherwise, you will get LOCATION names that refer to CEMETERIES and not CITIES, VILLAGES, TOWNSHIPS, etc.  The LOCATION fields are much more manageable not to mix them up with CEMETERY names.....IMO.  Plus, if you ever use TNG - The Next Generation of Genealogy Sitebuilding for your website data, you will have very messy PLACE names if you use CEMETERIES in fields that are really designed only for the traditional LOCATION / PLACE divisions. Jerry On 9/28/2010 10:41 PM, Jacki Richey wrote: Tim, why do you create a 'burial' event when Legacy has a place for "buried" right after "died"? > From: spa...@xmission.com > Jenny, > > Would one enter the Cemetery like this ? > > Forrest Lawn Cemetery, L. Street, Plot 5.4, Cypress, Orange, California, > USA > > I'm like Sherry. I create a 'Burial' event. > > Tim > > On 27/09/2010 19:13, Sherry/Support wrote: > >> I enter the cemetery name as an Event. That's easy to search and > >> create reports on. Some users enter the cemetery name and address info > >> using the Address feature for the Burial field. Click on the "+" at > >> the end of the field to enter the event address. > > > > And some of us enter the cemetery name as part of the location. Indeed, > > I include not only the cemetery name but also the plot/grave number when > > I know it. > > > > What's best is what works for you! 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
