Re: [LegacyUG] Place names - olde vs current
What I'd like to see is the ability to link locations, and have dates associated with locations. That way, you can have the progression of a location throughout history easily visible. If you have the location listed one way, but put in a date where it should have a different 'name' at that time, Legacy could recognize it due to the linked dated locations and then auto-correct. By historical progression, for example Bethabara, Rowan County, North Carolina Colony, British North America is where some of my ancestors lived in the 1750's (and beyond). That same location is now within the city of Winston-Salem, Forsyth County, North Carolina, United States. Every level of jurisdiction has changed (if only because state level changed from colony to state) - and more than once on the county level. The following are all the same location, in a historical progression: 1753-1771 - Bethabara, Rowan County, North Carolina Colony, British North America 1771-1776 - Salem, Surry County, North Carolina Colony, British North America [they actually built a new town nearby, and all villagers moved there. The county coincidentally changed in the same year.] 1776-1789 - Salem, Surry County, North Carolina, United States 1789-1849 - Salem, Stokes County, North Carolina, United States 1849-1913 - Salem, Forsyth County, North Carolina, United States 1913-today - Winston-Salem, Forsyth County, North Carolina, United States This is not to say I expect the Legacy team to expand the Geo Locations to include all historical names. Rather, I'd like the locations expanded to include dates that users can add, and then the ability to link them. Getting historical accuracy could be helped with forums or Facebook queries if a person is stuck and cannot find an answer online (which is where I look). Thank you, Trevor Carlson Edmonton, AB From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Jane Linkswiler Sent: 12-Apr-17 7:47 PM To: 'Legacy User Group' Subject: Re: [LegacyUG] Place names - olde vs current Sounds like a great idea for the suggestion box. Jane in Phoenix From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of CE WOOD Sent: Wednesday, April 12, 2017 6:35 PM To: Legacy User Group <legacyusergroup@legacyusers.com> 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 S helpful! CE _ From: LegacyUserGroup <legacyusergroup-boun...@legacyusers.com> on behalf of Ian Thomas <il.tho...@outlook.com> 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 didn't 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 couldn't be found by Bing Maps. The article you referred to is good - I hadn't seen it. Also, Brian Kelly's 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:legacyusergroup-boun...@legacyusers.com] On Behalf Of Cathy Pinner Sent: Wednesday, 12 April 2017 7:59 PM To: Legacy User Group <legacyusergroup@legacyusers.com> 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: What's the best practice for preserving the older plac
Re: [LegacyUG] Place names - olde vs current
Sounds like a great idea for the suggestion box. Jane in Phoenix From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of CE WOOD Sent: Wednesday, April 12, 2017 6:35 PM To: Legacy User Group <legacyusergroup@legacyusers.com> 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 S helpful! CE _ From: LegacyUserGroup <legacyusergroup-boun...@legacyusers.com <mailto:legacyusergroup-boun...@legacyusers.com> > on behalf of Ian Thomas <il.tho...@outlook.com <mailto:il.tho...@outlook.com> > 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 didn't 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 couldn't be found by Bing Maps. The article you referred to is good - I hadn't seen it. Also, Brian Kelly's 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:legacyusergroup-boun...@legacyusers.com] On Behalf Of Cathy Pinner Sent: Wednesday, 12 April 2017 7:59 PM To: Legacy User Group <legacyusergroup@legacyusers.com <mailto:legacyusergroup@legacyusers.com> > 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: What's 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 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] 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 S helpful! CE From: LegacyUserGroup <legacyusergroup-boun...@legacyusers.com> on behalf of Ian Thomas <il.tho...@outlook.com> 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 didn’t 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 couldn’t be found by Bing Maps. The article you referred to is good – I hadn’t seen it. Also, Brian Kelly’s 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:legacyusergroup-boun...@legacyusers.com] On Behalf Of Cathy Pinner Sent: Wednesday, 12 April 2017 7:59 PM To: Legacy User Group <legacyusergroup@legacyusers.com> 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 Sometimes I simply put the current name in brackets. Newcastle (now Toodyay), Western Australia, Australia. Cathy Ian Thomas wrote: What’s 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 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] Place names - olde vs current?
Cathy Thanks for the information; I had noticed some posts here about reverse sorting addresses, but I didn’t 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 couldn’t be found by Bing Maps. The article you referred to is good – I hadn’t seen it. Also, Brian Kelly’s 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:legacyusergroup-boun...@legacyusers.com] On Behalf Of Cathy Pinner Sent: Wednesday, 12 April 2017 7:59 PM To: Legacy User Group <legacyusergroup@legacyusers.com> 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 Sometimes I simply put the current name in brackets. Newcastle (now Toodyay), Western Australia, Australia. Cathy Ian Thomas wrote: What’s 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 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] Place names - olde vs current?
You can always manually place the icon using right click on the correct spot after dragging the map to the correct place. My trick when a place will not plot correctly is to temporarily edit the name to get legacy to plot the place near where I want. So for your first case I would temporarily change the name to Tooyay and have Legacy Geocode the place. Once the place is correctly plotted I would edit the name to Newcastle. You can do something similar for the properties, give a place name near by, have Legacy plot it, drag the map to the property location then right click to have Legacy change the icon position. Brian Kelly On 12-Apr-17 3:40 AM, Ian Thomas wrote: What's the best practice for preserving the older place names while still mapping them accurately? An Australian example, the current ton 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 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] 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 Sometimes I simply put the current name in brackets. Newcastle (now Toodyay), Western Australia, Australia. Cathy Ian Thomas wrote: What’s the best practice for preserving the older place names while still mapping them accurately? An Australian example, the current ton 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 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] Place names - olde vs current?
Does sorting locations country first help at all? Jane in Phoenix From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Ian Thomas Sent: Wednesday, April 12, 2017 12:41 AM To: legacyusergroup@legacyusers.com Subject: [LegacyUG] Place names - olde vs current? What's the best practice for preserving the older place names while still mapping them accurately? An Australian example, the current ton 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 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/
[LegacyUG] Place names - olde vs current?
What's the best practice for preserving the older place names while still mapping them accurately? An Australian example, the current ton 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 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] Place names sorting
When people ask I always tell them there is no one way of doing anything (only the best and most intuitive for you). The two key points are (1) know what the output will look like - how do you want to use your reports, charts, etc. - and then tweak the input to accomplish it; and (2) be consistent - when you make a decision, make a note of it and have your cheatsheet so you know your process or workflow. Finally (and this is the bonus) we own our programs, they don't own us - make conscious decisions, test the parameters, and use your program so that it works for you. Tessa *Tessa Keough* *Guild of One-Name Studies, **Keough (Keogh, Kough Kehoe) Registered ONS* *Legacy Virtual Users' Group Community on Google+* *Society for One-Place Studies - Plate Cove East, Newfoundland * On Sat, Feb 21, 2015 at 5:42 AM, Cathy Pinner genea...@gmail.com wrote: Hi Jenny, That's exactly why I don't use the Address fields except for repositories and mailing addresses. We each have to decide which standards we will follow and why. If we don't follow some accepted standard we need to know what the consequences are. In this case one of the consequences is much better output. We still need to be consistent. Cathy SNIP 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
RE: [LegacyUG] Place names sorting
Excellent, Tessa! Michele Technical Support mailto:mich...@legacyfamilytree.com mich...@legacyfamilytree.com http://www.legacyfamilytree.com www.legacyfamilytree.com From: Tessa Keough [mailto:murke...@gmail.com] Sent: Saturday, February 21, 2015 10:13 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Place names sorting When people ask I always tell them there is no one way of doing anything (only the best and most intuitive for you). The two key points are (1) know what the output will look like - how do you want to use your reports, charts, etc. - and then tweak the input to accomplish it; and (2) be consistent - when you make a decision, make a note of it and have your cheatsheet so you know your process or workflow. Finally (and this is the bonus) we own our programs, they don't own us - make conscious decisions, test the parameters, and use your program so that it works for you. Tessa 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
On 21/02/2015 01:27, Jay Wilpolt wrote: What they were saying is that in the Burial Place field, we should NOT put the name of the cemetery, but instead put that in the Burial Place address which is the field accessed by the + sign The reason I do not do that (but put the complete address in the Location field) is that I don't like the way Locations and Addresses appear in reports if one enters them separately. Using the Address field, one gets something like Joe Bloggs was buried in Barnton, Cheshire, England (Christ Church Churchyard) or even - if one fills in the complete Address which seems like a sensible thing to do in some ways) Joe Bloggs was buried in Barnton, Cheshire, England (Christ Church Churchyard, Barnton, Cheshire, England). I prefer to see Joe Bloggs was buried in Christ Church Churchyard, Barnton, Cheshire, England. I don't have a problem with having thousands of locations or with sorting them. -- Jenny M Benson 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
Well said Tessa! Marie Marie Varrelman Melchiori Melchiori Research Services, L.L.C. In a message dated 2015-02-21 11:16:52 A.M. Eastern Standard Time, mich...@legacyfamilytree.com writes: From: Tessa Keough [mailto:murke...@gmail.com] Sent: Saturday, February 21, 2015 10:13 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Place names sorting When people ask I always tell them there is no one way of doing anything (only the best and most intuitive for you). The two key points are (1) know what the output will look like - how do you want to use your reports, charts, etc. - and then tweak the input to accomplish it; and (2) be consistent - when you make a decision, make a note of it and have your cheatsheet so you know your process or workflow. Finally (and this is the bonus) we own our programs, they don't own us - make conscious decisions, test the parameters, and use your program so that it works for you. Tessa 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
Hi Jenny, That's exactly why I don't use the Address fields except for repositories and mailing addresses. We each have to decide which standards we will follow and why. If we don't follow some accepted standard we need to know what the consequences are. In this case one of the consequences is much better output. We still need to be consistent. Cathy Jenny M Benson wrote: On 21/02/2015 01:27, Jay Wilpolt wrote: What they were saying is that in the Burial Place field, we should NOT put the name of the cemetery, but instead put that in the Burial Place address which is the field accessed by the + sign The reason I do not do that (but put the complete address in the Location field) is that I don't like the way Locations and Addresses appear in reports if one enters them separately. Using the Address field, one gets something like Joe Bloggs was buried in Barnton, Cheshire, England (Christ Church Churchyard) or even - if one fills in the complete Address which seems like a sensible thing to do in some ways) Joe Bloggs was buried in Barnton, Cheshire, England (Christ Church Churchyard, Barnton, Cheshire, England). I prefer to see Joe Bloggs was buried in Christ Church Churchyard, Barnton, Cheshire, England. I don't have a problem with having thousands of locations or with sorting them. 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
You are asking for a Genealogy program to perform the function of a Data Manipulation program. To get the results you desire, export the data to csv and then use a data spreadsheet type program to manipulate your data. On Thu, Feb 19, 2015 at 10:47 PM, kaytt ka...@sasktel.net wrote: I have been using Legacy since Version 2 and I'm still struggling with finding a way to enter place names to show everything I want in a written report but have them sort properly in the list. My problem is that sometimes I have only 3 names with separating comas and sometimes 5. If I do a reverse sort: Country, State, County, City it's a mess. For example-- 3 places separated by comas: Kirk Maughold Cemetery, Maughold, Isle of Man (Isle of man is it's own country and not part of England as the Manx are quick to point out). sorts to - , Isle of Man, Maughold, Kirk Maughold 5 places separated by comas: Elmwood Cemetery, Kansas City, Jackson County, Missouri, USA. sorts to: Missouri, Jackson County, Kansas City, Elmwood Cemetery, USA Regina, Saskatchewan, Canada sorts to: , Canada, Saskatchewan, Regina. Most provinces in Canada do not have counties so almost everything is 3 places unless a cemetery is added to take up the 4th space. Any suggestions or creative ideas would be most welcome. My biggest concern is the sorting. If I want to make a list of people buried in various cemeteries in Kansas City, MO, I'd like to find them grouped together in the sort list rather than have to scroll through and try picking them out. USA, Missouri, Jackson County, Kansas City, cemetery A USA, Missouri, Jackson County, Kansas City, cemetery B USA, Missouri, Jackson County, Kansas City, cemetery C I hope I've explained this in a clear manner. Thanks, Kathy 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
I should add here my own idea that I hope might someday be implemented to resolve many place name issues. First, lets break down the place field into the individual components. A field for Country a field for State a field for County a field for Name Then lets add another set of fields to help us manage places that are not municipalities. probably 3 fields would suffice for most any applications Field 1 might contain a name like ; St. Mary's Catholic Church field 2 might contain the address : 123 Main Street Field 3 might contain a place type maybe 1 for cemetery, 2 for church, 3 for hospital, 4 for residence. When exporting data to a gedcom, we would mash all the 5 fields (but not the type) St. Marys Catholic Church, 123 Main st., Chicago, Cook, Illinois, USA Importing data might be more difficult, but we know we can take countries and states and match to the known possibilities. We could also then set user defaults for which fields are displayed. Hopefully, eventually Legacy will implement something like this to help us all manage our places better. Thanks Jay On Thu, Feb 19, 2015 at 10:47 PM, kaytt ka...@sasktel.net wrote: I have been using Legacy since Version 2 and I'm still struggling with finding a way to enter place names to show everything I want in a written report but have them sort properly in the list. My problem is that sometimes I have only 3 names with separating comas and sometimes 5. If I do a reverse sort: Country, State, County, City it's a mess. For example-- 3 places separated by comas: Kirk Maughold Cemetery, Maughold, Isle of Man (Isle of man is it's own country and not part of England as the Manx are quick to point out). sorts to - , Isle of Man, Maughold, Kirk Maughold 5 places separated by comas: Elmwood Cemetery, Kansas City, Jackson County, Missouri, USA. sorts to: Missouri, Jackson County, Kansas City, Elmwood Cemetery, USA Regina, Saskatchewan, Canada sorts to: , Canada, Saskatchewan, Regina. Most provinces in Canada do not have counties so almost everything is 3 places unless a cemetery is added to take up the 4th space. Any suggestions or creative ideas would be most welcome. My biggest concern is the sorting. If I want to make a list of people buried in various cemeteries in Kansas City, MO, I'd like to find them grouped together in the sort list rather than have to scroll through and try picking them out. USA, Missouri, Jackson County, Kansas City, cemetery A USA, Missouri, Jackson County, Kansas City, cemetery B USA, Missouri, Jackson County, Kansas City, cemetery C I hope I've explained this in a clear manner. Thanks, Kathy 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
Hi Kathy, Your problem is that you are choosing the wrong sorting option. Unless you strictly enter locations in the town, county, state, country format which appears to suit most of the USA but doesn't suit most of my locations, then you need to use the Right to Left sort. Then so long as you enter your information consistently from smallest unit to largest unit/country, then the bits will sort together. I include streets etc in my locations and by sorting right to left every location in a particular town comes together. Then the relevant items can all be highlighted by clicking on the first in the list and holding down shift when you click on the last. Then use the Options button and Show List to get everyone associated with that location. I did it this morning to get a list of everyone in my file associated with Wiltshire as there are new Wiltshire records available at FindMyPast. Once you've chosen a Right to Left sort, then you can change the direction of the locations in the list just by ticking or unticking the Sort checkbox. You don't have to click the Sort button ever again. However, while you are there, before you choose right to left you might want to choose Generic terms instead of USA terms. Cathy kaytt wrote: I have been using Legacy since Version 2 and I'm still struggling with finding a way to enter place names to show everything I want in a written report but have them sort properly in the list. My problem is that sometimes I have only 3 names with separating comas and sometimes 5. If I do a reverse sort: Country, State, County, City it's a mess. For example-- 3 places separated by comas: Kirk Maughold Cemetery, Maughold, Isle of Man (Isle of man is it's own country and not part of England as the Manx are quick to point out). sorts to - , Isle of Man, Maughold, Kirk Maughold 5 places separated by comas: Elmwood Cemetery, Kansas City, Jackson County, Missouri, USA. sorts to: Missouri, Jackson County, Kansas City, Elmwood Cemetery, USA Regina, Saskatchewan, Canada sorts to: , Canada, Saskatchewan, Regina. Most provinces in Canada do not have counties so almost everything is 3 places unless a cemetery is added to take up the 4th space. Any suggestions or creative ideas would be most welcome. My biggest concern is the sorting. If I want to make a list of people buried in various cemeteries in Kansas City, MO, I'd like to find them grouped together in the sort list rather than have to scroll through and try picking them out. USA, Missouri, Jackson County, Kansas City, cemetery A USA, Missouri, Jackson County, Kansas City, cemetery B USA, Missouri, Jackson County, Kansas City, cemetery C I hope I've explained this in a clear manner. Thanks, Kathy 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
Jay, maybe OK for the States, but no good fir many other countries. Ron Ferguson Jay Wilpolt jaywilp...@aol.com wrote: I should add here my own idea that I hope might someday be implemented to resolve many place name issues. First, lets break down the place field into the individual components. A field for Country a field for State a field for County a field for Name Then lets add another set of fields to help us manage places that are not municipalities. probably 3 fields would suffice for most any applications Field 1 might contain a name like ; St. Mary's Catholic Church field 2 might contain the address : 123 Main Street Field 3 might contain a place type maybe 1 for cemetery, 2 for church, 3 for hospital, 4 for residence. When exporting data to a gedcom, we would mash all the 5 fields (but not the type) St. Marys Catholic Church, 123 Main st., Chicago, Cook, Illinois, USA Importing data might be more difficult, but we know we can take countries and states and match to the known possibilities. We could also then set user defaults for which fields are displayed. Hopefully, eventually Legacy will implement something like this to help us all manage our places better. Thanks Jay On Thu, Feb 19, 2015 at 10:47 PM, kaytt ka...@sasktel.net wrote: I have been using Legacy since Version 2 and I'm still struggling with finding a way to enter place names to show everything I want in a written report but have them sort properly in the list. My problem is that sometimes I have only 3 names with separating comas and sometimes 5. If I do a reverse sort: Country, State, County, City it's a mess. For example-- 3 places separated by comas: Kirk Maughold Cemetery, Maughold, Isle of Man (Isle of man is it's own country and not part of England as the Manx are quick to point out). sorts to - , Isle of Man, Maughold, Kirk Maughold 5 places separated by comas: Elmwood Cemetery, Kansas City, Jackson County, Missouri, USA. sorts to: Missouri, Jackson County, Kansas City, Elmwood Cemetery, USA Regina, Saskatchewan, Canada sorts to: , Canada, Saskatchewan, Regina. Most provinces in Canada do not have counties so almost everything is 3 places unless a cemetery is added to take up the 4th space. Any suggestions or creative ideas would be most welcome. My biggest concern is the sorting. If I want to make a list of people buried in various cemeteries in Kansas City, MO, I'd like to find them grouped together in the sort list rather than have to scroll through and try picking them out. USA, Missouri, Jackson County, Kansas City, cemetery A USA, Missouri, Jackson County, Kansas City, cemetery B USA, Missouri, Jackson County, Kansas City, cemetery C I hope I've explained this in a clear manner. Thanks, Kathy 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
RE: [LegacyUG] Place names sorting
As long as you are consistent with how many fields you use for each country your Master Location List will sort the countries together properly. For example, I use 4 fields for US, I use 3 for Germany, I use 4 for Poland and I use 6 for France. I have no problem with sorting. Where you run into problems is when you are not consistent within a country. Also, addresses and names of building do not belong in the location field. These belong in the address field. Michele Technical Support mailto:mich...@legacyfamilytree.com mich...@legacyfamilytree.com http://www.legacyfamilytree.com www.legacyfamilytree.com 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
So long as you are consistent and always end with the country, there isn't a problem. Just sort right to left and the places come together whether or not you want who lived in a particular town or county or country (or street) Michelle says addresses don't belong in the location. However. I've always put the address in the location and it works fine for me and many others. I don't like the way addresses report and you either enter incomplete addresses or get a repetition when you use the address field. I think there are other problems as well. Also I know addresses can now be mapped in Legacy 8 but I could map mine in Legacy 7. Jay, you can do that now if you want to use the 7 of the available 9 fields. Cathy ronfergy@tiscali.co.uk wrote: Jay, maybe OK for the States, but no good fir many other countries. Ron Ferguson Jay Wilpolt jaywilp...@aol.com wrote: I should add here my own idea that I hope might someday be implemented to resolve many place name issues. First, lets break down the place field into the individual components. A field for Country a field for State a field for County a field for Name Then lets add another set of fields to help us manage places that are not municipalities. probably 3 fields would suffice for most any applications Field 1 might contain a name like ; St. Mary's Catholic Church field 2 might contain the address : 123 Main Street Field 3 might contain a place type maybe 1 for cemetery, 2 for church, 3 for hospital, 4 for residence. When exporting data to a gedcom, we would mash all the 5 fields (but not the type) St. Marys Catholic Church, 123 Main st., Chicago, Cook, Illinois, USA Importing data might be more difficult, but we know we can take countries and states and match to the known possibilities. We could also then set user defaults for which fields are displayed. Hopefully, eventually Legacy will implement something like this to help us all manage our places better. Thanks Jay On Thu, Feb 19, 2015 at 10:47 PM, kaytt ka...@sasktel.net mailto:ka...@sasktel.net wrote: I have been using Legacy since Version 2 and I'm still struggling with finding a way to enter place names to show everything I want in a written report but have them sort properly in the list. My problem is that sometimes I have only 3 names with separating comas and sometimes 5. If I do a reverse sort: Country, State, County, City it's a mess. For example-- 3 places separated by comas: Kirk Maughold Cemetery, Maughold, Isle of Man (Isle of man is it's own country and not part of England as the Manx are quick to point out). sorts to - , Isle of Man, Maughold, Kirk Maughold 5 places separated by comas: Elmwood Cemetery, Kansas City, Jackson County, Missouri, USA. sorts to: Missouri, Jackson County, Kansas City, Elmwood Cemetery, USA Regina, Saskatchewan, Canada sorts to: , Canada, Saskatchewan, Regina. Most provinces in Canada do not have counties so almost everything is 3 places unless a cemetery is added to take up the 4th space. Any suggestions or creative ideas would be most welcome. My biggest concern is the sorting. If I want to make a list of people buried in various cemeteries in Kansas City, MO, I'd like to find them grouped together in the sort list rather than have to scroll through and try picking them out. USA, Missouri, Jackson County, Kansas City, cemetery A USA, Missouri, Jackson County, Kansas City, cemetery B USA, Missouri, Jackson County, Kansas City, cemetery C I hope I've explained this in a clear manner. Thanks, Kathy 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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:
Re: [LegacyUG] Place names sorting
The problem is the address function Does NOT give you one cemetery addresses with everyone attached to it, it created one address record for EVERY burial, I dont want 1200 st. Mary Cemetery address records On Fri, Feb 20, 2015 at 2:36 PM, Michele/Support mich...@legacyfamilytree.com wrote: Jay, What is the problem with having one cemetery entry and 1200 burials attached to it? The cemetery/address would show up for every person and you could easily see who all is attached by simply doing a “Show List” The problem you will run into is when you share your information with other genealogists. The standard is locations go in location fields so if you send someone a piece of your file they will have a lot of cleanup to do. If you sync to FamilySearch you will get a “non standard” location warning message. I can give you a third option (and this is the one I use). I create a cemetery event. I like this option because I can add notes, transcription, photographs etc. If I really wanted to I could put the address in the description field along with the cemetery name but I don’t do that. Instead, the address (or directions) are in the source citation. Coal Town Cemetery (Lamar County, Mississippi; intersection of Coal Town Road and White Oak Road), Docia Leora Simmons and William Houston Simmons double marker, personally read, 2001. Westover Memorial Park (Richmond County, Georgia; 2601 Wheeler Road), Pamela Arlene Storey marker, personally read, 2002. Michele Technical Support mich...@legacyfamilytree.com www.legacyfamilytree.com From: Jay Wilpolt [mailto:jaywilp...@aol.com] Sent: Friday, February 20, 2015 5:03 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Place names sorting Michelle, re: addresses and names of building do not belong in the location field. These belong in the address field. I disagree that Legacy LOGICALLY handles addresses and places in the ADDRESS field The best example I can give is a cemetery. If you added the cemetery name in the Burial address field for each person that was buried there, you would have an address record for each burial, instead of just ONE St. Mary's cemetery with 1200 records attached to the address. 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
Ron, can you explain why? the names for the 4 main municipality location fields are just labels and could be adjusted as needed. Maybe they could be City, Parish, County, Country Or even just City, state, Country and have one field disabled There are many ways that these could be adjusted so that globally we are better off that the one field we have now. But since I am not familiar with the place name location needs of other countries, it would help if you explain what you do need. Thanks Jay On Fri, Feb 20, 2015 at 6:10 AM, ronfergy@tiscali.co.uk wrote: Jay, maybe OK for the States, but no good fir many other countries. Ron Ferguson Jay Wilpolt jaywilp...@aol.com wrote: I should add here my own idea that I hope might someday be implemented to resolve many place name issues. First, lets break down the place field into the individual components. A field for Country a field for State a field for County a field for Name Then lets add another set of fields to help us manage places that are not municipalities. probably 3 fields would suffice for most any applications Field 1 might contain a name like ; St. Mary's Catholic Church field 2 might contain the address : 123 Main Street Field 3 might contain a place type maybe 1 for cemetery, 2 for church, 3 for hospital, 4 for residence. When exporting data to a gedcom, we would mash all the 5 fields (but not the type) St. Marys Catholic Church, 123 Main st., Chicago, Cook, Illinois, USA Importing data might be more difficult, but we know we can take countries and states and match to the known possibilities. We could also then set user defaults for which fields are displayed. Hopefully, eventually Legacy will implement something like this to help us all manage our places better. Thanks Jay On Thu, Feb 19, 2015 at 10:47 PM, kaytt ka...@sasktel.net wrote: I have been using Legacy since Version 2 and I'm still struggling with finding a way to enter place names to show everything I want in a written report but have them sort properly in the list. My problem is that sometimes I have only 3 names with separating comas and sometimes 5. If I do a reverse sort: Country, State, County, City it's a mess. For example-- 3 places separated by comas: Kirk Maughold Cemetery, Maughold, Isle of Man (Isle of man is it's own country and not part of England as the Manx are quick to point out). sorts to - , Isle of Man, Maughold, Kirk Maughold 5 places separated by comas: Elmwood Cemetery, Kansas City, Jackson County, Missouri, USA. sorts to: Missouri, Jackson County, Kansas City, Elmwood Cemetery, USA Regina, Saskatchewan, Canada sorts to: , Canada, Saskatchewan, Regina. Most provinces in Canada do not have counties so almost everything is 3 places unless a cemetery is added to take up the 4th space. Any suggestions or creative ideas would be most welcome. My biggest concern is the sorting. If I want to make a list of people buried in various cemeteries in Kansas City, MO, I'd like to find them grouped together in the sort list rather than have to scroll through and try picking them out. USA, Missouri, Jackson County, Kansas City, cemetery A USA, Missouri, Jackson County, Kansas City, cemetery B USA, Missouri, Jackson County, Kansas City, cemetery C I hope I've explained this in a clear manner. Thanks, Kathy 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and
Re: [LegacyUG] Place names sorting
Michelle, re: addresses and names of building do not belong in the location field. These belong in the address field. I disagree that Legacy LOGICALLY handles addresses and places in the ADDRESS field The best example I can give is a cemetery. If you added the cemetery name in the Burial address field for each person that was buried there, you would have an address record for each burial, instead of just ONE St. Mary's cemetery with 1200 records attached to the address. On Fri, Feb 20, 2015 at 6:43 AM, Michele/Support mich...@legacyfamilytree.com wrote: As long as you are consistent with how many fields you use for each country your Master Location List will sort the countries together properly. For example, I use 4 fields for US, I use 3 for Germany, I use 4 for Poland and I use 6 for France. I have no problem with sorting. Where you run into problems is when you are not consistent within a country. Also, addresses and names of building do not belong in the location field. These belong in the address field. Michele Technical Support mich...@legacyfamilytree.com www.legacyfamilytree.com 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
Gene, Yes, My senior moment has caught up with me, as one of the discussions (in a different thread) was about having different Long/lat for each stone within a cemetery and that Legacy has no way to handle that as it either creates a new record (if some field differs) or overwrites the previous Long/Lat that was stored for that exact same place name) Thanks Jay. On Fri, Feb 20, 2015 at 6:31 PM, Gene Young n2...@cfl.rr.com wrote: On 2/20/2015 8:27 PM, Jay Wilpolt wrote: Gene, This is an oft mis understood area. What they were saying is that in the Burial Place field, we should NOT put the name of the cemetery, but instead put that in the Burial Place address which is the field accessed by the + sign That is correct and is exactly what I do. I have one for each cemetery with no duplicates regardless of how many individuals I have connected to it. -- Gene Young Researching Young, Harer, Cox Sallada With Legacy Family Tree http://myyoungs.atspace.com/index.htm 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
On 2/20/2015 6:35 PM, Jay Wilpolt wrote: The problem is the address function Does NOT give you one cemetery addresses with everyone attached to it, it created one address record for EVERY burial, I dont want 1200 st. Mary Cemetery address records If this is the result you are getting you are doing something wrong. I create one address location for each cemetery. I then attach the appropriate individuals to the correct cemetery. I have hundreds attached to a single cemetery and still have only ONE address location for the cemetery. It sounds like you are creating a new cemetery every time instead of attaching the new person to the existing location. -- Gene Young Researching Young, Harer, Cox Sallada With Legacy Family Tree http://myyoungs.atspace.com/index.htm 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
Gene, This is an oft mis understood area. What they were saying is that in the Burial Place field, we should NOT put the name of the cemetery, but instead put that in the Burial Place address which is the field accessed by the + sign On Fri, Feb 20, 2015 at 4:27 PM, Gene Young n2...@cfl.rr.com wrote: On 2/20/2015 6:35 PM, Jay Wilpolt wrote: The problem is the address function Does NOT give you one cemetery addresses with everyone attached to it, it created one address record for EVERY burial, I dont want 1200 st. Mary Cemetery address records If this is the result you are getting you are doing something wrong. I create one address location for each cemetery. I then attach the appropriate individuals to the correct cemetery. I have hundreds attached to a single cemetery and still have only ONE address location for the cemetery. It sounds like you are creating a new cemetery every time instead of attaching the new person to the existing location. -- Gene Young Researching Young, Harer, Cox Sallada With Legacy Family Tree http://myyoungs.atspace.com/index.htm 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
On 2/20/2015 8:27 PM, Jay Wilpolt wrote: Gene, This is an oft mis understood area. What they were saying is that in the Burial Place field, we should NOT put the name of the cemetery, but instead put that in the Burial Place address which is the field accessed by the + sign That is correct and is exactly what I do. I have one for each cemetery with no duplicates regardless of how many individuals I have connected to it. -- Gene Young Researching Young, Harer, Cox Sallada With Legacy Family Tree http://myyoungs.atspace.com/index.htm 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
RE: [LegacyUG] Place names sorting
Does Geo Location work with all of your countries when you use this scheme? Bobby From: Michele/Support [mailto:mich...@legacyfamilytree.com] Sent: Friday, February 20, 2015 9:44 AM To: legacyusergroup@LegacyUsers.com Subject: RE: [LegacyUG] Place names sorting As long as you are consistent with how many fields you use for each country your Master Location List will sort the countries together properly. For example, I use 4 fields for US, I use 3 for Germany, I use 4 for Poland and I use 6 for France. I have no problem with sorting. Where you run into problems is when you are not consistent within a country. Also, addresses and names of building do not belong in the location field. These belong in the address field. Michele Technical Support mailto:mich...@legacyfamilytree.com mich...@legacyfamilytree.com http://www.legacyfamilytree.com www.legacyfamilytree.com 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
RE: [LegacyUG] Place names sorting
Yup. For example, in the Geo German location are like this… Leverkusen, , Nordrhein-Westfalen, Germany After I have selected the location I remove the extra comma in the Core+ field and then click Select. My location is formatted like I want and it has the correct map location. Michele Technical Support mailto:mich...@legacyfamilytree.com mich...@legacyfamilytree.com http://www.legacyfamilytree.com www.legacyfamilytree.com From: Bobby Johnson [mailto:b...@brmemc.net] Sent: Friday, February 20, 2015 11:05 AM To: legacyusergroup@LegacyUsers.com Subject: RE: [LegacyUG] Place names sorting Does Geo Location work with all of your countries when you use this scheme? Bobby 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
RE: [LegacyUG] Place names sorting
Great!! Maybe you should record this procedure in the “Tips and Tricks” Legacy web page. Bobby From: Michele/Support [mailto:mich...@legacyfamilytree.com] Sent: Friday, February 20, 2015 11:47 AM To: legacyusergroup@LegacyUsers.com Subject: RE: [LegacyUG] Place names sorting Yup. For example, in the Geo German location are like this… Leverkusen, , Nordrhein-Westfalen, Germany After I have selected the location I remove the extra comma in the Core+ field and then click Select. My location is formatted like I want and it has the correct map location. Michele Technical Support mailto:mich...@legacyfamilytree.com mich...@legacyfamilytree.com http://www.legacyfamilytree.com www.legacyfamilytree.com 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
RE: [LegacyUG] Place names sorting
Bobby, The extra commas inserted by the Geo Location DB into places in the Master Location List can be removed from reports and charts. Click the Report Options button (has a pencil, ruler and triangle) and select the Format tab. See Locations and the use of Commas at http://support.legacyfamilytree.com/article/AA-00968 and Geo Location Database Quick Guide at http://support.legacyfamilytree.com/article/AA-00953. Thanks, Jim Legacy Support Original Message From: Bobby Johnson b...@brmemc.net Sent: Friday, February 20, 2015 8:59 AM To: legacyusergroup@LegacyUsers.com Subject: RE: [LegacyUG] Place names sorting Great!! Maybe you should record this procedure in the Tips and Tricks Legacy web page. Bobby From: Michele/Support [mailto:mich...@legacyfamilytree.com] Sent: Friday, February 20, 2015 11:47 AM To: legacyusergroup@LegacyUsers.com Subject: RE: [LegacyUG] Place names sorting Yup. For example, in the Geo German location are like this. Leverkusen, , Nordrhein-Westfalen, Germany After I have selected the location I remove the extra comma in the Core+ field and then click Select. My location is formatted like I want and it has the correct map location. Michele Technical Support mailto:mich...@legacyfamilytree.com mich...@legacyfamilytree.com http://www.legacyfamilytree.com www.legacyfamilytree.com 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
RE: [LegacyUG] Place names sorting
Jay, What is the problem with having one cemetery entry and 1200 burials attached to it? The cemetery/address would show up for every person and you could easily see who all is attached by simply doing a “Show List” The problem you will run into is when you share your information with other genealogists. The standard is locations go in location fields so if you send someone a piece of your file they will have a lot of cleanup to do. If you sync to FamilySearch you will get a “non standard” location warning message. I can give you a third option (and this is the one I use). I create a cemetery event. I like this option because I can add notes, transcription, photographs etc. If I really wanted to I could put the address in the description field along with the cemetery name but I don’t do that. Instead, the address (or directions) are in the source citation. Coal Town Cemetery (Lamar County, Mississippi; intersection of Coal Town Road and White Oak Road), Docia Leora Simmons and William Houston Simmons double marker, personally read, 2001. Westover Memorial Park (Richmond County, Georgia; 2601 Wheeler Road), Pamela Arlene Storey marker, personally read, 2002. Michele Technical Support mich...@legacyfamilytree.com www.legacyfamilytree.com From: Jay Wilpolt [mailto:jaywilp...@aol.com] Sent: Friday, February 20, 2015 5:03 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Place names sorting Michelle, re: addresses and names of building do not belong in the location field. These belong in the address field. I disagree that Legacy LOGICALLY handles addresses and places in the ADDRESS field The best example I can give is a cemetery. If you added the cemetery name in the Burial address field for each person that was buried there, you would have an address record for each burial, instead of just ONE St. Mary's cemetery with 1200 records attached to the address. 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place names sorting
Thank you everyone for your ideas. Sorting right to left works for the results I was after. 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
[LegacyUG] Place names sorting
I have been using Legacy since Version 2 and I'm still struggling with finding a way to enter place names to show everything I want in a written report but have them sort properly in the list. My problem is that sometimes I have only 3 names with separating comas and sometimes 5. If I do a reverse sort: Country, State, County, City it's a mess. For example-- 3 places separated by comas: Kirk Maughold Cemetery, Maughold, Isle of Man (Isle of man is it's own country and not part of England as the Manx are quick to point out). sorts to - , Isle of Man, Maughold, Kirk Maughold 5 places separated by comas: Elmwood Cemetery, Kansas City, Jackson County, Missouri, USA. sorts to: Missouri, Jackson County, Kansas City, Elmwood Cemetery, USA Regina, Saskatchewan, Canada sorts to: , Canada, Saskatchewan, Regina. Most provinces in Canada do not have counties so almost everything is 3 places unless a cemetery is added to take up the 4th space. Any suggestions or creative ideas would be most welcome. My biggest concern is the sorting. If I want to make a list of people buried in various cemeteries in Kansas City, MO, I'd like to find them grouped together in the sort list rather than have to scroll through and try picking them out. USA, Missouri, Jackson County, Kansas City, cemetery A USA, Missouri, Jackson County, Kansas City, cemetery B USA, Missouri, Jackson County, Kansas City, cemetery C I hope I've explained this in a clear manner. Thanks, Kathy 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
[LegacyUG] Place Names in England and Wales
Following on from the Washington DC thread that started discussing Middlesex and London, whenever I am in doubt as to the jurisdiction of a place at a certain point in time, I always refer to http://http://www.ukbmd.org.uk/genuki/places/index.html I recommend that you download the place name index and keep it handy on your desktop. Christine 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place Names in England and Wales
On 9/8/2012 8:54 AM, Randy Clark wrote: bad link On Sat, Sep 8, 2012 at 10:13 AM, gen_quest gen_qu...@yahoo.ca mailto:gen_qu...@yahoo.ca wrote: Following on from the Washington DC thread that started discussing Middlesex and London, whenever I am in doubt as to the jurisdiction of a place at a certain point in time, I always refer to http:// http:///http://www.ukbmd.org.uk/genuki/places/index.html http:/// http://www.ukbmd.org.uk/genuki/places/index.html A few to many http:/// Tim 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place Names in England and Wales
Just remove one of the http:// Ron Ferguson http://www.fergys.co.uk/ From: Randy Clark Sent: Saturday, September 08, 2012 3:54 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Place Names in England and Wales bad link On Sat, Sep 8, 2012 at 10:13 AM, gen_quest gen_qu...@yahoo.ca wrote: Following on from the Washington DC thread that started discussing Middlesex and London, whenever I am in doubt as to the jurisdiction of a place at a certain point in time, I always refer to http://http:/// I recommend that you download the place name index and keep it handy on your desktop. Christine 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place Names in England and Wales
On 2012/09/08 16:13, gen_quest wrote: http:///http://www.ukbmd.org.uk/genuki/places/index.html http:/// Let's give the right url http://www.ukbmd.org.uk/genuki/places/index.html :-) -- Regards, Mike Fry Johannesburg (g) 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Place Names
On 30/09/2010 04:14, Jacki Richey wrote: I don't understand why you say that you can only get headstone pictures with a custom event. To the right of the BURIED line is a +, which allows one to add a picture. Am I missing something? Burial pictures - and Birth, Baptism and Death - which are added in that way do not show up in all Reports. Only Individual and FGS, I think. Not sure what the position is with regard to Web pages. -- Jenny M Benson 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
Re: [LegacyUG] Place Names
Jenny M Benson wrote: On 30/09/2010 04:14, Jacki Richey wrote: I don't understand why you say that you can only get headstone pictures with a custom event. To the right of the BURIED line is a +, which allows one to add a picture. Am I missing something? Burial pictures - and Birth, Baptism and Death - which are added in that way do not show up in all Reports. Only Individual and FGS, I think. Not sure what the position is with regard to Web pages. Jenny et al, They don't show on web pages either. Ron Ferguson _ *New* Tutorial: Add Location Pins to Google Earth http://www.fergys.co.uk Includes the family tree for Alan J Grimshaw And the Fergusons of N.W. England 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
Re: [LegacyUG] PLACE NAMES
So, is there any way to use the [Search] function on the addresses in the [+] fields? I can't seem to get it to return any results. Gene Harris On Wed, Sep 29, 2010 at 11:40 AM, Ward Walker wnkwal...@rogers.com wrote: From previous LUG discussions, I had been under the impression that the Address fields (at the '+' signs) had the disadvantage of not showing up in certain output products (as opposed to the Location fields). A quick experiment with a burial address indicates that the Address shows up nicely, in brackets, after the Location, in Family Group Sheets and Descendant Narrative reports. It does not show on graphical charts (probably a good thing). It does not show on web pages. Of course it is not visible in Legacy on Family View -- probably not so important. I think if the addresses were to be made available in web pages, then I would consider switching over to using this field instead of Location, for cemetery and hospital names. The Notes fields at the '+' signs are a little different from the Address fields. These notes appear to be for the event (e.g., burial), rather than for the location of the event. The notes appear in their own section of reports, sometimes well removed from where the event date/location appears. Furthermore, you can't select a previously entered cemetery or hospital from a master list, like you can for Addresses. These notes can, however, be selected to appear on web pages. (I used the 'Individual' style in my experiment.) Overall, using the Notes field just for a cemetery/hospital name seems to add clutter/verbosity, in my opinion. Of course, those of you who create your own burial event are prepared to occupy a little more space in the reports, compared to the Burial Date/Location fields (with or without Address) approach. Presumably you turn off the display of the Burial Date/Location fields, if you always and only use your custom events. At least this event can appear on web pages. Does this sum it up correctly? Ward - Original Message - From: Jerry bearjerca...@gmail.com To: LegacyUserGroup@LegacyUsers.com Sent: Wednesday, September 29, 2010 6:28 AM Subject: Re: [LegacyUG] PLACE NAMES Nothing wrong with thatisn't it part of the NOTES field? That's what I had in mind... Jerry On 9/29/2010 12:54 AM, BMcL Robinson wrote: Hi Jerry What is wrong with the Address field/table for cemeteries etc - then you can edit the details from one place, select them from the list (second application etc), and show list to find out who is there? I thought that Notes would be less friendly. Cheers, Brett BMcL Robinson, Hamilton 3240, New Zealand - Original Message - From: Jerry To: LegacyUserGroup@LegacyUsers.com Sent: Wednesday, September 29, 2010 5:09 PM 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.asphttp://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.asphttp://www.legacyfamilytree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asphttp
Re: [LegacyUG] PLACE NAMES
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 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
Re: [LegacyUG] PLACE NAMES
I'm one of the folks who use the Buried/Location field for cemetery names locations, and initially this did indeed cause my master locations list to be quite a mess. However, I got rid of the jumble by entering every cemetery as follows (example): Cem: Trinity Cemetery, Sylvania, DeKalb, Alabama, United States Then for the short version, I edit and remove Cem: and also , United States. I do this in the Master Locations list after I have added some new cemeteries, or whenever I get around to it. Once it's done for any given cemetery, it's done. So this particular cemetery shows up naturally on screen and in reports as Trinity Cemetery, Sylvania, DeKalb, Alabama. And in the master location list, all of my cemeteries are grouped together alphabetically beginning with the prefix Cem:space. This eliminated the mess. I imagine it won't work well if you are using the mapping/lat/long stuff, but I don't... :-) Maybe this approach will be helpful to someone out there. Mark Wednesday, September 29, 2010, 12:09:22 AM, Jerry wrote: 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
Re: [LegacyUG] PLACE NAMES
Mark, I doubt if the use of a colon will make any different to the mapping function, and the rest of the location certainly doesn't - it is basically the format I always use, and I do use the mapping facility. In fact from the point of view of mapping, using the full address for the location gives a much more accurate result (providing the road still exists!). Ron Ferguson http://www.fergys.co.uk/ -- From: Mark Klan m...@markabout.com Sent: Wednesday, September 29, 2010 10:16 AM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES I'm one of the folks who use the Buried/Location field for cemetery names locations, and initially this did indeed cause my master locations list to be quite a mess. However, I got rid of the jumble by entering every cemetery as follows (example): Cem: Trinity Cemetery, Sylvania, DeKalb, Alabama, United States Then for the short version, I edit and remove Cem: and also , United States. I do this in the Master Locations list after I have added some new cemeteries, or whenever I get around to it. Once it's done for any given cemetery, it's done. So this particular cemetery shows up naturally on screen and in reports as Trinity Cemetery, Sylvania, DeKalb, Alabama. And in the master location list, all of my cemeteries are grouped together alphabetically beginning with the prefix Cem:space. This eliminated the mess. I imagine it won't work well if you are using the mapping/lat/long stuff, but I don't... :-) Maybe this approach will be helpful to someone out there. Mark Wednesday, September 29, 2010, 12:09:22 AM, Jerry wrote: 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
Re: [LegacyUG] PLACE NAMES
On 2010/09/29 12:07, Ron Ferguson wrote: I doubt if the use of a colon will make any different to the mapping function, and the rest of the location certainly doesn't - it is basically the format I always use, and I do use the mapping facility. In fact from the point of view of mapping, using the full address for the location gives a much more accurate result (providing the road still exists!). Ron, You and I are pretty much of one mind when it comes to the confusion that Legacy causes over Locations and place names. To your views concerning the 4-part location name, I would add that not only is it very US-centric, it is also very closely tied to the Geo-Database and is thus closely tied to modern naming conventions. -- Regards, Mike Fry Johannesburg 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
Re: [LegacyUG] PLACE NAMES
Nothing wrong with thatisn't it part of the NOTES field? That's what I had in mind... Jerry On 9/29/2010 12:54 AM, BMcL Robinson wrote: Hi Jerry What is wrong with the Address field/table for cemeteries etc - then you can edit the details from one place, select them from the list (second application etc), and show list to find out who is there? I thought that Notes would be less friendly. Cheers, Brett BMcL Robinson, Hamilton 3240, New Zealand - Original Message - From: Jerry To: LegacyUserGroup@LegacyUsers.com Sent: Wednesday, September 29, 2010 5:09 PM 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 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
Re: [LegacyUG] PLACE NAMES
Mark and Ron - Interesting discussion about the use of Cem: - I'll have to experiment with that, but I think I might still prefer the use of the NOTES button to add the cemeteries to BURIED, not positive yet... With the UK, is it standardized at all at five positions, for example? If so, would Legacy work if use always used five positions? Jerry On 9/29/2010 6:07 AM, Ron Ferguson wrote: Mark, I doubt if the use of a colon will make any different to the mapping function, and the rest of the location certainly doesn't - it is basically the format I always use, and I do use the mapping facility. In fact from the point of view of mapping, using the full address for the location gives a much more accurate result (providing the road still exists!). Ron Ferguson http://www.fergys.co.uk/ -- From: Mark Klanm...@markabout.com Sent: Wednesday, September 29, 2010 10:16 AM To:LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES I'm one of the folks who use the Buried/Location field for cemetery names locations, and initially this did indeed cause my master locations list to be quite a mess. However, I got rid of the jumble by entering every cemetery as follows (example): Cem: Trinity Cemetery, Sylvania, DeKalb, Alabama, United States Then for the short version, I edit and remove Cem: and also , United States. I do this in the Master Locations list after I have added some new cemeteries, or whenever I get around to it. Once it's done for any given cemetery, it's done. So this particular cemetery shows up naturally on screen and in reports as Trinity Cemetery, Sylvania, DeKalb, Alabama. And in the master location list, all of my cemeteries are grouped together alphabetically beginning with the prefix Cem:space. This eliminated the mess. I imagine it won't work well if you are using the mapping/lat/long stuff, but I don't... :-) Maybe this approach will be helpful to someone out there. Mark Wednesday, September 29, 2010, 12:09:22 AM, Jerry wrote: 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 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
Re: [LegacyUG] PLACE NAMES
Jerry, There is not a standard way of expressing locations within the UK, Ireland and the Isle of Man. The format is always smallest to largest, the latter being one of the countries comprising the UK, viz. England, Northern Ireland, Scotland and Wales. As countries we have been at the forefront of civilisation for a long time, a long time before any thought was given to the advantages, or otherwise, of standards, and woe betide anyone who tries to change this. The point being that we are very protective of our history and historic locations, one only has to see the furore when changes in county boundaries are suggested! I suggest that you take a look at http://homepages.nildram.co.uk/~jimella/counties.htm which gives a detailed look at the type and history of our locations. Ron Ferguson http://www.fergys.co.uk -- From: Jerry bearjerca...@gmail.com Sent: Wednesday, September 29, 2010 11:30 AM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES Mark and Ron - Interesting discussion about the use of Cem: - I'll have to experiment with that, but I think I might still prefer the use of the NOTES button to add the cemeteries to BURIED, not positive yet... With the UK, is it standardized at all at five positions, for example? If so, would Legacy work if use always used five positions? Jerry On 9/29/2010 6:07 AM, Ron Ferguson wrote: Mark, I doubt if the use of a colon will make any different to the mapping function, and the rest of the location certainly doesn't - it is basically the format I always use, and I do use the mapping facility. In fact from the point of view of mapping, using the full address for the location gives a much more accurate result (providing the road still exists!). Ron Ferguson http://www.fergys.co.uk/ -- From: Mark Klanm...@markabout.com Sent: Wednesday, September 29, 2010 10:16 AM To:LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES I'm one of the folks who use the Buried/Location field for cemetery names locations, and initially this did indeed cause my master locations list to be quite a mess. However, I got rid of the jumble by entering every cemetery as follows (example): Cem: Trinity Cemetery, Sylvania, DeKalb, Alabama, United States Then for the short version, I edit and remove Cem: and also , United States. I do this in the Master Locations list after I have added some new cemeteries, or whenever I get around to it. Once it's done for any given cemetery, it's done. So this particular cemetery shows up naturally on screen and in reports as Trinity Cemetery, Sylvania, DeKalb, Alabama. And in the master location list, all of my cemeteries are grouped together alphabetically beginning with the prefix Cem:space. This eliminated the mess. I imagine it won't work well if you are using the mapping/lat/long stuff, but I don't... :-) Maybe this approach will be helpful to someone out there. Mark Wednesday, September 29, 2010, 12:09:22 AM, Jerry wrote: 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
Re: [LegacyUG] Place Names
Jenny, I enter burial/cemetery events so I can attach Headstone pictures that print on reports. I also use the address along with location. In the location field I just use City,County, State, Country. In the address fields I can put the complete address and GPS coordinates of the cemetery ( That also prints on reports). G.C. On Tue, Sep 28, 2010 at 10:41 PM, Jacki Richey pdxjacki...@hotmail.com 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 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
Re: [LegacyUG] PLACE NAMES
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.ukwrote: 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.asphttp://www.legacyfamilytree.com/Etiquette.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asphttp://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.asphttp://www.legacyfamilytree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asphttp://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21
Re: [LegacyUG] PLACE NAMES
From previous LUG discussions, I had been under the impression that the Address fields (at the '+' signs) had the disadvantage of not showing up in certain output products (as opposed to the Location fields). A quick experiment with a burial address indicates that the Address shows up nicely, in brackets, after the Location, in Family Group Sheets and Descendant Narrative reports. It does not show on graphical charts (probably a good thing). It does not show on web pages. Of course it is not visible in Legacy on Family View -- probably not so important. I think if the addresses were to be made available in web pages, then I would consider switching over to using this field instead of Location, for cemetery and hospital names. The Notes fields at the '+' signs are a little different from the Address fields. These notes appear to be for the event (e.g., burial), rather than for the location of the event. The notes appear in their own section of reports, sometimes well removed from where the event date/location appears. Furthermore, you can't select a previously entered cemetery or hospital from a master list, like you can for Addresses. These notes can, however, be selected to appear on web pages. (I used the 'Individual' style in my experiment.) Overall, using the Notes field just for a cemetery/hospital name seems to add clutter/verbosity, in my opinion. Of course, those of you who create your own burial event are prepared to occupy a little more space in the reports, compared to the Burial Date/Location fields (with or without Address) approach. Presumably you turn off the display of the Burial Date/Location fields, if you always and only use your custom events. At least this event can appear on web pages. Does this sum it up correctly? Ward - Original Message - From: Jerry bearjerca...@gmail.com To: LegacyUserGroup@LegacyUsers.com Sent: Wednesday, September 29, 2010 6:28 AM Subject: Re: [LegacyUG] PLACE NAMES Nothing wrong with thatisn't it part of the NOTES field? That's what I had in mind... Jerry On 9/29/2010 12:54 AM, BMcL Robinson wrote: Hi Jerry What is wrong with the Address field/table for cemeteries etc - then you can edit the details from one place, select them from the list (second application etc), and show list to find out who is there? I thought that Notes would be less friendly. Cheers, Brett BMcL Robinson, Hamilton 3240, New Zealand - Original Message - From: Jerry To: LegacyUserGroup@LegacyUsers.com Sent: Wednesday, September 29, 2010 5:09 PM 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
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 mailto: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 mailto: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
Re: [LegacyUG] Place Names
Ah yes, that's what I missed in the e-mail I just sent. The only way to get headstone pictures is with a custom event. And, since you insert the event Address using the event sentence definition, I would hope that in this case it does show up on web pages. (Not tested.) Ward - Original Message - From: G Oliver gcoliv...@gmail.com To: LegacyUserGroup@LegacyUsers.com Sent: Wednesday, September 29, 2010 10:57 AM Subject: Re: [LegacyUG] Place Names Jenny, I enter burial/cemetery events so I can attach Headstone pictures that print on reports. I also use the address along with location. In the location field I just use City,County, State, Country. In the address fields I can put the complete address and GPS coordinates of the cemetery ( That also prints on reports). G.C. On Tue, Sep 28, 2010 at 10:41 PM, Jacki Richey pdxjacki...@hotmail.com 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
Re: [LegacyUG] PLACE NAMES
On 9/29/2010 11:40 AM, Ward Walker wrote: It does not show on web pages. Ward, speaking about the ADDRESS + NOTES next to the BURIED LOCATION and DATE fields. It depends on what you are referring to - perhaps if you create web pages directly from Legacy, it does not show up (?) - but if you use a Gedcom file to upload into TNG (The Next Generation of Genealogy Sitebuilding) to build your database online, YES, it does show up...--Jerry 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
Re: [LegacyUG] PLACE NAMES
Scott, I don't think that I am being too rigid at all. The last name in a location is that of the country, these are England, Scotland, Wales and Northern Ireland which are the constituent countries of the United Kingdom, the latter being a Kingdom comprising an alliance of countries. Note that Wales has its own Assemby, and Northern Ireland and Scotland have their own Parliament. Let me ask you, given that we now have the European Community, would you say that the location for Paris is Paris, France, Europe? Of course not, because France is the country and not Europe. If one did then England etc. would have the status of a county! BTW. shire at the end of a word actually means county so we do not use the word county when shire is in the name. Hampshire is a contraction of Hamptonshire (which hasn't been used for a long time). To me, it is a matter of respect to consider any country on the way that its residents do, which means following the way in which they describe their own locations, rather than trying to make it fit into a convention which wasn't even derived by that country.. Ron Ferguson http://www.fergys.co.uk/ From: Scott Hall Sent: Wednesday, September 29, 2010 4:33 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES 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
Re: [LegacyUG] PLACE NAMES
On 2010/09/29 17:33, Scott Hall wrote: 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? The use of UK and England together is superfluous. It's akin to saying America, USA. Also, there is only one county in England that has an extraneous County in its name: County Durham. For the sake of further argument, I would gratefully exclude Ireland, both parts from this discussion. Thus, your Hampshire County is like chalk on a blackboard to us Brits - it grates. So, Hampshire only! It's a pity that the British postcode system wasn't devised a whole lot earlier than it was. Then we could use the likes of CM11 2QA for my former address in England :-) Much more precise than the zip code in the US. -- Regards, Mike Fry Johannesburg 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
Re: [LegacyUG] PLACE NAMES
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
Re: [LegacyUG] PLACE NAMES
Sorting the Location list right to left, as has been mentioned several times, seems to eliminate any concern over the number of fields in the location (such as putting in commas for force 4 locations). As far as I can tell, the ONLY downside to this is the Global-Locator, and Ron explains a good work-around when it is needed. Does anyone see any other downside to the right to left sorting of the location list? On Wed, Sep 29, 2010 at 9:32 AM, Ron Ferguson ronfergy@tiscali.co.ukwrote: 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 bearjerca...@gmail.com *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.ukwrote: 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
Re: [LegacyUG] PLACE NAMES
On 29/09/2010 16:40, Ward Walker wrote: From previous LUG discussions, I had been under the impression that the Address fields (at the '+' signs) had the disadvantage of not showing up in certain output products (as opposed to the Location fields). A quick experiment with a burial address indicates that the Address shows up nicely, in brackets, after the Location, in Family Group Sheets and Descendant Narrative reports. It does not show on graphical charts (probably a good thing). It does not show on web pages. Of course it is not visible in Legacy on Family View -- probably not so important. I think if the addresses were to be made available in web pages, then I would consider switching over to using this field instead of Location, for cemetery and hospital names. My objection to the + sign Address fields is the way they appear in Reports. You end up with something like Jenny was baptized in Oxton, Birkenhead, Cheshire, England (Christ Church, Christ Church Road, Oxton, Birkenhead, Cheshire, England) or Jenny was baptized in Oxton, Birkenhead, Cheshire, England (Christ Church, Christchurch Road.) The latter is slightly preferable, but means you have a long list of rather meaningless addresses, comprising just street addresses without town, county, (state) or country. I much prefer to see Jenny was baptized at Christ Church, Christ Church Road, Oxton, Birkenhead, Cheshire, England. I think if only the programmers would enable us to print in all Reports photos attached behind the + sign everyone would be satisfied. -- Jenny M Benson 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
Re: [LegacyUG] PLACE NAMES
Hi Ron. I understand your desire to be true to the correct way for your country. However, since I want to see all the names sort properly in a list, I'll go ahead and insert that extra blank field. As I see it, no harm done because it is just a blank anyway. I have a cousin in Canada I work with on our website and she insisted (at first) in putting Upper Canada, Lower Canada, Colony of Massachusetts, etc., for some of our ancestors when their birth places were called names no longer in use. I finally convinced her that we could use the NOTE field for those things and not mess up our location database. But your explanations do help see the bigger picture and I appreciate them! Jerry On 9/29/2010 12:32 PM, Ron Ferguson wrote: 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 mailto:bearjerca...@gmail.com *Sent:* Wednesday, September 29, 2010 4:56 PM *To:* LegacyUserGroup@LegacyUsers.com mailto: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 mailto: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
Re: [LegacyUG] PLACE NAMES
But unless the event took place in the modern UK, why would you even consider putting it into the location field? The country such as England should be the last entry in the location field. So my grandmother was born in 1881 in: Saint Vincent Villa, Lynton, Devon, England And yes, although I am in the US and the majority of my locations are in the US, I have chosen to completely ignore the 4-field location format. This same grandmother is buried in: Elmlawn Cemetery - 3939 Delaware Avenue, Kenmore, Erie County, New York, USA In addition, I always record the event location as it was at the time of the event. I have entries for events that took place in each of the following locations (listed latest to oldest), although they each mean the same place, just at different times of history when the event took place: Detroit, Wayne County, Michigan, USA Detroit, Wayne County, Michigan Territory, USA Detroit, Wayne County, Indiana Territory, USA Detroit, Wayne County, Northwest Territory, USA Detroit, British North America Fort Ponchartrain du Detroit, New France Each of these is entered separately in my Locations master list. This works for me but let's all keep in mind that Legacy is very flexible in almost all aspects. What works for me might not work for you! Mary 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
Re: [LegacyUG] PLACE NAMES
Hi Mary. I understand what you are doing. I just don't like it because it creates many different location names for the exact same place. Hence, we decided to modify the location, when necessary, by using the extra (+) note field. Just seems to me that if you want to find every person born in Detroit (like your example and where I live, by the way), it would be far better to have only one master name for that location. Fort Ponchartrain won't sort anywhere near Detroit in a long list of places either. But to each his own, as you say. Jerry On 9/29/2010 1:13 PM, brenze...@roadrunner.com wrote: But unless the event took place in the modern UK, why would you even consider putting it into the location field? The country such as England should be the last entry in the location field. So my grandmother was born in 1881 in: Saint Vincent Villa, Lynton, Devon, England And yes, although I am in the US and the majority of my locations are in the US, I have chosen to completely ignore the 4-field location format. This same grandmother is buried in: Elmlawn Cemetery - 3939 Delaware Avenue, Kenmore, Erie County, New York, USA In addition, I always record the event location as it was at the time of the event. I have entries for events that took place in each of the following locations (listed latest to oldest), although they each mean the same place, just at different times of history when the event took place: Detroit, Wayne County, Michigan, USA Detroit, Wayne County, Michigan Territory, USA Detroit, Wayne County, Indiana Territory, USA Detroit, Wayne County, Northwest Territory, USA Detroit, British North America Fort Ponchartrain du Detroit, New France Each of these is entered separately in my Locations master list. This works for me but let's all keep in mind that Legacy is very flexible in almost all aspects. What works for me might not work for you! Mary 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 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
Re: [LegacyUG] PLACE NAMES
Jerry, Clearly we are not going to agree on the subject of place names, and I do not agree with what you say below either. Place names should be those used at the time of the event, and not only from the point of view of accuracy. Let us consider the town of Slaithwaite in Yorkshire, England, or rather it was until the boundaries changed and its location became Slaithwaite, Lancashire, England, much to the annoyance of the residents of the town - I mean what were the Wars of the Roses for if not to protect our borders? Anyhow if one writes the location using the current county of Lancashire then it will not easily be found in the 19c censuses as it was then in Yorkshire. Not being a 100 years old, yet, I am not included in any censuses but should anyone be bothered looking for me when they are published, the will see that I was brought up in the Hamlet of Winton in Eccles, Lancashire, England. In 1974 Eccles was merged into the City of Salford, so now the location is Winton, Eccles, Salford, Lancashire, England. It doesn't look like much of a change, but actually it is, because prior to 1971 Eccles was a county borough with its own administration and police force etc. Now it is a district of Salford, not the same at all and one will certainly not find Eccles in Salford in the censuses prior to 1974. These are just a couple of examples, but the principle applies to all historic data, it will not be found if one looks in the wrong place. Ron Ferguson http://www.fergys.co.uk/ -- From: Jerry bearjerca...@gmail.com Sent: Wednesday, September 29, 2010 6:28 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES Hi Mary. I understand what you are doing. I just don't like it because it creates many different location names for the exact same place. Hence, we decided to modify the location, when necessary, by using the extra (+) note field. Just seems to me that if you want to find every person born in Detroit (like your example and where I live, by the way), it would be far better to have only one master name for that location. Fort Ponchartrain won't sort anywhere near Detroit in a long list of places either. But to each his own, as you say. Jerry On 9/29/2010 1:13 PM, brenze...@roadrunner.com wrote: But unless the event took place in the modern UK, why would you even consider putting it into the location field? The country such as England should be the last entry in the location field. So my grandmother was born in 1881 in: Saint Vincent Villa, Lynton, Devon, England And yes, although I am in the US and the majority of my locations are in the US, I have chosen to completely ignore the 4-field location format. This same grandmother is buried in: Elmlawn Cemetery - 3939 Delaware Avenue, Kenmore, Erie County, New York, USA In addition, I always record the event location as it was at the time of the event. I have entries for events that took place in each of the following locations (listed latest to oldest), although they each mean the same place, just at different times of history when the event took place: Detroit, Wayne County, Michigan, USA Detroit, Wayne County, Michigan Territory, USA Detroit, Wayne County, Indiana Territory, USA Detroit, Wayne County, Northwest Territory, USA Detroit, British North America Fort Ponchartrain du Detroit, New France Each of these is entered separately in my Locations master list. This works for me but let's all keep in mind that Legacy is very flexible in almost all aspects. What works for me might not work for you! Mary 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
Re: [LegacyUG] PLACE NAMES
-- From: Ron Ferguson ronfergy@tiscali.co.uk Sent: Wednesday, September 29, 2010 6:42 AM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES . we are very protective of our history and historic locations, one only has to see the furore when changes in county boundaries are suggested! Apparently, no so much -- From: Ron Ferguson ronfergy@tiscali.co.uk Sent: Wednesday, September 29, 2010 11:34 AM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES .. Let us consider the town of Slaithwaite in Yorkshire, England, or rather it was until the boundaries changed and its location became Slaithwaite, Lancashire, England, ... Anyhow if one writes the location using the current county of Lancashire then it will not easily be found in the 19c censuses as it was then in Yorkshire. . I was brought up in the Hamlet of Winton in Eccles, Lancashire, England. In 1974 Eccles was merged into the City of Salford, so now the location is Winton, Eccles, Salford, Lancashire, England. It doesn't look like much of a change, but actually it is, because prior to 1971 Eccles was a county borough with its own administration and police force etc. Now it is a district of Salford, not the same at all and one will certainly not find Eccles in Salford in the censuses prior to 1974... John S. Adams Hermosa Beach, CA 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
Re: [LegacyUG] PLACE NAMES
Thanks, Ron. I don't disagree with you on accuracy - just how that accuracy should be noted to keep the place names systematic with the computer age and GPS. But at least I think we got some good information out there. Thanks again for the history lesson for Great Britain where many of my ancestors came from also. --Jerry On 9/29/2010 2:34 PM, Ron Ferguson wrote: Jerry, Clearly we are not going to agree on the subject of place names, and I do not agree with what you say below either. Place names should be those used at the time of the event, and not only from the point of view of accuracy. Let us consider the town of Slaithwaite in Yorkshire, England, or rather it was until the boundaries changed and its location became Slaithwaite, Lancashire, England, much to the annoyance of the residents of the town - I mean what were the Wars of the Roses for if not to protect our borders? Anyhow if one writes the location using the current county of Lancashire then it will not easily be found in the 19c censuses as it was then in Yorkshire. Not being a 100 years old, yet, I am not included in any censuses but should anyone be bothered looking for me when they are published, the will see that I was brought up in the Hamlet of Winton in Eccles, Lancashire, England. In 1974 Eccles was merged into the City of Salford, so now the location is Winton, Eccles, Salford, Lancashire, England. It doesn't look like much of a change, but actually it is, because prior to 1971 Eccles was a county borough with its own administration and police force etc. Now it is a district of Salford, not the same at all and one will certainly not find Eccles in Salford in the censuses prior to 1974. These are just a couple of examples, but the principle applies to all historic data, it will not be found if one looks in the wrong place. Ron Ferguson http://www.fergys.co.uk/ -- From: Jerrybearjerca...@gmail.com Sent: Wednesday, September 29, 2010 6:28 PM To:LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] PLACE NAMES Hi Mary. I understand what you are doing. I just don't like it because it creates many different location names for the exact same place. Hence, we decided to modify the location, when necessary, by using the extra (+) note field. Just seems to me that if you want to find every person born in Detroit (like your example and where I live, by the way), it would be far better to have only one master name for that location. Fort Ponchartrain won't sort anywhere near Detroit in a long list of places either. But to each his own, as you say. Jerry On 9/29/2010 1:13 PM, brenze...@roadrunner.com wrote: But unless the event took place in the modern UK, why would you even consider putting it into the location field? The country such as England should be the last entry in the location field. So my grandmother was born in 1881 in: Saint Vincent Villa, Lynton, Devon, England And yes, although I am in the US and the majority of my locations are in the US, I have chosen to completely ignore the 4-field location format. This same grandmother is buried in: Elmlawn Cemetery - 3939 Delaware Avenue, Kenmore, Erie County, New York, USA In addition, I always record the event location as it was at the time of the event. I have entries for events that took place in each of the following locations (listed latest to oldest), although they each mean the same place, just at different times of history when the event took place: Detroit, Wayne County, Michigan, USA Detroit, Wayne County, Michigan Territory, USA Detroit, Wayne County, Indiana Territory, USA Detroit, Wayne County, Northwest Territory, USA Detroit, British North America Fort Ponchartrain du Detroit, New France Each of these is entered separately in my Locations master list. This works for me but let's all keep in mind that Legacy is very flexible in almost all aspects. What works for me might not work for you! Mary 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 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
RE: [LegacyUG] Place Names
I don't understand why you say that you can only get headstone pictures with a custom event. To the right of the BURIED line is a +, which allows one to add a picture. Am I missing something? Jacki From: wnkwal...@rogers.com To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Place Names Date: Wed, 29 Sep 2010 12:06:13 -0400 Ah yes, that's what I missed in the e-mail I just sent. The only way to get headstone pictures is with a custom event. And, since you insert the event Address using the event sentence definition, I would hope that in this case it does show up on web pages. (Not tested.) Ward 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
RE: [LegacyUG] Place Names
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
[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
Re: [LegacyUG] PLACE NAMES
Hi Jerry What is wrong with the Address field/table for cemeteries etc - then you can edit the details from one place, select them from the list (second application etc), and show list to find out who is there? I thought that Notes would be less friendly. Cheers, Brett BMcL Robinson, Hamilton 3240, New Zealand - Original Message - From: Jerry To: LegacyUserGroup@LegacyUsers.com Sent: Wednesday, September 29, 2010 5:09 PM 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
[LegacyUG] Place Names
What does Core and Core + mean in the address fields? I searched for it in Help without success. Ditto the index to the printed manual. Where do I put the note about the current name of the county? I do have the videos but I like to be able to look up something, know where to find it next time. I was impressed with #1 but I didn't retain every detail and I am sure it will be the same with the rest of them. 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
Re: [LegacyUG] Place Names
As explained in the Help file for the Geo Location Database, The Core field shows the regular location name as found in the list. The Core + field adds any other location pieces that were attached to the incoming place name. There is an extensive discussion with examples in the Help file. Sincerely, Sherry Technical Support Legacy Family Tree On Mon, Sep 27, 2010 at 8:34 AM, Cheryl Rothwell historysle...@gmail.com wrote: What does Core and Core + mean in the address fields? I searched for it in Help without success. Ditto the index to the printed manual. Where do I put the note about the current name of the county? I do have the videos but I like to be able to look up something, know where to find it next time. I was impressed with #1 but I didn't retain every detail and I am sure it will be the same with the rest of them. 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
Re: [LegacyUG] Place Names
On 2010/09/27 17:34, Cheryl Rothwell wrote: What does Core and Core + mean in the address fields? I searched for it in Help without success. Ditto the index to the printed manual. I found this in the Help File - press the Help button when the window shows the Core and Core+ fields. Selecting a Location As you scroll up and down in the list and highlight specific lines, the location on that line is filled into the two main core fields at the top of the window, Core and Core +. The Core field shows the regular location name as found in the list. The Core + field adds any other location pieces that were attached to the incoming place name. For example, let's say that you were looking at a person's Individual Information screen and the Burial location field contained Hilltop Cemetery, Benton City, Benton,. (Notice that there is no state or country name.) After clicking the Geo Location List icon at the end of field, the Geo Location Database window appears with Hilltop Cemetery, Benton City, Benton, Iowa, USA in the Core + field and Benton City, Benton, Iowa, USA in the Core field. The Core + field has the non-standard Hilltop Cemetery kept in it. But notice that the state and country have been filled into both locations, and notice that there are two locations down in the list, one in Iowa, USA and one in Washington USA. Because the top location in the list is highlighted, its pieces have been filled into the Core + and Core fields. Now lets assume that you know that the correct location is in Washington. When you click on the Washington location line down in the list, the Core + and Core fields change to include the state of Washington and USA as the country. Hilltop Cemetery is also retained in the Core + field. -- Regards, Mike Fry Johannesburg 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
Re: [LegacyUG] Place Names
I searched on core as keyword. I would not have thought of Geo Location. Of course it makes sense now. :-) Thank you for bearing with me. 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
RE: [LegacyUG] Place Names
I am a new user, new to Legacy, but not to genealogy. I previously used PAF and kept the four grandparents (my two and my husband's two) lines as separate databases. I imported as a gedcom the smallest one with few problems. Now I am really confused about entering cemetery names. On ancestry they said to follow the city, county, state/province, country strictly and to put the cmemtery name under description. However, Legacy does not have a description line. I read many messages in the archives about cemeteries and have read all the UG messages for the last week. One person suggested putting the name of the cemetery with the city as Spokane - Hope Cemetery, Spokane, Washington, USA. Now in this message it is suggested that one enter just three fields and that Legacy will figure out the rest for the Core and Core+ fields. Enter Hilltop Cemetery, Benton City, Benton So is this later the best way to enter cemetery locations? Thanks, Jacki in Morelia, Mexico From: mike...@iafrica.com To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Place Names Date: Mon, 27 Sep 2010 17:40:17 +0200 On 2010/09/27 17:34, Cheryl Rothwell wrote: What does Core and Core + mean in the address fields? I searched for it in Help without success. Ditto the index to the printed manual. I found this in the Help File - press the Help button when the window shows the Core and Core+ fields. Selecting a Location As you scroll up and down in the list and highlight specific lines, the location on that line is filled into the two main core fields at the top of the window, Core and Core +. The Core field shows the regular location name as found in the list. The Core + field adds any other location pieces that were attached to the incoming place name. For example, let's say that you were looking at a person's Individual Information screen and the Burial location field contained Hilltop Cemetery, Benton City, Benton,. (Notice that there is no state or country name.) After clicking the Geo Location List icon at the end of field, the Geo Location Database window appears with Hilltop Cemetery, Benton City, Benton, Iowa, USA in the Core + field and Benton City, Benton, Iowa, USA in the Core field. The Core + field has the non-standard Hilltop Cemetery kept in it. But notice that the state and country have been filled into both locations, and notice that there are two locations down in the list, one in Iowa, USA and one in Washington USA. Because the top location in the list is highlighted, its pieces have been filled into the Core + and Core fields. Now lets assume that you know that the correct location is in Washington. When you click on the Washington location line down in the list, the Core + and Core fields change to include the state of Washington and USA as the country. Hilltop Cemetery is also retained in the Core + field. -- Regards, Mike Fry Johannesburg 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 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
Re: [LegacyUG] Place Names
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. Sincerely, Sherry Technical Support Legacy Family Tree On Mon, Sep 27, 2010 at 10:55 AM, Jacki Richey pdxjacki...@hotmail.com wrote: I am a new user, new to Legacy, but not to genealogy. I previously used PAF and kept the four grandparents (my two and my husband's two) lines as separate databases. I imported as a gedcom the smallest one with few problems. Now I am really confused about entering cemetery names. On ancestry they said to follow the city, county, state/province, country strictly and to put the cmemtery name under description. However, Legacy does not have a description line. I read many messages in the archives about cemeteries and have read all the UG messages for the last week. One person suggested putting the name of the cemetery with the city as Spokane - Hope Cemetery, Spokane, Washington, USA. Now in this message it is suggested that one enter just three fields and that Legacy will figure out the rest for the Core and Core+ fields. Enter Hilltop Cemetery, Benton City, Benton So is this later the best way to enter cemetery locations? Thanks, Jacki in Morelia, Mexico 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
Re: [LegacyUG] Place Names
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! -- Jenny M Benson 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
Re: [LegacyUG] Place Names
Jenny, As you know I agree with you, and record my cemetery names and locations exactly as you describe (as I do with *all* my locations). To me there is only one decision to be made: whether or not to use the so called 4 field convention. Since this was designed by Americans for Americans, it is not much use to the rest of us (and as I understand it some American places as well). Thus, if the 4 field system doesn't work, then one may as well not use it at all, and put the full address/location in the Location Field for all the Events. The result is a location which is complete, and is placed in the most sensible place in all reports. Ron Ferguson http://www.fergys.co.uk/ -- From: Jenny M Benson ge...@cedarbank.me.uk Sent: Monday, September 27, 2010 7:26 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Place Names 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! -- Jenny M Benson 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
Re: [LegacyUG] Place Names
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 Don't eat burrito's after 2am On 9/27/2010 12:26 PM, Jenny M Benson wrote: 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
Re: [LegacyUG] Place Names
Tim, Personally I use: Plot, Cemetery Name, Road, Town, etc. Ron Ferguson -- From: Tim Rosenlof spa...@xmission.com Sent: Monday, September 27, 2010 7:41 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Place Names 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 Don't eat burrito's after 2am On 9/27/2010 12:26 PM, Jenny M Benson wrote: 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
Re: [LegacyUG] Place Names
On 27/09/2010 20:59, Ron Ferguson wrote: Personally I use: Plot, Cemetery Name, Road, Town, etc. I do likewise. -- Jenny M Benson 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
