One of the other points mentioned in my original post was about phantom updates. These are people who appear in Treeshare as having been changed even though no data relevant to Treeshare has been changed.
I have just processed a batch of updates to RM9 reflecting people that I had added or updated on Ancestry. After that I went through the new people and matched them to FamilySearch. In the process, I discovered one spouse that FS had which I had originally missed; I added Mary Beatrice Link to Ancestry, so that she and her husband (Allen Grierson Knapp) are legitimate changes. All the other ‘changed’ people in this screen print are phantom changes caused by RM9.
As I wrote originally the issue arises when you use the ‘Share data’ screen for someone already matched to FS to match their relatives. These relatives do not appear as phantom matches, but the person whose screen you were using when you did the match does.
I think that this is a bug and should be put on the list to be fixed. Plainly, it is much less serious than a bug which results in corrupt data, so would have a much lower priority.
Even so, it is 100% reproduceable. Update everything in Treeshare, match to FS using the ‘share data screen’ for people already matched and don’t change anything else. Go back into Treeshare. I encourage others to test it.
By the way, I made a separate post here about matching people between RM and FamilySearch. As I am now doing this in a parallel run between RM7 and RM9, I can confirm that the RM9 process is much, much more time consuming than that in RM7. This is the main thing I can think of that would prompt me to stay with RM7 as my main database.
One of the points that would fix this (an optional automatic match when hints found) would solve part of the problem. The other part is that scrolling in the RM9 screen is much too slow and that the screen refreshes (taking ages) each time you match someone. This does not happen in RM7.
This is the same Treeshare screen in RM7.
The same two entries in it are genuine. There are many fewer phantom changes because the auto-matching does not generate them.
Alan
A small PS after originally posting this. Because of fact that many items appear to need amending on RM7 Treeshare’s compare person screen and not on RM9, it was relatively painless to clear the phantom changes above from RM9; most of them showed no changes required and just needed a single click. There were, however, a couple of exceptions like this
These show extra sources in RM which is a little odd as I have done literally nothing in this RM database except create and update it from Treeshare, match it to FS, add some colour coding and a group and process a few not-a-problem entries. In this particular case, the source concerned behaved very strangely in Ancestry and did not originally add to the event concerned (the marriage); I had to add it manually. RM shows it as attached twice. I strongly suspect that Ancestry is at fault here.