UPDATE - Tree Not Searchable (Ancestry / RootsMagic)

The verdict is in! 

 I need to accept hints on Ancestry in order for my tree to become searchable.

Ironically, my DNA 'shared matches' list was working even though I was accepting the hints on RootsMagic and not on Ancestry!

Not only do I have shared Ancestry hints and circles but the list of hints and circles has been growing.

Thus, I didn't think there was an issue with the way I was using RootsMagic!



Now, that I'm aware of the issue, I'm going to change my workflow.

• Accept valid hint on Ancestry
• Use RootsMagic to source that hint and manually add the image (as I was doing prior to TreeShare)
• Ignore pink sources and media on TreeShare

 In the meantime, I'm going back thru my 5 generation pedigree and

• Clicking confirmed sources and changing them to undecided within RootsMagic
• Accepting those sources on Ancestry

 Now, I wait for Ancestry indexing to pick up my tree.

I would like to thank the RootsMagic community (both Facebook and RootsMagic Forums) for helping me work thru this issue.

Ancestry / RootsMagic - Tree not Searchable

I work from RootsMagic.
I click on the lightbulb and accept the hints.
I write the citations within RootsMagic.
I then use TreeShare to upload my changes to Ancestry.

All of my citations transfer to citations -- but -- are listed in the 'other citations' area. Even though they are based on those accepted hints, they are not listed as Ancestry citations. Below is a link to Judson Foster Crawford on my tree:

https://www.ancestry.com/family-tree/person/tree/115166653/person/270137689801/facts

My tree (Crawford-Briles) has lots of sources attached.

Ancestry views my tree as having NO sources. Thus, it doesn't show in a search. [Try searching for Judson Foster Crawford died 1949 and look for the Crawford-Briles tree.]

Yes, this and the member connect issue are Ancestry issues.

BUT -- they wouldn't be occurring IF I didn't use the lightbulb to accept the hints.

Yes, I could avoid this issue by accepting the hints on the Ancestry side -- BUT

• I lose control of the citation format
• I lose control of where the media is stored
• I lose control of how the media is named

Right now, I don't like my choices:

• Continue my workflow realizing that my tree won't be searchable
• Switch to accepting hints on Ancestry and lose control over citations and images
• Quit using TreeShare so that I can have a searchable tree and control where the downloaded images go

I don't like any of those choices and am hoping that RootsMagic will work with Ancestry to resolve this.

Land on Sugar Creek / Mary Crawford

Mary Crawford purchased land from Richard Cave in 1791. Below is a transcription of that deed.

Crawford Research: Which James Is Which?

My ancestor, James Crawford, died in Preble County, Ohio in 1854. In 1821, he sold a piece of land to Wm Sellers. This Preble County Deed (Book 5, page 87), identifies the seller as James Crawford Junr and indicates that James was from Preble County, Ohio. The deed is signed by James Crawford and Sally Crawford. Sally's signature is significant since it identifies my James Crawford and not another James Crawford living in Preble County at the time.

DNA and NodeXL

The Facebook group, Genetic Genealogy Tips and Techniques, has provided lots of opportunities to learn how to use my DNA results to support my research -- and to break thru brick walls. Recently, Shelley Crawford has been posting links to her blog posts detailing how to use NodeXL and Microsoft Excel to find DNA connections. Yesterday, I followed the steps in her post, Visualizing Ancestry DNA Part 2 - Loading the Files. With my first attempt, I downloaded all of my matches and worked my way thru the instructions to get a 'blob'. I went back and rechecked my 'alternate' file to make sure I was skipping my siblings, my mother and 1st cousins (once removed). It took a while for the graph to appear but it was still a blob.

So, I started over and downloaded my matches for 4th cousins or closer. After creating a new file and again making sure the 'skip' information was included, I still had a blob -- just less dense.

Knowing this wasn't what it was supposed to look like, I dug thru her posts and the comments to discover that this whole process is more difficult with lots of data. One suggestion was to change the way the data was grouped. So I decided to try 'grouping by cluster'. That seemed to help since it separated the 'blobs'.

Even though it was still hard to visualize a DNA circle with the above graph, it was possible to click on a dot and see how that one dot was related to other dots (red lines). After some playing around, I figured out that the dark blue dots in the upper left contained a lot of my BRILES matches. So I'm wondering whether I can isolate certain branches of my tree by 'skipping' known matches from other branches of my tree.

