Bear with me this will take some explaining. I have two trees on Ancestry that match two trees I have in Roots Magic. The current tree is a spin-off of the 2nd tree on both platforms. I work on Tree A both places. Tree B does not get updated - at least it’s not supposed to. However, I appear to have had a brain fog and instead of working on Tree A, I worked on Tree B for about a week, adding people, deleting people, sources, etc. This affects about 50 people. The new people in Tree A are not in Tree B, on Ancestry or in Tree A or B on Roots Magic. Tree B is not connected to Roots Magic but Tree A is. So - how do I get the new people I erroneously added to Tree B into Tree A on Roots Magic and/or Ancestry. If I can get them into Tree B on Roots Magic, I can slide them over to Tree A and then TreeShare with Ancestry to get them into Tree A on Ancestry. I cannot believe I did this. HELP!!! Thanks for your consideration -Martha
Ouch! I assume that you have not treeshared the new people from Ancestry to RM at all? If not and you know who the new people are perhaps you should disconnect both trees from Ancestry in RM and then connect your working tree in RM to ‘tree A’ in Ancestry, then treeshare and download the records you want from Ancestry. Then disconnect the tree and connect it back to the correct tree in Ancestry. I’d avoid connecting the trees you do not update again, unless you need to alter things at a later stage.
you may want to pause and carefully determine best course of action.
Restore is one option- that means you would have to redo any work since
Drag N drop to add new people to opposite side. (opening both A & B and dragging New B people to A, You might end up with some duplicate info unless they are all truly new. Some may need to be merged if they are not seen as matching.
You can drag and drop the new or newly changed people from RM database B to RM database A. Then TreeShare RM database A with Ancestry tree A so that they match. That’s the basic concept.
I would make a group of new or newly changed people in database B in RM, with the group criteria being based on the Date Last Edited Field. Then use the group for your drag and drop.
There probably still will be additional cleanup in database A, including possible merges of duplicate people. The hardest part is going to be doing any of the deletes of people or facts in database A to match any deletes you did in database B.
Thank you, Charlie. I’m not sure who the “new” people are. I didn’t know I could disconnect and then reconnect a tree from Ancestry. I have not tree-shared or done anything yet. I don’t want to mess things up further. Thanks for the suggestion!
I hadn’t thought about making a group in B of the new people. The deletes are going to be a problem, because I know there are some. Right now I have ProTools active in Ancestry and I have discovered that it will tell me what changes were made to B, but it doesn’t tell me specifically who or what was deleted (people or sources). I’m going to have to figure that out myself. And, it doesn’t distinguish between the two trees. So maybe I deleted something from Tree B or maybe it was Tree A??? I’m thinking creating the Group will get me mostly what I need. Thanks Jerry! I’ll let everyone know how I fared getting it back together. Geesh - I need to pay more attention to what I’m doing.
Thanks Bob. I figured that out. Tree A is the only one connected to Ancestry, and I haven’t disconnected it. BTW - I note the Purple Heart. Thank you for your service!
You can Reconnect any RM to Ancestry by doing a Restore from a database the was connected prior. Of course if you have deleted it from Ancestry, I don’t think it will work.
My TreeShare connection from RM Tree A to Ancestry Tree A is the thing of nightmares. I get people on one side without a link or person on the other; I get people that look like there’s a link on both sides but there is only one side when I click on it. I cannot seem to break a link between two unrelated people. And I’m wondering if I do a backup of my RM A tree, and then disconnect from Ancestry, and then restore the backup, if all the gremlins in the prior connection will be gone. I couldn’t work on anything last night because the power went out and it’s the coldest night so far this winter. -4 degrees 8 inches of snow and I had to switch to tanks for my oxygen. Been working on it this morning, tho. So here’s what I did:
Downloaded tree B from Ancestry to new RM Tree. Because it was a new tree, the Group search for recently edited people did not work - it returned everyone in the database.
I did a compare between new Ancestry Tree B and old Ancestry Tree B to see how many new people there were. Then I checked the tree on Ancestry to see the changes there and there was a span of only 5 days (90 people) where I was working on the wrong tree. Not bad, but still. . .
I added the new people from the compare of the two B trees to the Ancestry A tree using the Ancestry change log as an aid. Then the power went out.
This a.m. I finished cleaning things up. I have not yet restored anything to the RM A tree; I plan to do that by TreeShare if I can get the gremlins out of it. I DO NOT want to re-download my Ancestry A tree to RM because it makes a mess of the sources. And it took forever to straighten those out the first time. So if anyone can enlighten me on the TreeShare thing, or do I just suck it up and manually update my RM Tree A and forget about using TreeShare again.