I put cemetery, church, house, hospital, et. al. in both location and address fields. I do location because it will appear on screen or in reports more predictable/dependably than the address fields. But Legacy could improve that someday, so I figure it's easier to enter the data now than to try and go back and update an entire database someday. Plus maybe I have OCD, I have a hard time leaving form fields blank. :)
I also subscribe to the notion that do what works best for you. For me that means adding locations that will make sense, but I still want to get the most out of Legacy so I also try to conform to the 4 comma location format. If I find a way to make location work within the 4 part location I do, but am not afraid to break away when necessary. As such, I would not recommend locations like this: Riverview Cemetery, South Bend, St. Joseph, Indiana, United States Rather, I'd suggest South Bend, St. Joseph, Indiana, United States South Bend-Riverview Cemetery, St. Joseph, Indiana, United States South Bend-1st Baptist Church, St. Joseph, Indiana, United States ... Why? - All South Bend locations sort together in master list - No space around the dash (ie. South Bend-Riverview Cemetery), means the 'standard' "South Bend, St. Joseph, Indiana, United States" will sort to the top, which means when you start typing "South Bend" into a location field the 'standard' format is prefilled for you. - Locations follow the 4part pattern for most effective use in Legacy, and provide the more specific location information in a meaningful way to my reports - Each location can be given more exact geolocation coordinates On Mon, Nov 25, 2013 at 5:54 AM, Mike Fry <[email protected]> wrote: > On 2013/11/25 13:48, Rose Hatten wrote: > > > Pam, there's a Sample database that comes with Legacy. You might want to > > test your thoughts on that, changing one thing or another and looking at > the > > reports to see if you like the output. That way you won't mess up your > data, > > and you can get an idea about how each of the options have an effect on > > sorting, reporting, GEDCOM exporting, and the like. > > The Sample database, whilst instructive, often doesn't mean as much to > people as > it does to Geoff. My recommendation to people is to create a cut-down > version of > your own database and call it Sandbox. This is where you can play and > experiment > to your heart's content without harming the main object of your affections. > > -- > 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/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > 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 > > > -- James Cook GED Utils, Ancestry Utils http://loosestacks.blogspot.com/ Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ 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
