> Here are some examples of what I want to enter:
>
> Evergreen Memorial Park, McMinnville, Yamhill County, Oregon
> St. Vincents Hospital, Portland, Multnomah County, Oregon
>
Andy,
Here is the way I enter them (using your examples).
Evergreen Memorial Park - McMinnville, Yamhill County, Oregon
St. Vincent's Hospital - Portland, Multnomah County, Oregon
I use a "-" (hyphen/dash) between the 'Place' and the 'City/Town' instead of
using a "," (comma). This way you can sort on County, State, Country.
It does make it a little difficult when you want to sort on the 'City/Town'
field though. This doesn't bother me too much because when I sort on State,
County, City, I am able to see all the "Evergreen Memorial Park" cemeteries
that are located in "Yamhill County, Oregon" with no trouble. And, I have
several hundred locations listed (probably near a 1,000).
If it's best for you, you can always put the "-" between the 'City' the
'Place', such as:
McMinnville - Evergreen Memorial Park, Yamhill County, Oregon
This way, you can sort on the City also.
P.S. It is really a good practice to use ", ," (two commas) when you are
not sure of the City, County, or the State.
I hope this helps,
Louise
----- Original Message -----
From: "A&A Stringer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 20, 2003 2:23 PM
Subject: RE: [LegacyUG] Cemeteries
> I hope you all can help me settle on a logical and consistent method of
> entering locations, as I am in the process of learning this software.
>
> ISSUE #1
> =========
> I am still unsettled about what to do with names of cemeteries,
> hospitals, churches, etc (hereafter called special location names).
> Here are some examples of what I want to enter:
>
> Evergreen Memorial Park, McMinnville, Yamhill County, Oregon
> St. Vincents Hospital, Portland, Multnomah County, Oregon
>
> This pattern adheres to a set of guidelines, supposedly from a Family
> History Center staff member:
> http://www.geocities.com/Heartland/Pointe/5802/images/FAQ/047i.html
>
> Unfortunately, Legacy does not play well with this "standard". In
> Legacy, we are supposed to enter City, County, State, Country, using
> extra commas where certain elements are unknown, such as this:
>
> Albany, Linn County, Oregon, USA
> , Linn County, Oregon, USA
> ,, Oregon, USA
> ,, Oregon,
> etc.
>
> I have not seen any official instructions from Millenia on what to do
> with special lcoations, such as names of cemeteries, schools, churches,
> hospitals, etc. As mentioned previously in this thread, you CAN enter
> specal locations in event address, but these never get into an exported
> GEDCOM, which makes them pretty useless for sharing data (unless the
> lucky recipient also has Legacy).
>
> I kind of like Jim's suggested workaround, in which special locations
> are entered after the country. However, when exporting to a GEDCOM, is
> it possible to move the special location back to the head of the
> location field, to comply with the "standard" order?
>
> On a related note, it certainly seems like there could be a closer tie
> between location and event address in Legacy. Why do we need to enter
> city, state, and country twice?
>
> ISSUE #2
> =========
> What should be done when a location is uncertain, such as if I think an
> individual was born in New Jersey but not definitely. There are some
> oblique hints in Legacy that estimated dates and places are indicated by
> enclosing them in angle brackets. Should I enter this:
> ,,<New Jersey>, USA
>
> or this:
> <,,New Jersey, USA>
>
> Or just leave it blank?
>
> Thanks, Andy
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jim
> Winfrey
> Sent: Friday, June 20, 2003 5:04 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [LegacyUG] Cemeteries
>
>
> Monty,
>
> The convention you use for entering cemeteries, churches, schools, etc
> (Local Sites) depends on what you intend to do with your data. If you
> are
> going to use it only for your research you can do whatever best meets
> your
> needs and that looks good on reports. If you are going to work with a
> group
> of researchers as I do then it becomes a different animal. Legacy's
> address
> function does not work well if you export via gedcom to other
> researchers
> because the address is stripped from the event and put in as a general
> address. Second, there are quasi place structures in place in other
> genealogy programs. While they are different, most structured place
> name
> programs recognize 4-5 elements to a place name. I use the form "Town,
> County, State, Country, Local Site" because it works well with other
> programs and it makes sorting within Legacy work very well. When
> editing in
> Legacy, I sort by "Country, State, County, Town, Local Site". This
> makes it
> very easy to find common elements and to edit. For reports, etc within
> Legacy I use the Short Location Name because it takes less space but
> these
> short names also do not export in gedcom.
>
> So, I guess the answer is to think it through and determine what your
> purpose is for your data and make your decisions accordingly.
>
> Jim
> ----- Original Message -----
> From: "Montford Reed" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, June 19, 2003 9:37 PM
> Subject: [LegacyUG] Cemeteries
>
>
> | Hi,
> | Has there been a consensus on how to enter rural cemeteries in the
> Burial
> | box? Many rural cemeteries are remote from "places" and are known by
> family
> | names. Example: Moreland Cemetery, Powell, Kentucky, USA. Or, enter
> the
> | cemetery as an event, and the burial place looks like: , Powell,
> Kentucky,
> | USA. The former seems to make much more sense.
> |
> | I realize this has been discussed previously, but I get in a "stew"
> every
> | time I run into the problem.
> | Monty
> |
> | Legacy User Group Etiquette guidelines can be found at:
> | http://www.LegacyFamilyTree.com/Etiquette.asp
> |
> | To find past messages, please go to our searchable archives at:
> | http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
> |
> | To unsubscribe please visit:
> | http://www.legacyfamilytree.com/LegacyLists.asp
>
> Legacy User Group Etiquette guidelines can be found at:
> http://www.LegacyFamilyTree.com/Etiquette.asp
>
> To find past messages, please go to our searchable archives at:
> http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
>
> To unsubscribe please visit:
> http://www.legacyfamilytree.com/LegacyLists.asp
>
> Legacy User Group Etiquette guidelines can be found at:
> http://www.LegacyFamilyTree.com/Etiquette.asp
>
> To find past messages, please go to our searchable archives at:
> http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
>
> To unsubscribe please visit:
> http://www.legacyfamilytree.com/LegacyLists.asp
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
