Finally! CRAWFORD hint on We’re Related App

I’ve gotten so that I don’t regularly check the ‘We-re Related‘ app since it usually points to the same few New England lines in my tree. I’m currently, not working on those lines and thus haven’t spent any time to determine whether the hints provided will help.

So when I opened the app yesterday and saw that I may be related to Alec Baldwin, I thought OK, which New England line will it be this time. To may amazement, it was my CRAWFORD line. Having been able to locate sources to prove the next generation on a couple of other We’re Related hints, I was SO HOPING the same would be true  with my CRAWFORD line. Below is the proposed line(s).

img_7370img_7371The image on the right is for my line and the image on the left is for Alec Baldwin’s line.

When I first looked at it, I only looked at my side and was disappointed.

  • unnamed Crawford as the father of my James
  • more James and John’s to sort out

Then, I looked at his line and started comparing the two. That’s when I realized that it was proposing that Janett Thomson had TWO sons named John Crawford — born three years apart. This wasn’t unusual if the first son died. But no, they both live long enough to get married and have offspring.

Since the app doesn’t provide any other information about the line — such as places or spouses names, it is hard to determine if anyone else has a tree that agrees with what the app is proposing. Since Ancestry trees weren’t much help, I turned to Family Search.

On Family Search, I found an Archibald Crawford (KLBT-3N1) that matched the Archibald Crawford in Alec Baldwin’s line. According to Family Search, this Archibald Crawford was the son of John Crawford (LC55-44P) and grandson of Janett Thomson and Robert Crawford (L5B1-L8Y). That’s where it gets messy! The family of Robert and Janett shows 10 children with 3 of them being named John, 2 named William and 2 named Robert. (See any issues here?)

