Yay!!!! You made my day. My goals is to serve people and help them accomplish things they have wanted to do but didn't know now.

Glad it helped! I tested everything on a database with over 1,000 persons. It was a merged mess from multiple sources. I figured we could all learn to clean things up a bit. I hadn't heard anyone else take the time to explain this. So, I did my best. I hope you'll share this video with others in your genealogy circle.

You're so welcome. I have a way to do this in RootsMagic that will come out next week. In your genealogy circles, please let other FTM users know about this video.

You are welcome!

YOU MADE MY DAY! I'm so happy to have helped you learn the tools to make your life easier.

My pleasure!

Wow. Thanks. My pleasure.

No worries. I had thousands!

😃😄😃😄😃😄😃😄😃😄 This is the only way I know how to smile like crazy after reading this response!

The unresolved place list is beneficial for large updates. However, for fine tuning, I like doing things either within a profile as I'm working on a person or from the place list. Thus, I wanted to ensure I covered the three different ways.

So, removing the Leinster was NOT a good recommendation by Family Tree Maker. AND users need to be aware that Dublin could be a county OR a city. Dang. You just gave us more evidence that I'm not a fan of some of the FTM recommendations for resolving places. And, the need to insert more education of locations into our genealogy software programs.

@@FamilyHistoryFanatics I know it's hard for Americans to adjust, but Irish counties don't use County as a suffix but as a prefix. Thus, "Dublin, Co. Dublin, Ireland" for postal addresses. The anomalous "King's County" and "Queen's County" are now "Co. Offaly" and "Co. Laois". In England, County Durham uses the same form.

Thanks for sharing your approach to place names. It would be nice if there was some consistency for all to work towards. That way, when someone is unfamiliar with an area, then, they can look to the common standard to learn more, instead of becoming more and more confused. Would you agree?

@@FamilyHistoryFanatics Yep! That's why I use Ancestry's recommended place names of city, county, state, country. I don't see a consistent format for Irish records, though. The records themselves sometimes use civil parish, or barony as it existed when the record was made. Things are different today! Yikes!

Thanks so much for educating me. So, I'm now more confident that I don't like the restating the location from Dublin, Leinster, Ireland is not well done. I do wonder, should it thus be Dublin County, Leinster, Ireland until we know for certain that it was in Dublin, Dublin County, Leinster, Ireland? Thanks so much for helping myself, and others learn.

@@FamilyHistoryFanatics Personally, i just put Dublin, Ireland ... unless I have a specific street address etc ... the last time that I looked at using the FTM address functionality I hated that it tries to omit street addresses ... and for that reason, i used it to check addresses but did not accept a lot of changes ... i am happy with more info in the address to determine location within the city as it helps to locate family clusters ...

@@FamilyHistoryFanatics Dublin is not a large county ... en.wikipedia.org/wiki/County_Dublin

@@FamilyHistoryFanatics very few people in ireland would include Leinster in an address ... they know it is in the province of Leinster but it is not in daily use as part of an address ... I suppose it might be something like would you use 'Mid West' or 'East Coast' as part of a USA address ? maybe a generic locality description but not an address ...

If your trees are synced, you should be able to add information anywhere in the description field.

I'm SOOO glad you asked. That's next Monday's video.

You are correct. This is an debate that continues in the genealogy community and would be easily solved by technology already developed. For instance, one line could be the historic places names (which are critical to know to find genealogical records). And the second field could be the standardized place names which FamilySearch is pushing folks toward. What would be awesome is that when we then strive to print a family tree, we can opt for the historical or modern place names for our family members. But as researchers, we would have both.

Yes. I agree that the format was an acceptable standard in the past. I would prefer to say the confirmed location in the place field (United States) and the strong possibility in the notes. That way we're not propagating possibilities for misunderstandings.

Thanks for the tip. I thought I covered that as one of the various ways you can change names. However, if it wasn't clear, I'm so glad you shared your tip. It takes a community to cover all the ways to do things!

Yep. Check out this video kzfaq.info/get/bejne/hq2mbNyG1r2nj4U.html

Family Tree Builder is a MyHeritage product, correct? I'm not sure because I don't use that program since it only serves one website. But, you can use the terminology from this video to see if you can find out more in the help files of Family Tree Builder.

