Jump to content


Member Since 12 Aug 2017
Offline Last Active Yesterday, 05:02 PM

Posts I've Made

In Topic: Places and Ancestry TreeShare

12 October 2017 - 04:12 PM

Thanks I will try that.

In Topic: Places and Ancestry TreeShare

11 October 2017 - 03:10 PM

Hmm, it is unhelpful that the place list is modal meaning that you cannot create the group while the looking at the place information especially if you have split the place and location facts. It would be so much easier if there were fewer modal screens and a way of RM automatically changing a changed flag when a change has been made.


However, thanks for the very complicated workaround.

In Topic: Places and Ancestry TreeShare

10 October 2017 - 02:16 PM

That is a partial workaround but that filter would then provide all the individuals who previously had the new place name and so they do not need sync'ing again with Ancestry.


The situation is something like this: If a hint provides a place "Here Upon There" but its official name is "Here-Upon-There" (i.e. with the hyphens) then it is easy in RM to change the non-hyphened version to the hyphened version (I normally just merge the two versions with the hyphened version remaining). However, if there are already 500 instances of the hyphened version in RM (and in Ancestry) then filtering on the hyphened version in TreeShare would still provide me with 501 instances for me to plough my way through to find the one instance that it is wrong in Ancestry.


The reason for using standardised places is so that it is easier to do statistical queries in RM and it helps when using a atlas against timelines.


I have not found an instance when Ancestry changes place names back and certainly not without me knowing about it. Obviously if there is a hint then it will use whatever was on the original record. Even then you have to individually tell Ancestry (when online) to overwrite a place name (or any other fact) with the data from the hint. Even for new facts, which have a non-standardised place name, I can cope with that by simply using the above system to bring the fact and sources into RM, clean it in RM and then sync it back to Ancestry.

In Topic: Places and Ancestry TreeShare

09 October 2017 - 02:55 PM

I am not even asking for bulk acceptance, although that would be helpful.


All I want is that if there are any changes or differences on either side then they are shown on the changed list. I am then happy to have to click on each individual to share that change up to Ancestry or mark it as not changed and keep the RM data different to that on Ancestry. Obviously with TreeShare I can edit each side individually ir necessary. So if I make a change to a place name I will then only see the list of individuals who are affected and individually decide to propagate that change up to Ancestry.


As I said currently I either have to scroll through each individual to find those changes (which with a database of nearly 9,000 individuals is very time consuming) or do complicated checks with saved reports to try to find the affected individuals.


Of course it takes time to generate those reports.

In Topic: TreeShare Disconnected For No Apparent Reason

27 September 2017 - 04:42 PM

That happened to me today, i.e. a tree disconnected for no reason. In the end I moved the current database to another location (to ensure that it was not overwritten), I restored yesterday's version (always good to make sure RM does a backup before exiting), then I did a file compare between the restored database and the 'current' database to regain today's work. That is now sync'ing fine with Ancestry again.