So what about my side? Family Search shows a son of Robert & Janett named John who died in 1736. However, FS shows this John Crawford  (LHZG-Y9W) being born in 1701. Based on the number of wives associated with John Crawford (LHZG-Y9W), it is likely that more than one John Crawford is involved. Thus, not much help. (:

Going back to Robert Crawford (L5B1-L8Y), FS also shows him married to Mary Shaw (L5B1-P2Z). According to FS, this couple had 4 children: James, Robert, Col. William and Col. John  (L8WG-7DQ). Although I haven’t found the documentation to support it, other researchers have connected several Crawford families from Lincoln and Madison Counties, Kentucky prior to 1790 to Col. John Crawford (L8WG-7DQ) and believe he is the son of Robert and Mary (Shaw) Crawford.

At this point, I have not found anything to support or disprove the Crawford ancestors proposed by the We’re Related app. For now, my line is a dead-end with James Crawford in the 1790s in Kentucky.

Preparing for Ancestry Sync

TMG –> RootsMagic Cleanup

Randy Seaver recently discussed the upcoming ability of RootsMagic to sync with Ancestry and what he is and isn’t doing to prepare for that in his blog post, “Dear Randy: What are you doing to prepare for the RootsMagic program sync with your Ancestry family tree?” While reading Randy’s blog, I realized that I was in the middle of such a preparation with my work on my census facts.

My genealogy data was migrated from The Master Genealogist version 9 to RootsMagic. When I selected The Master Genealogist (around version 4 or earlier), it was because I wanted something that allowed me to add citations for each event. Thru the TMG community, I developed my research and documentation skills. I also applied several TMG ‘hacks’ — especially if they helped visualize the events in someone’s life.

tmgcensusOne of those ‘hacks’ was a modification to the census tag developed by Terry Reigel. It took me some time to implement this hack, but once completed, it allowed me to see the family in the timeline for the head of the household.

Since RootsMagic would not handle the ‘split sentences’ in the census-head or census-enum tags, I did have to modify the sentences. I was able to do this in TMG prior to the migration. Because, I liked how the census tags worked, I did not modify them in TMG but let them migrate into RootsMagic as custom event (fact) types.

As I began to learn to use RootsMagic with Family Search, I realized that my custom fact types were not lining up with the corresponding fact type on Family Search. Since the tree on Family Search is a community tree, I’m very hesitant about making changes – but also want to see more documentation for my ancestors. Thus, the conflict — my custom fact types would ‘foul up’ the Family Search tree but the census records have not been sourced. Because of that conflict, I decided to figure out how to revert my custom fact types (census-head and census-enum) to the standard type.

Knowing that there wasn’t an easy way to do this from within RootsMagic I turned to the SQLite Tools for RootsMagic community. There, I found directions on how to setup SQLiteSpy so that it would read and modify the tables in the RootsMagic database. Once I had this software downloaded and correctly configured, I used the SQL script, Facts – Change Fact Type to change all of my census-head and census-enum fact types to the standard census fact type. Since this SQL script directly modifies the database, I copied the database and worked with the copy FIRST. That allowed me to make sure the script was doing what I wanted without the danger of corrupting my data. Once I knew it was working, I backed up the data and then ran the script on the original copy of the data.

After running the script, the census citations in my RootsMagic database lined up with any census citations on Family  Search. Step one accomplished!

Besides changing the custom fact type to the standard, I had two other potential issueds with my census facts. The first involved the sentences. It appears that what was in the memo field in TMG was dumped into the note field in RootsMagic while the sentences pull the information from the description field. Thus, all of the information I had entered about the individual wasn’t being pulled for the sentence. Since almost all of my census facts had witnesses associated with each fact, individual reports and web output was showing extra sentences/facts for other members of the household.

So, my next step was to move the info in the note field to the description field while also removing any witnesses. Since I couldn’t get the SQL scripts for this process to work (they do exist), I resorted to doing this one person at a time. With over 10,000 census entries this is no small task. I started with my ancestors who were living in 1850 and worked thru their descendants. However, I’ve been researching several neighbors and other potentially connected families and their descendants. Thus, I needed some sort of report that would help me know who was left to do.

The SQLite Tools for RootsMagic came thru again! On their site, I found a link to the “People who share a fact with a principal list” script. This particular script just creates a list, it doesn’t modify the database. However, the script must be run with the RootsMagic database closed. I have the script saved in my SQL directory. Each time I want to run it, I open the script with Notepad and then copy and paste it into SQLiteSpy. Once executed, the script will create a list. I copy the info in that list and paste it into a blank Excel spreadsheet. That way, I can close SQLiteSpy and open RootsMagic and still have a list to work with.

Once the data is in Excel, I do a multilevel sort: Fact, Surname1, Given1, RIN1. This allows me to easily delete everything but the census records. Armed with that list, I just work my way thru the records. I’m down to about 1300 census events.

Will this be worth it? Because this is cleaning up my data and making it easier to see corresponding census records on Family Search, I will continue until finished. I’m also hoping that by using the standard ‘census’ fact type, this data will also line up with Ancestry. My wish is that all of my census data will keep me from having shaky leaves for those same census records.



Hints Discovery

Thanks to Randy Seaver and his blog about using the links from Family Search to access hints from Ancestry and other genealogy sites, I retried the links. I did discover that (for me at least), I have to use Chrome for those links to work.

grandad1The Ancestry link gave me 111,849 hints — and the first 50 appear to actually be for my grandfather!

grandad2In that list of 50 were a couple of links to high school yearbooks. Following the first of those links, I discovered a list of ‘Athenian’ members that included my grandfather’s name.



Since I have no idea what the ‘Athenian’ group is, I started browsing the yearbook from the start to make sure I was looking at a yearbook from Dodge City and to see if I could find my grandfather elsewhere in the publication. That’s when I found the unlabeled picture of the freshman class that includes my grandfather. (The next page of the yearbook lists the members of the class.)


I could see my grandfather in this picture before finding the list of class members on the next page. I see a lot of my nephew in the way my grandfather is standing. I wonder if other family members will be able to pick him out!