While the abbreviations make sense to you, many people become confused with other abbreviations, especially since those state abbreviations have changed over time. So, for the state, it's typically best to have that spelled out. The use of County is important in Ireland, because they often refer to their locations as County Down, County Kerry, etc. In the US, County is often recommended to be included so that people practice consistency and clarity. For instance, let's say you have a location of Denver, Colorado, United States? Is that Denver the city or Denver the county? Without the consistent use of County (regardless of whether you have a City preceding it or not), is worth considering for consistency sake. HOWEVER, if every platform uses geocoding and standardized place names for a second field, then our personal preference for the use of County or not can be trivial because the comparison of locations is based on the standardized field. Those are some of my thoughts.

ditto ! I still haven't recovered ... totally screwed up all my sources ... nightmare !

@@davidwilkes3845 I'm sorry it happened to you, too. Good luck with your recovery!

I'm sorry to hear of these issues. I have run into a few bugs from syncing. Some of the syncing in RootsMagic breaks when I do an update using FTM and want the persons to link to FS. It's kind of complicated. Genealogy software and updating online trees can be such a challenge. I wish there were easier systems.

David, sorry to hear about sources being messed up. However, I do know that sources between software programs and online trees are another nightmare that I'm not ready to figure out yet.

@@FamilyHistoryFanatics I think that everything is a challenge for me these days. Life is like, "Oh, she's getting old. Let's make her get there faster!" :) I wish there were easier systems, too. I don't think that I will ever get Legacy figured out, even with the manual and videos.

Yes. I have noticed that Family Tree Maker does try to push us to standardization. However, that standardization is not in line with what the geopolitical locations use. Some places really must have the township designation in order to be differentiated from another similarly named location. By contrast, RootsMagic allows it. So, that's one point for the other product.

@@FamilyHistoryFanatics I end up typing it in manually, but it bugs me to see the question mark next to it in the window.

What do I do? I strive for historically accurate place names and put the modern place names in the notes section. FTM and Ancestry try to force us into using modern place names but I have found it has created more confusion in my research because, as you mentioned, I look in the wrong county, state, or territory. So, if a program tries to force modern places, I disregard it and use historic names. Thankfully, FamilySearch allows for both names in their family tree. RootsMagic can work with that. I wish the other platforms would follow suit.

Fantastic question. The answer depends on the time your ancestor lived in Paddington. A quick search of the place revealed that it is an area within the City of Westminster, in central London. For modern names, then my guess is that place name could be Westminster, London, England (and then in your notes include Paddington) since the City of Westminster was established as a borough in 1965 by the amalgamation of the boroughs of Westminster, Paddington, and St. Marylebone. OR... Some websites say Paddington, London, England, United Kingdom, with a note that says it's part of the city of Westminster. In either case, you'll likely be using a note to add either Paddington or Westminster. Paddington, Westminster, London, England, United Kingdom does not seem accurate based on my preliminary exploration. I would need more time to dive into the place names to have a solid answer. In modern place name cases where things are ambiguous, I often refer to the postal address. For instance, I lived in Houston, Fort Bend County, Texas, United States. Many genealogical programs try to force that place into Houston, Harris County, Texas, United States. Heck, even Google Maps doesn't know this area exists. But, this little section of Fort Bend County was part of the city of Houston but also not. This unincorporated area with the city name of Houston and the county of Fort Bend affected where I went to school, where my parents voted, and where many of our court records are filed. (All of these activities happened in Fort Bend County, not Harris.) Therefore, I use the modern place name based on postal information. Prior to 1965, Paddington was in the county of Middlesex, so the likely accurate place would be Paddington, Middlesex, England back to the 1200s. That makes things easier, doesn't it?

I would recommend two things because you can't make FTM do what you want. 1. Use the legitimate city, county, state location. 2. Submit to Family Tree Maker Support and request an update of the location. You will have to submit documentation (like a FamilySearch Wiki or a official city page). www.mackiev.com/techsupport/ftm/livechat.html

I found that many of the Co that should be County entries were from early GEDcom users who were still in the constraints and shortcuts invented during typing of family group sheets for sharing. I had not suspected that this was an Ancestry problem.

