I have updated all my Place Name data in RM to include the full name of a state (Montana vs MT) but the changes are not showing up in Ancestry. What am I doing wrong?
Thanks in advance.
1 Like
a screenshot might help others.
I assume you are referring to the fact/event?
Just changing a place name doesnât trigger a change to Ancestry. There has to be another change.
Here is an example. In looking at Birth, I corrected details to show New Hampshire but Ancestry still shows NH.
Could you give an example of what other change I could make to trigger Ancestry? Thank you.
some changes seem to be a bit of mystery of what criteria counts and does not trigger a âchanged personâ I do not maintain that way so I do not know from personal experience
(on side note I spent most of my first 40 years in NH)
I could see Ancestry not equating NH vs. New Hampshire as âa differenceâ, perhaps because their Places toponomy is already configured to recognize and search either of those as one and the same. Have not used Tree Share, but if what MYoung says is true and quantity is a metric, I wonder if a global replacement using Places>Tools>Search and Replace might trigger changes:
As others have already mentioned, the issue is almost certainly that you changed the spelling of all the place names in the Place list. In the very first release of TreeShare, that triggered a âchanged personâ for each person who had a fact for one of the changed places. Therefore, a relatively small number of changes to your place list could easily result in hundreds or thousands of people who needed to be copied back to Ancestry, one person at a time.
As a result of this issue, TreeShare was changed almost immediately so that changes in the Place list would not trigger changes for each person who had a fact for one of the changed places. As far as I know, the only thing that triggers TreeShare to mark a person as changed in RM is to do the change in the Edit Person screen. I do not believe that any changes in the Place List, the Source List, the Multimedia List, global Search and Replace, DataClean, or any other global updating method will trigger TreeShare.
I think you really only have three choices. One choice is to upload your RM database to a new Ancestry Tree. The second choice is to go into TreeShare and turn off the Only show changed people option. Then go through your database one person at a time and upload anything thatâs different from RM to Ancestry. The third choice is to accept that forever your RM database and your Ancestry tree will have different place names for many of your people.
Itâs worth mentioning that even if the change had not been made in TreeShare to ignore global changes in RM, you would still be in a similar situation. You still would have had to use something similar to my second option where you uploaded anything that was different from RM to Ancestry, one person at a time. It would only have been for the people where a place name had changed, but it sounds like thatâs nearly everybody in your database.
3 Likes
It is the same problem in the opposite direction. Years ago in RM7 I allowed RM to add âUnited Kingdomâ to all my UK addresses using county check. It annoyed me soon after as the addresses got too long and, after all, there is only one England, Wales, Scotland & Northern Ireland. I globally changed all the addresses in RM to remove âUnited Kingdomâ but that never triggered any changes in Ancestry. As Jerry suggests, I now wait until I revisit a record in Ancestry to add or update the person and then remove the offending words. There is a positive though. When I see a âUnited Kingdomâ in Ancestry I know I havenât looked at that record for at least 5 years so then spend a bit more time looking for more recently released records for that individual and their immediate family (Censuses).
1 Like
Thanks for the explanation. I have decided I will just have to get over the the different place names for many people in my databases. I appreciate everyoneâs suggestions.
3 Likes