Experiment #1: Isolating CRAWFORD line

• Sort Vertices by shared CM from largest to smallest
• Using data in 'notes', enter 'skip' in visibility field for known matches to other lines thru 150 matches
• Save file different name
• Refresh graph

 Group by Cluster

Unfortunately, that didn't clear out enough data to make it easy to see the 'circles'.

Since my experimentation (playing around) didn't produce a graph anything close to the example, I'm going to give up for now and wait for the next blog post of suggestions.

Citation Length - Using TreeShare to Modify

I'm experimenting again!

Can I use RootsMagic to modify an overly long citation and then use TreeShare to get that citation uploaded to Ancestry.

The first task is to locate the 'offending' citation in my list of sources. Since I know that this citation is associated with several facts for William Taylor Thompson, I'm going to use his screen to locate more info about the citation. When I look at the birth sources, I find the 'offending' citation.

From the info on this screen, I know the citation is listed under 'History-IA Wapello Portrait ...' in my list of sources. Since I only want to change the citation one time, I'm hoping that I will be able to use the Master Source List to make the change. After opening the Master Source List (Lists menu), I scroll to locate 'History-IA Wapello Portrait ...' in the list.

Having found the source, I click on the Edit button to make changes. I'm going to shorten the citation by removing the subtitle, 'Together with Portraits and Biographies of All of he Governors of Iowa and the Presidents of the United States.'

After shortening the title, I have a much shorter citation (but I haven't counted characters).

After clicking OK to accept the change and closing the window, I then opened William Thompson's window to see if the change carried over to his citations -- which it did!

Unfortunately, when I go to TreeShare, the program doesn't recognize the change in the citation since I didn't make the change on an individual's record.

 Nor does TreeShare recognize the difference in the sources when I go to William Thompson.

On Ancestry, I locate William Thompson's profile page.

I deleted the offending citations. His family now appears on the screen.

I re-open TreeShare hoping that the changes in Ancestry will produce prompts to upload the citation. William Thompson now shows on my list of changed people and the affected source citations are pink.

I select the first event and chose the UPDATE option.

I place a check mark in the box next to Sources and click OK

I repeat the process for the other 'pink' citations and then click Accept Changes. This should push those modified sources up to Ancestry -- and if I shortened the citation enough -- the screen should continue to display the family.

It Worked! The shorter citation is there and the family is still showing on the screen!

The next challenge is to figure out who all the citation is attached to and get the revised citation uploaded for them. Another option would be to keep track of citations that have been edited and then when the weird screen is encountered, use the list to determine which citation needs deleted and re-uploaded.

New Tree DNA Issues

On Wednesday (June 28), I uploaded my RootsMagic data to Ancestry, thus creating a new tree. Since I want to be able to utilize the TreeShare features of Ancestry, I want this new tree to be my primary tree in Ancestry. Thus, I attached my DNA results to this new tree.

I knew that when I switched my DNA to this new tree, it was going to cause some 'hiccups' in my DNA screens AND that it might take several days (weeks) for those 'hiccups' to go away.

However, I am seeing some strange, unexpected behavior that I'm trying to figure out the cause.

The first strange behavior is with the 'Shared Ancestor Hints'. I expected them to drop to zero and had documented those matches. Even though I can understand the few I have back, I can't figure out why I got those and not others.

The 5 shared Ancestor Hints are from my Briles (Broyles) / Rush line. I have circles for a couple of men on my Briles line and for my Rush line. However, these 5 people are not on the list of matches for the circles.

In trying to figure out why those I expect to appear aren't showing up, I discovered another strange behavior. I looked at my DNA match with my dad's first cousin. Since she has a tree and since I have accepted Ancestry hints for our common ancestor, she is one of the first people I expected to reappear on my list of shared matches. We also are grouped together in quite a few of my circles.

As indicated in the note, Judson Crawford is one of our common ancestors. Her DNA match screen shows that she has Judson Crawford in her tree.

My tree also contains Judson Crawford.

When I click on Judson F Crawford in my tree, a window opens showing his full name and birth/death information.

If I go back to her DNA match screen and look at her Crawfords, she has the same birth and death years for Judson Crawford that I have.

So, my question: Why is it only showing shared surnames and not a screen comparing our trees back to the common ancestor?

I plan to call Ancestry on this, but am wondering if anyone else with DNA attached to a new tree is having similar issues.