I have noticed a minor issue with treeshare. Since I use treeshare a lot, check the results fairly closely and haven’t seen exactly this problem before, I guess that it might be related to the new API or changes made when implementing it. I must confess that I can’t guess how the problem happened.
I have just added a new family to my Ancestry tree. My newly-discovered relative married twice and had children with both wives. I think I created the family properly on Ancestry
I then copied the family to RM using Treeshare and had a look at it there. The final one of these children appeared in both of the new families created on RM
None of the other children appeared in both families and I can’t understand how this could have happened selectively - my recollection is that I added the father and all the children (all with name Leland) before adding either of the wives, but I don’t really see how that could be relevant.
The problem was very easily fixed and appears to be unique (very easy to check with new search on parents >=2 and edited date after new API), so for now it is not a big deal. But it is rather odd.
2 Likes
I think I had a similar issue – father / child and adopted child - my (half) aunt was adopted by my grandfather but my grandmother was bio mother. However, my father and 2 other siblings were blood – however for some reason treeshare skipped him (I am not positive that was the reason or if part of reason). This was with a 32K tree upload earlier this week.
I guess I could do a test smaller tree from those assorted family groups later this weekend and see what happens and let you know
I vaguely recall that when you Add in TreeShare someone to RM, you are prompted to add them as “New Person with x parents” or some such verbiage so it’s likely you just added to wrong parents.
As you say, it’s an easy fix.
Your vague recollection is wrong. There is no such ability to intervene and choose the relationships applying to anyone that you transfer from Ancestry to RM; relationships are taken directly from Ancestry. (I vaguely recall that there is or was a choice along the lines you state when transferring people from FamilySearch to RM, but I have not done this for many years, so my recollection might be wrong or out of date.)
It is possible to end up with relationship errors that need fixing manually, because treeshare only adds and does not amend or delete relationships. So if I had first transferred the child to RM with the wrong mother, corrected the relationships in ancestry and transferred again, then I would have ended up with exactly the position that I got, whereby the final child had two mothers. I would have understood this; it is a known limitation in the functionality which you always have to fix manually. However, I didn’t do any of that; I created the family correctly in Ancestry in the first place and transferred all the family members to RM in one go. Unless there is some un-documented secret handshake, there is nothing that I could have done differently.
I suspect this might be the best way to “fix” if it happens something pass better from ANC to RM that may not (or not correctly) RM to ANC – although in past when I used FTM with ANC I had similar sync problems