Was I not clear in the title of the video or what I said. If not, I hope to make it more clear. The Family Tree Maker program is what I'm using to improve the place names on the Ancestry website. Let me know how I could be more clear.

@@FamilyHistoryFanatics thank you. I heard you say Family Tree Maker, but I didn't realize it was an app. I appreciate your help.

GREAT question. Thanks for looking so closely. The ticks on the left mean you're keeping what's currently in the database. The ticks on the right (with the grayed out lines) means you've changed the entry and you want Family Tree Maker to update the database to that name. Now, I didn't correct everything in this video so some entries will not seem to change when they should have because I was just running a small Demo. Does that help clarify that part?

@@FamilyHistoryFanatics Yes, thank you so much for answering my question. I do find FTM help notes on this subject very limiting. Could you please answer another question - I have a place 'Amounderness, Lancashire, England', this did not change its boundary in 1974, yet, it has not moved to the 'England' folder, why would that be?

It makes PERFECT sense to ignore until you have resolved the location. I do that all the time. I don't want to force a change until I'm ABSOLUTELY sure I know that the change recommended or implemented is accurate.

While it's not perfect, you could try the Google Reverse Image Search that I discussed in this video. kzfaq.info/get/bejne/rd15qJOQys7KaKs.html

I AGREE that Ancestry would do well to provide two location boxes and the geocoding option. However, customers have to demand it before they'll add it. I am starting the conversation but need others to contribute to the discussion. The location for an event field as “Huntington Township, York County(now Adams County), Pennsylvania, United States of America” is quite confusing. it would be best to use one or the other and use the Ancestry description field (and the one Family Tree Maker provides) for the 'now Adams County. It would serve the databases better and look cleaner. But I do agree that in any notes and supporting place fields that the 'now in this county' statement is so helpful. I LOVE the example you share in Pennsylvania because I have had something similar happen with Lycoming County, PA. But there are places all around the world that have had city, county, and country boundary changes. It would be best if we have the double location options that you mentioned. Fingers crossed?

That's a great question and that's my preferred method. You will be fighting with Family Tree Maker and Ancestry because they have a modern place name preference. I use Ancestry and I keep my historic place names even though the website constantly asks me to convert. So, the decision is yours. Keep the modern and deal with the problems I expressed in this video. Or convert and put the historic place names in notes for each event. I WISH there was a better answer but this is one of my biggest gripes.

@@FamilyHistoryFanatics Thanks. Sounds like a great minds category. I too put historic place names in notes for the corresponding facts. A case in point, I have Virginia ancestors dating back to the 1700s. The current naming for where they lived is Preston County WV, which has no records for that era (I checked). They suggested checking with Monongalia County, the county they were created from, while still VA, and the WV and VA Archives. Someone who had not checked with that County would not have known this, and Preston County is not alone. You don't know what you don't know un til you know you don't know.

You can. That video goes live next week. Stay tuned!

@@FamilyHistoryFanatics can’t wait.

There are very few free programs in genealogy. Sorry, this one is rather expensive compared to others.

I'm not certain what document that you're finding that statement on. Who created the document will be source to understand what the phrase means. I can give you an example. For early US Census records (something I mentioned in this video kzfaq.info/get/bejne/aMB3q5t-zNnbgHU.html), Free white males or females means they are not servants or slaves. They are citizens in the US who are not obligated to another person who has reached their majority. But, it all depends on the creator of the document and the purposes they created it.

Agreed. You have to look through each option very carefully.

Truer words have not be said before this comment. Thanks, and I firmly agree. I would prefer the entry you put forth to be split as follows. Place description: 826 Wigan Rd Location = Bolton, Lancashire, England

@@FamilyHistoryFanatics The address was pasted straight from the Ancestry page. There ought not to be any distinction between "address", "place" and "location". The CORRECT address would be "826, Wigan Rd, Bolton, Lancashire, England", which is what would have appeared on the front of an envelope at the time.

@@FamilyHistoryFanatics FindMyPast trees also make this absurd distinction between parts of an address. Their web interface has a sheet for tidying up place names, but they try to hide street addresses from you. Good software not only lets you adjust the addresses, but lts you find out where those addresses have been used, so you can cross-check before making changes.