How to Create New Ancestry Tree from RM Database

[kevinm]

@billbremer

a Reset …will not automatically upload missing people or fix broken or missing links on the Ancestry side. Correct?

Exactly right.

@billbremer

After a disconnect and a reload of a previously “synced” database to a new Ancestry tree, Ancestry will (understandably) start all over pushing hints for the new tree. This would also be true for the new “private” tree you suggested in you post, correct?

Correct.

The reason I suggested making the test tree private would be to avoid giving others duplicate hints until you have a tree that has all of the desired people in it. There are many reasons why an initial treeshare of a full rm db might not complete (often it’s server load issues on the ancestry side) and the problem you describe increases the potential for the new tree to also have problems – perhaps more than your existing tree.) So, the idea was to keep all of your existing stuff in place and operational until you’re satisfied that the new tree is what you want.

@billbremer

Is there evidence that people who are “participants” in shared facts will not upload properly to Ancestry?

Not that I am aware of. The shared fact only transfers for the person that the event was added to (sharer vs sharee) but a shared fact should not impact whether or not the person gets uploaded, From what I have seen reported the core issue with whatever changed in the API is not straight forward or intuitive. Here’s a link to another thread from August.. The thread is long but it describes a few scenarios people were experiencing. There are others. This issue is significant enough that it will be called out when the fix is available.

@billbremer

Is there a list of RM specific features or issues that should be cleaned up before pushing a DB to Ancestry? Any items on this list that would silently (no error message) block the person being uploaded?

Great question. There’s nothing that should block a person in your DB from being uploaded via Treeshare. There have been requests for such a block (for privacy reasons) but none exists yet. There are settings to block Facts and/or Notes marked private from an initial upload but that won’t affect the uploading of the person record.

The question of features to cleanup before uploading is a good one. I am sure that folks can weigh in with good suggestions from the perspective of data quality. This post is already quite long and others are better qualified to comment. To reiterate, no features should silently block a person from being uploaded via treeshare.

One last thought is that you might consider seeing if the problem is repeatable.. ie do the same people fail every time? if so, opening a support ticket would be a good idea. It may help development isolate the core issue(s). Even if it’s not repeatable to the specific people that fail but it never completes 100%, it could still be helpfull to open a ticket.