RootsWeb.com Mailing Lists
Previous Page      Next Page
Total: 1800/10000
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. BJ via
    3. I'm sorry Christine, I didn't intend to be overly critical of what you are attempting to accomplish. I think I would have approached it slightly differently by leaving the entry as "Gold Coast" and then gone to the Place work area and moved the pin on the map so it was pointing to "Ghana". BJ On 3/28/2015 6:19 AM, Christine Benson via wrote: > I am new to this so am still experimenting and finding my personal > preferences. But I decided to resolve "Gold Coast" to include "Ghana", not > because the name was incorrect, but because I knew I would need reminding > where the place was. But I "Ignored" "Wadhurst, East Sussex" as the place is > correct at the time of the event and I know exactly where the place is. > > Christine > > -----Original Message----- > From: BJ via > Sent: Saturday, March 28, 2015 3:18 AM > To: ftm-tech@rootsweb.com > Subject: Re: [FTM-TECH] Resolving place names (from the thread Program > crashes when resolving place names) > > I'm continually confused with this obsession of resolving the place > name. The PNA is a tool to help researchers enter the Place name in a > uniform format but it only a tool. Its use not required or mandated. > So why do these contrivances just to remove the flag. For a historical > place whose name has been changed or no longer exists, why not simply > enter the name as documented and then ignore the flag. You can ignore > it in one of two ways: just pretend it isn't there (my preference) or > click the ignore option telling FTM to discontinue displaying the > unresolved flag (indicator). > > I'm sorry but it just seems like a lot of effort for no real purpose. > > BJ > > > ********************************** > List information page > http://lists.rootsweb.com/index/other/Software/FTM-TECH.html > > ------------------------------- > To unsubscribe from the list, please send an email to FTM-TECH-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message >

    03/28/2015 02:17:41
    1. Re: [FTM-TECH] Resolving place names in FTM
    2. BJ via
    3. Great example of how to use the PNA as a tool. That is its intent. I do essentially the same thing. When I come across something which doesn't make sense to resolve, I leave it. As an example, I have a lady who documentation says she was born in Kemp, Texas. I tried to resolve it, the problem is there are two counties with a town named Kemp. I have nothing to indicate which of the two counties is correct so I just left it as Kemp, Texas unresolved so I will keep looking for more definitive documentation. BJ On 3/28/2015 12:03 PM, John Okerson via wrote: > I have listened for a good long while on this topic. When I converted from > FTM 16 to FTM 2012, I had a very large list of place names, many of which > were not recognized. I was able to rid my database of about 50% by using > the PNA. I do it differently than most, but I am happy with it. The BIG > thing the several hundred hours of work did for me was eliminate spelling > errors and items placed in location when I feel they belong. I had multiple > entries which meant the same place and many where a misspelling crept in. > > The net result is that my list of places is now completely recognized. > Thus, as I work on the database, if I make a misteak - spelling > intentional - then it is easy enough for the PNA to point it out to me > before I post to Ancestry. > > That is how I work it. > > John Okerson > Lakeland, TN > > ********************************** > List information page > http://lists.rootsweb.com/index/other/Software/FTM-TECH.html > > ------------------------------- > To unsubscribe from the list, please send an email to FTM-TECH-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message >

    03/28/2015 02:10:37
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. Jim Hoke via
    3. BJ, You've hit the nail on the head. The PNA is a helpful tool in standardizing format and it doesn't matter whether a location is resolved by the PNA or not. The important thing is that the documentation captures the location information at the time of the event. The documentation of historical locations becomes more useful when related to the present. Indicating in the documentation that Gold Coast, West Africa is now Ghana is an example. Jim ------------------------------------------------ Date: Fri, 27 Mar 2015 21:18:21 -0600 From: BJ <oldtrails@gmx.com> Subject: Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names) To: ftm-tech@rootsweb.com Message-ID: <55161D7D.7080100@gmx.com> Content-Type: text/plain; charset=windows-1252; format=flowed I'm continually confused with this obsession of resolving the place name. The PNA is a tool to help researchers enter the Place name in a uniform format but it only a tool. Its use not required or mandated. So why do these contrivances just to remove the flag. For a historical place whose name has been changed or no longer exists, why not simply enter the name as documented and then ignore the flag. You can ignore it in one of two ways: just pretend it isn't there (my preference) or click the ignore option telling FTM to discontinue displaying the unresolved flag (indicator). I'm sorry but it just seems like a lot of effort for no real purpose. BJ

    03/28/2015 07:51:50
    1. [FTM-TECH] Resolving place names in FTM
    2. John Okerson via
    3. I have listened for a good long while on this topic. When I converted from FTM 16 to FTM 2012, I had a very large list of place names, many of which were not recognized. I was able to rid my database of about 50% by using the PNA. I do it differently than most, but I am happy with it. The BIG thing the several hundred hours of work did for me was eliminate spelling errors and items placed in location when I feel they belong. I had multiple entries which meant the same place and many where a misspelling crept in. The net result is that my list of places is now completely recognized. Thus, as I work on the database, if I make a misteak - spelling intentional - then it is easy enough for the PNA to point it out to me before I post to Ancestry. That is how I work it. John Okerson Lakeland, TN

    03/28/2015 07:03:22
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. Christine Benson via
    3. I am new to this so am still experimenting and finding my personal preferences. But I decided to resolve "Gold Coast" to include "Ghana", not because the name was incorrect, but because I knew I would need reminding where the place was. But I "Ignored" "Wadhurst, East Sussex" as the place is correct at the time of the event and I know exactly where the place is. Christine -----Original Message----- From: BJ via Sent: Saturday, March 28, 2015 3:18 AM To: ftm-tech@rootsweb.com Subject: Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names) I'm continually confused with this obsession of resolving the place name. The PNA is a tool to help researchers enter the Place name in a uniform format but it only a tool. Its use not required or mandated. So why do these contrivances just to remove the flag. For a historical place whose name has been changed or no longer exists, why not simply enter the name as documented and then ignore the flag. You can ignore it in one of two ways: just pretend it isn't there (my preference) or click the ignore option telling FTM to discontinue displaying the unresolved flag (indicator). I'm sorry but it just seems like a lot of effort for no real purpose. BJ

    03/28/2015 06:19:55
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. H R Worthington via
    3. Jim, I handle historical names differently AND I don't worry about the PNA. The Map is really close. I am more interested in the Grouping by the historical place names. I have a listing of when States became States. Place Name: Massachusetts Bay Colony nothing in Place Detail or Description I don't Ignore the unresolved place name, just don't worry about them in the UnResolved Place Names. What I don't want to see, in the Place Name on the screen is USA, prior to 1788 for Massachustts. Just another approach Russ  ___________________________ Mailto:rworthington@att.net From: Jim Hoke via <ftm-tech@rootsweb.com> To: FTM-TECH mailing list submission <FTM-TECH@rootsweb.com> Sent: Friday, March 27, 2015 9:30 PM Subject: Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names) Christine, Thanks for the feedback.  I use a similar approach for locations in the U.S. when the facts occurred before the U.S. existed as a country.  For example, for the early years of Pennsylvania I use: Place detail:  Pennsylvania colony, British Colonial America (at the time) Place name:  Pennsylvania, USA Description:  [blank]

    03/27/2015 09:12:26
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. H R Worthington via
    3. Jim, As you Enter Place names, you have a visual indication IF that place name is in the PNA format. It's easy to see it and deal with it, right then and there (if you chose) IF you are entering a place name that is IN the right format, it will be presented to you to select. I rarely go to the Place workspace while doing data entry. I do check it a couple of times, especially IF I need to use the Place Detail screen.  Russ ___________________________ Mailto:rworthington@att.net From: Jim Hoke <j12251225@gmail.com> To: ftm-tech@rootsweb.com Cc: 'H R Worthington' <rworthington@att.net> Sent: Friday, March 27, 2015 8:49 PM Subject: RE: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names) Russ, Let’s say you’ve just entered into FTM, while in the People workspace, a location-related fact, such as the residence of a person.  Because there are numerous errors in FTM 2014's application of the Place Name Authority, I find it advisable to check whether the PNA has properly located the place geographically on the map.  After entering the fact in the People workspace, one way of doing this is to click on the tab for the Places workspace, then locate the place name of interest in the list of place names.  This is a rather tedious process when one is entering a large group of facts at numerous locations. It would be much more straight forward if one could click on the place name in the Place line of the fact in the People workspace and then have the location displayed on a map in the Places workspace.  I was hoping FTM 2014 might provide this functionality, but I haven't been able to find it, if it does. Jim ---------------------------------------------------------------- From: H R Worthington [mailto:rworthington@att.net] Sent: Thursday, March 26, 2015 11:37 AM To: Jim Hoke; ftm-tech@rootsweb.com Subject: Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names) Jim, You asked: 4.  My question involves FTM 2014 navigation.  In the People workspace under the Person tab, how can one easily get to a map showing the location of a place-related fact? If you are map a PERSON, why not do that in the Places Workspace, selecting Person ? Russ

    03/27/2015 07:11:44
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. Allie Warnier-Susko via
    3. Amen to that BJ. Allie -----Original Message----- From: BJ via Sent: Friday, March 27, 2015 11:18 PM To: ftm-tech@rootsweb.com Subject: Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names) I'm continually confused with this obsession of resolving the place name. The PNA is a tool to help researchers enter the Place name in a uniform format but it only a tool. Its use not required or mandated. So why do these contrivances just to remove the flag. For a historical place whose name has been changed or no longer exists, why not simply enter the name as documented and then ignore the flag. You can ignore it in one of two ways: just pretend it isn't there (my preference) or click the ignore option telling FTM to discontinue displaying the unresolved flag (indicator). I'm sorry but it just seems like a lot of effort for no real purpose. BJ On 3/27/2015 7:30 PM, Jim Hoke via wrote: > Thanks for the feedback. I use a similar approach for locations in the > U.S. > when the facts occurred before the U.S. existed as a country. For > example, > for the early years of Pennsylvania I use: > > Place detail: Pennsylvania colony, British Colonial America (at the time) > > Place name: Pennsylvania, USA > > Description: [blank] > > > > It's rather contrived, but at least indicates the historical context of > the > fact in a way that's resolved by the Place Name Authority. ********************************** List information page http://lists.rootsweb.com/index/other/Software/FTM-TECH.html ------------------------------- To unsubscribe from the list, please send an email to FTM-TECH-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

    03/27/2015 05:30:01
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. Jim Hoke via
    3. Christine, Thanks for the feedback. I use a similar approach for locations in the U.S. when the facts occurred before the U.S. existed as a country. For example, for the early years of Pennsylvania I use: Place detail: Pennsylvania colony, British Colonial America (at the time) Place name: Pennsylvania, USA Description: [blank] It's rather contrived, but at least indicates the historical context of the fact in a way that's resolved by the Place Name Authority. Jim -------------------------------------------------------------- From: "Christine Benson" <christinebenson313@btinternet.com> Subject: Re: [FTM-TECH] Resolving place names (from the thread Programcrasheswhen resolving place names) Date: Thu, 26 Mar 2015 21:14:36 -0000 References: <001c01d067d7$ef0583d0$cd108b70$@gmail.com> In-Reply-To: <001c01d067d7$ef0583d0$cd108b70$@gmail.com> Hi Jim, Thanks for the idea of dealing with the Gold Coast. I like it. Not perfect, but I think the best that is available. Christine

    03/27/2015 03:30:13
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. BJ via
    3. I'm continually confused with this obsession of resolving the place name. The PNA is a tool to help researchers enter the Place name in a uniform format but it only a tool. Its use not required or mandated. So why do these contrivances just to remove the flag. For a historical place whose name has been changed or no longer exists, why not simply enter the name as documented and then ignore the flag. You can ignore it in one of two ways: just pretend it isn't there (my preference) or click the ignore option telling FTM to discontinue displaying the unresolved flag (indicator). I'm sorry but it just seems like a lot of effort for no real purpose. BJ On 3/27/2015 7:30 PM, Jim Hoke via wrote: > Thanks for the feedback. I use a similar approach for locations in the U.S. > when the facts occurred before the U.S. existed as a country. For example, > for the early years of Pennsylvania I use: > > Place detail: Pennsylvania colony, British Colonial America (at the time) > > Place name: Pennsylvania, USA > > Description: [blank] > > > > It's rather contrived, but at least indicates the historical context of the > fact in a way that's resolved by the Place Name Authority.

    03/27/2015 03:18:21
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. Jim Hoke via
    3. Russ, Let’s say you’ve just entered into FTM, while in the People workspace, a location-related fact, such as the residence of a person. Because there are numerous errors in FTM 2014's application of the Place Name Authority, I find it advisable to check whether the PNA has properly located the place geographically on the map. After entering the fact in the People workspace, one way of doing this is to click on the tab for the Places workspace, then locate the place name of interest in the list of place names. This is a rather tedious process when one is entering a large group of facts at numerous locations. It would be much more straight forward if one could click on the place name in the Place line of the fact in the People workspace and then have the location displayed on a map in the Places workspace. I was hoping FTM 2014 might provide this functionality, but I haven't been able to find it, if it does. Jim ---------------------------------------------------------------- From: H R Worthington [mailto:rworthington@att.net] Sent: Thursday, March 26, 2015 11:37 AM To: Jim Hoke; ftm-tech@rootsweb.com Subject: Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names) Jim, You asked: 4. My question involves FTM 2014 navigation. In the People workspace under the Person tab, how can one easily get to a map showing the location of a place-related fact? If you are map a PERSON, why not do that in the Places Workspace, selecting Person ? Russ

    03/27/2015 02:49:28
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crasheswhen resolving place names)
    2. Christine Benson via
    3. Hi Jim, Thanks for the idea of dealing with the Gold Coast. I like it. Not perfect, but I think the best that is available. Christine

    03/26/2015 03:14:36
    1. Re: [FTM-TECH] Outline Descendant Report - How to Include Sources
    2. H R Worthington via
    3. Tom, I think that if you LOOK at an ODR, Outline Descendant Report, you will quickly see what you might NOT want to include Citations. Even the Superscript numbers would be totally confusing. Then to have to have the End Notes at the bottom ? Perhaps the ODR isn't the best way to present the information you want. Yes, I have thought about this topic for a while, and that is where I come out with it. I wouldn't want to confuse some one trying to look at an ODR and try to understand that many numbers that would appear around a person. One user's opinion. Russ ___________________________ Mailto:rworthington@att.net From: Tom Herson via <ftm-tech@rootsweb.com> To: FTM-Tech <ftm-tech@rootsweb.com> Sent: Thursday, March 26, 2015 1:20 PM Subject: [FTM-TECH] Outline Descendant Report - How to Include Sources I'm using the latest update of FTM2014 with Windows 8.1 I want to run an Outline Descendant Report for Direct Ancestors of mine and their siblings. I do not find a place to opt to include Sources. Can someone tell me how to do it or is it not possible?

    03/26/2015 11:59:29
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. H R Worthington via
    3. Jim, You asked: 4.  My question involves FTM 2014 navigation.  In the People workspace under the Person tab, how can one easily get to a map showing the location of a place-related fact?  If you are map a PERSON, why not do that in the Places Workspace, selecting Person ? Russ ___________________________ Mailto:rworthington@att.net From: Jim Hoke via <ftm-tech@rootsweb.com> To: FTM-TECH mailing list submission <FTM-TECH@rootsweb.com> Sent: Thursday, March 26, 2015 11:17 AM Subject: [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names) BJ, I've several thoughts and a question as follow-ups to your very helpful comments.  1.  You said you tend to enter the house number/street address in the fact Description field to cut down on the number of entries in the place name list.  My personal preference at this point is to include address-related information (such as street number, street name, city/town [if different from the information in the Place field], and zip code) in the Place Detail field.  As you point out, this creates a unique entry in the place name list.  A benefit, however, is that one can then associate a latitude/longitude location with that entry so the location of the address can be plotted on the FTM map in the Places workspace.  For those folks who create a separate Address fact in addition to a location-related fact, I assume they keep the Address fact's location unresolved with respect to the Place Name Authority. 2.  Like you, I prefer to preserve the original location information as much as possible.  The PNA doesn't make this easy, however, as it is an authority of the present and not of the past.  If I understand correctly, you would have handled Christine's challenge as follows, leaving the entry unresolved with respect to the PNA: Place detail: Place name:  Gold Coast, West Africa Description: Here's how I handle the case: Place detail:  Gold Coast, West Africa (at the time) Place name:  Ghana Description: This allows resolution with respect to the PNA of the location using its current name, while preserving information on the former name. 3.  One pet peeve I have with the PNA is that it uses a 4-tier jurisdictional hierarchy instead of a 5-tier one.  Frequently there are villages/towns in the PNA that are in townships in the PNA.  One option for handling this situation is to use the village/town as the fourth tier level, thereby taking township out of the hierarchy for that entry.  An alternative is to use township as the fourth tier level, indicating the village/town under Place detail.  This can be undesirable because the village/town then cannot have any locations placed under it in the FTM/PNA representation of the hierarchy.  Thus, neither option is very satisfying. 4.  My question involves FTM 2014 navigation.  In the People workspace under the Person tab, how can one easily get to a map showing the location of a place-related fact?  In FTM 2014 it is easy to go from the Places workspace (showing the geographic location of a place on a map) to the facts associated with that place under the People workspace.  Unless I've overlooked something, going the opposite direction is not nearly as easy.

    03/26/2015 09:36:53
    1. Re: [FTM-TECH] Outline Descendant Report - How to Include Sources
    2. BJ via
    3. Unfortunately, FTM doesn't provide any way to include the sources or notes on either the Outline Descendant Report nor the Outline Ancestry Report. Interestingly, the note options are displayed but they are dimmed and not available. Include Sources option is not even displayed. BJ On 3/26/2015 11:20 AM, Tom Herson via wrote: > I'm using the latest update of FTM2014 with Windows 8.1 > > I want to run an Outline Descendant Report for Direct Ancestors of mine > and their siblings. I do not find a place to opt to include Sources. Can > someone tell me how to do it or is it not possible? > > Thanks, > > Tom Herson > Ithaca, NY > > > ********************************** > List information page > http://lists.rootsweb.com/index/other/Software/FTM-TECH.html > > ------------------------------- > To unsubscribe from the list, please send an email to FTM-TECH-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message >

    03/26/2015 07:26:30
    1. [FTM-TECH] Outline Descendant Report - How to Include Sources
    2. Tom Herson via
    3. I'm using the latest update of FTM2014 with Windows 8.1 I want to run an Outline Descendant Report for Direct Ancestors of mine and their siblings. I do not find a place to opt to include Sources. Can someone tell me how to do it or is it not possible? Thanks, Tom Herson Ithaca, NY

    03/26/2015 07:20:23
    1. Re: [FTM-TECH] Outline Descendant Report - How to Include Sources
    2. John Okerson via
    3. > I think that if you LOOK at an ODR, Outline Descendant Report, you will > quickly see what you might NOT want to include Citations. Even the > Superscript numbers would be totally confusing. Then to have to have the > End Notes at the bottom ? Perhaps the ODR isn't the best way to present the information you want. Yes, I have thought about this topic for a while, and that is where I come out with it. I wouldn't want to confuse some one trying to look at an ODR and try to understand that many numbers that would appear around a person. One user's opinion. Personally, I prefer Descendant Report - just seems better put together! John

    03/26/2015 07:11:44
    1. Re: [FTM-TECH] Outline Descendant Report - How to Include Sources
    2. John Okerson via
    3. >I'm using the latest update of FTM2014 with Windows 8.1 I want to run an Outline Descendant Report for Direct Ancestors of mine and their siblings. I do not find a place to opt to include Sources. Can someone tell me how to do it or is it not possible? I use FTM 2014 and Windows 7 Professional, but it should be identical. Choose whichever ancestor you wish, then go to Publish, Collection, Relationship Reports and choose ODR. Once there, single left click on the leftmost icon in the right column under the O. It has three3 dots and a right pointing arrow. This allow you to choose which facts to include. Choose Source and it should work for you. Good luck. John Okerson

    03/26/2015 06:31:12
    1. Re: [FTM-TECH] Resolving place names (from the thread Program crasheswhen resolving place names)
    2. Allie Warnier-Susko via
    3. I put extra address information under NOTES. As a matter of fact I use NOTES extensively. Allie -----Original Message----- From: Jim Hoke via Sent: Thursday, March 26, 2015 11:17 AM To: FTM-TECH mailing list submission Subject: [FTM-TECH] Resolving place names (from the thread Program crasheswhen resolving place names) BJ, I've several thoughts and a question as follow-ups to your very helpful comments. 1. You said you tend to enter the house number/street address in the fact Description field to cut down on the number of entries in the place name list. My personal preference at this point is to include address-related information (such as street number, street name, city/town [if different from the information in the Place field], and zip code) in the Place Detail field. As you point out, this creates a unique entry in the place name list. A benefit, however, is that one can then associate a latitude/longitude location with that entry so the location of the address can be plotted on the FTM map in the Places workspace. For those folks who create a separate Address fact in addition to a location-related fact, I assume they keep the Address fact's location unresolved with respect to the Place Name Authority. 2. Like you, I prefer to preserve the original location information as much as possible. The PNA doesn't make this easy, however, as it is an authority of the present and not of the past. If I understand correctly, you would have handled Christine's challenge as follows, leaving the entry unresolved with respect to the PNA: Place detail: Place name: Gold Coast, West Africa Description: Here's how I handle the case: Place detail: Gold Coast, West Africa (at the time) Place name: Ghana Description: This allows resolution with respect to the PNA of the location using its current name, while preserving information on the former name. 3. One pet peeve I have with the PNA is that it uses a 4-tier jurisdictional hierarchy instead of a 5-tier one. Frequently there are villages/towns in the PNA that are in townships in the PNA. One option for handling this situation is to use the village/town as the fourth tier level, thereby taking township out of the hierarchy for that entry. An alternative is to use township as the fourth tier level, indicating the village/town under Place detail. This can be undesirable because the village/town then cannot have any locations placed under it in the FTM/PNA representation of the hierarchy. Thus, neither option is very satisfying. 4. My question involves FTM 2014 navigation. In the People workspace under the Person tab, how can one easily get to a map showing the location of a place-related fact? In FTM 2014 it is easy to go from the Places workspace (showing the geographic location of a place on a map) to the facts associated with that place under the People workspace. Unless I've overlooked something, going the opposite direction is not nearly as easy. Jim Hoke ------------------------------ Message: 11 Date: Tue, 24 Mar 2015 18:42:48 -0600 From: BJ <oldtrails@gmx.com> Subject: Re: [FTM-TECH] Program crashes when resolving place names To: ftm-tech@rootsweb.com Message-ID: <55120488.2060202@gmx.com> Content-Type: text/plain; charset=windows-1252; format=flowed ... I understand the desire to incorporate the house number and street address into the Place name; however, you need to understand - that will create a unique entry for each house number and street in your list of Place names. Personally, I think creates too many unique place names with very little benefit. I normally want the place names to reflect a group. Therefore, I will enter the Cemetery name along with the place name. In most instances, I will have multiple facts associated with a given cemetery. If you do not use the hierarchical listing, you will wind up with one listing for every house number street combination. Even if you use the hierarchical listing, the place names will be grouped under the Country name, State name, County name, City name with one entry for each house number street address combination. Again that tends to be too many for me to browse through efficiently. So I tend to enter the house number street address in the fact Description field. This keeps my place names to a more manageable list making it easier to use Fast Find in the Place Names. ... Hope this helps. BJ ------------------------------ Message: 3 Date: Wed, 25 Mar 2015 15:28:55 -0600 From: BJ <oldtrails@gmx.com> Subject: Re: [FTM-TECH] Program crashes when resolving place names To: ftm-tech@rootsweb.com Message-ID: <55132897.30001@gmx.com> Content-Type: text/plain; charset=windows-1252; format=flowed .. > What do you do with the place Gold Coast, West Africa? I know it is now > Ghana but it wasn't at the time. I would probably handle it this way as I prefer to preserve the original data as much as possible. I would enter the Place name, "Gold Coast, West Africa" and leave it as unresolved. The "unresolved" indicator is simply an advisory flag which brings it to your attention. It doesn't mean the information is incorrect but simply alerts you the the fact it is not in the Place Name Authority data base. Alternately, if you want to get rid of the "unresolved" indicator, you can elect to ignore the alert. ********************************** List information page http://lists.rootsweb.com/index/other/Software/FTM-TECH.html ------------------------------- To unsubscribe from the list, please send an email to FTM-TECH-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

    03/26/2015 06:30:06
    1. [FTM-TECH] Resolving place names (from the thread Program crashes when resolving place names)
    2. Jim Hoke via
    3. BJ, I've several thoughts and a question as follow-ups to your very helpful comments. 1. You said you tend to enter the house number/street address in the fact Description field to cut down on the number of entries in the place name list. My personal preference at this point is to include address-related information (such as street number, street name, city/town [if different from the information in the Place field], and zip code) in the Place Detail field. As you point out, this creates a unique entry in the place name list. A benefit, however, is that one can then associate a latitude/longitude location with that entry so the location of the address can be plotted on the FTM map in the Places workspace. For those folks who create a separate Address fact in addition to a location-related fact, I assume they keep the Address fact's location unresolved with respect to the Place Name Authority. 2. Like you, I prefer to preserve the original location information as much as possible. The PNA doesn't make this easy, however, as it is an authority of the present and not of the past. If I understand correctly, you would have handled Christine's challenge as follows, leaving the entry unresolved with respect to the PNA: Place detail: Place name: Gold Coast, West Africa Description: Here's how I handle the case: Place detail: Gold Coast, West Africa (at the time) Place name: Ghana Description: This allows resolution with respect to the PNA of the location using its current name, while preserving information on the former name. 3. One pet peeve I have with the PNA is that it uses a 4-tier jurisdictional hierarchy instead of a 5-tier one. Frequently there are villages/towns in the PNA that are in townships in the PNA. One option for handling this situation is to use the village/town as the fourth tier level, thereby taking township out of the hierarchy for that entry. An alternative is to use township as the fourth tier level, indicating the village/town under Place detail. This can be undesirable because the village/town then cannot have any locations placed under it in the FTM/PNA representation of the hierarchy. Thus, neither option is very satisfying. 4. My question involves FTM 2014 navigation. In the People workspace under the Person tab, how can one easily get to a map showing the location of a place-related fact? In FTM 2014 it is easy to go from the Places workspace (showing the geographic location of a place on a map) to the facts associated with that place under the People workspace. Unless I've overlooked something, going the opposite direction is not nearly as easy. Jim Hoke ------------------------------ Message: 11 Date: Tue, 24 Mar 2015 18:42:48 -0600 From: BJ <oldtrails@gmx.com> Subject: Re: [FTM-TECH] Program crashes when resolving place names To: ftm-tech@rootsweb.com Message-ID: <55120488.2060202@gmx.com> Content-Type: text/plain; charset=windows-1252; format=flowed ... I understand the desire to incorporate the house number and street address into the Place name; however, you need to understand - that will create a unique entry for each house number and street in your list of Place names. Personally, I think creates too many unique place names with very little benefit. I normally want the place names to reflect a group. Therefore, I will enter the Cemetery name along with the place name. In most instances, I will have multiple facts associated with a given cemetery. If you do not use the hierarchical listing, you will wind up with one listing for every house number street combination. Even if you use the hierarchical listing, the place names will be grouped under the Country name, State name, County name, City name with one entry for each house number street address combination. Again that tends to be too many for me to browse through efficiently. So I tend to enter the house number street address in the fact Description field. This keeps my place names to a more manageable list making it easier to use Fast Find in the Place Names. ... Hope this helps. BJ ------------------------------ Message: 3 Date: Wed, 25 Mar 2015 15:28:55 -0600 From: BJ <oldtrails@gmx.com> Subject: Re: [FTM-TECH] Program crashes when resolving place names To: ftm-tech@rootsweb.com Message-ID: <55132897.30001@gmx.com> Content-Type: text/plain; charset=windows-1252; format=flowed .. > What do you do with the place Gold Coast, West Africa? I know it is now > Ghana but it wasn't at the time. I would probably handle it this way as I prefer to preserve the original data as much as possible. I would enter the Place name, "Gold Coast, West Africa" and leave it as unresolved. The "unresolved" indicator is simply an advisory flag which brings it to your attention. It doesn't mean the information is incorrect but simply alerts you the the fact it is not in the Place Name Authority data base. Alternately, if you want to get rid of the "unresolved" indicator, you can elect to ignore the alert.

    03/26/2015 05:17:10