I follow the location and address "camp" - two separate lists. The advantage is locations work as they should, and addresses help for example with building/site names eg Auckland Hospital, Waikemete Cemetery - once entered the detail is there just to accept next time, and list all those connected to the address (eg for a cemetery visit).
Cheers, Brett BMcL Robinson, New Zealand ----- Original Message <snipped> ----- I know this has been discussed several times before and its almost as if we all break down into two camps on this issue similar to the listing of sources and the lumpers and splitters involved with that issue. There are those that like to use the very specific location name at the front such as "Mercy Hospital, San Jose, Williams County, Oregon, USA" (other countries feel free to substitute names as necessary). That method can make for some very nice sorting requirements and the specific information is readily apparent when in Family View mode. Then there is the other camp which would list the above address as "San Jose, Williams County, Oregon". The specific location of Mercy Hospital is added to the Birth Address Window under which not only is the name "Mercy Hospital" added, but the specific street address, postal codes, and GPS co-ordinates can also be added. If one doesn't want to use the Birth Address Window, then the specific location of "Mercy Hospital" can be added to the Birth Notes Window (an easier, less-complicated method that I prefer.) The drawback of this method is that the information is not readily apparent when in the normal Family View mode unless you go through the "great effort" to click the mouse one or two more times to open up those Addresses/Notes windows. These very specific location turn up all the time on births, deaths, marriages, christenings, etc. I ran across one a few months back that had the name of the Hospital, the floor, and the room number. I liked the statement given by someone a few days ago on this list "How far down the hole do we chase the rabbit?" I've often wondered exactly what purpose some of this extra information serves, genealogically speaking. Well, that was outdone last night when I came across a death location starting with "In the arms of his son, ....city, county, state, USA". Brian in CA > -----Original Message----- > My way is not for everyone, but it works for me. Instead of: > > Miami-Dade Medical Center, Miami, Miami-Dade County, Florida, USA, > > I use instead: > > Miami-Dade Medical Center, Miami-Dade County, Florida, USA > > because the latter has four parts. Then, in the location list, I > reverse the sort. Therefore: > > USA, Florida, Miami-Dade County, Miami-Dade Medical Center > > very neatly sorts with everything I have for Miami-Dade County. > Reversing the display so that it reads country, state, county, city > keeps hospitals, cemeteries, churches, all together, and I like that. > Not everyone does though. > > Robert > > At 2010-06-11 05:35 PM, you wrote: > >I find that the structure of some events results in an excessive > >number of locations that cannot be resolved by geo-location. For > >example the location of many marriages is reported in the marriage > >license as "at the home of so and so [usually father of the bride], > >actual address". Many deaths take place at "Such and such Hospital, > >address". Geo-location cannot resolve these because it does not > >know to ignore everything from the beginning to the first > >comma. These extra entries complicate the auto-complete function > >for locations. For example I have a frequently used "location" of > >"Ontario Psychiatric Hospital, London, Ontario, Canada". Whenever I > >want to specify that an event took place in Ontario, Canada, I have > >to type almost the whole location before auto-complete works, > >because space sorts before comma. Also I end up with a lot of > >semi-duplicate entries in the locations master list, which in my > >database currently contains 18,088 entries. I wish that I could > >separate the description of the location from the actual location > >while not affecting how the complete value is displayed to > >users. That caveat makes the option of putting the description into > >the marriage notes less than satisfactory. > > > >I would appreciate your thoughts on this. 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
