Documenting Parent-Child Relationships

Today, I had another researcher ask about my ‘ChildParent’ events associated with Nancy Jane McCormick. That event is a fact type that I created.

I created this fact type because I was used to using a similar fact type in The Master Genealogist (TMG). In TMG, I used the dau-bio and son-bio tag types. The tag allowed me to connect a parent with a child — and attach source documentation to that relationship.

Since RootsMagic doesn’t have a similar fact type, I’ve been struggling with how to document parent-child relationships. I’d love to hear how other RootsMagic users are documenting parent/child relationships!

Tree Indexing Update

According to what I was previously told by Ancestry support, public member trees were last indexed on October 10th. It has been EIGHT months and my tree still isn’t showing in public member tree searches.

I rechecked my tree (Heartland Genealogy) to make sure it meets the minimum requirements to be included in the indexing of public member trees.

Must be a PUBLIC tree (under tree settings)


Tree must contain Ancestry Sources (Tree Overview)


I then ran my ‘standard’ search for Judson Foster Crawford to verify that my tree still isn’t showing up in the results:


An exact search for Judson Foster Crawford has resulted in 24 trees for the past several months. When I scroll the results list, my Heartland Genealogy tree is NOT listed.

I rechecked the profile for Judson Foster Crawford to verify that there are Ancestry sources attached.


Since I was told that it might not be possible to search for my own tree, I tried doing the same search with my ‘free’ Ancestry account.


I also tried the same search from an Ancestry Library Edition account provided by the Kansas State Historical Society.


After verifying that my tree isn’t showing up in a public member tree search, I called Ancestry support (again). Support diligently asked questions about my problem and duplicated the issue. During the conversation, I was not told the last index date. I was given a case number and they are supposed to email me when the issue is resolved.

For the “rest of the story” see my previous blog post, Ancestry Indexing Update.

The wait begins again!


Ancestry Indexing Update

Well, it is the first of the month and time for my monthly call to about my public tree (Heartland Genealogy) not showing up in searches. Prior to making the call, I used a free account to search for my tree.  I have been using the following search criteria:

  • First Name: Judson
  • Last Name: Crawford
  • Death Year: 1949
  • Match all terms exactly

My search returned 24 trees — none being my tree.

I was very pleased with the Ancestry associate on the other end of the phone. She took time to verify the issue and research the cause. Unfortunately, I didn’t get her name, so I can’t thank her publicly.

Unfortunately, she verified that trees were last indexed on October 3, 2017. She also indicated that it was Ancestry’s practice to index the trees every 3 to 4 months. Hopefully, she was correct in saying that the trees would be indexed in the ‘next few weeks.’

Since I had her on the phone, I also asked about my DNA results. I manage my mother’s DNA test which is attached to my (unindexed) tree. That DNA test has very few ‘hints’. My DNA test has about half of the hints it had prior to connecting the DNA tests to my Heartland Genealogy tree (published in late July 2017). I explained that I could see cousins in my mom’s match list that had public trees that share a common ancestor. However, these cousins aren’t showing up when I click on the DNA leaf (hints). She was able to verify that my unindexed tree was likely the issue.

For the back story on this issue, see the following blogs:


What Are Unsourced Citations on Ancestry?

While investigating an issue with Ancestry hints brought up by Russ Worthington in a comment on the Genea-Musings blog post, “When Did Last Index Ancestry Member Trees?” I discovered ‘Unsourced Citations’ on Ancestry.

These ‘Unsourced Citations’ appeared in a small tree created by uploaded a gedcom file to Ancestry and then using TreeShare to bring the tree down into RootsMagic.

When I looked at the event in RootsMagic, there were sources attached.

The sources are complete.

Upon further investigation, I found that these ‘unsourced citations’ were the Notes attached to an event.

Since my tree was created by uploading a gedcom file, I looked back at the gedcom export screen and found that I had included the Notes in the gedcom export.

Thus, the source of the ‘Unsourced Citations’ are the Notes attached to an individual event.

Why do those notes transfer to Ancestry (via gedcom) as a citation?

Ancestry Hints: Public vs Private

I’m writing in response to Russ Worthington‘s comment on the Genea-Musing’s blog post,

When Did Last Index Ancestry Member Trees? In the comment, Russ brings up the issue of hints not showing. Since I haven’t noticed an issue with ‘missing’ hints on my un-indexed tree, Russ’s post made me question whether I was indeed missing hints. However, I did notice one difference between my tree and Russ’s experiment. I work with a public tree and Russ’ test was with a private tree.

Thus, I wanted to know whether public trees produced hints when the tree lacked Ancestry sources. Thus, I needed a public tree (small) without Ancestry sources. Since I’ve been searching for Judson Crawford to see if my tree was indexed, I decided to create a small public tree on Ancestry for Judson Crawford, his wife, children and parents.

My first attempt at creating the tree was to drag Judson and his family into a new tree. When I tried to use TreeShare with this new tree, I did not get the option to upload the tree. Instead this small tree was connecting to my large tree on Ancestry.

For my second attempt, I created a Gedcom for Judson and his family. I then imported that gedcom into a new RootsMagic file. Again, I couldn’t use TreeShare to upload this tree to Ancestry.

On the third try, I uploaded the previously created Gedcom to Ancestry. I then used TreeShare to download that tree into RootsMagic. [JudsonTrial2]

Lightbulbs started appearing in the RootsMagic tree shortly after the download completed.

On Ancestry, those same individuals with light bulbs in RootsMagic had hints in Ancestry.

Based on this experience, I would conclude that there might be a difference between private and public trees in the way hints are populated. Unfortunately, the public/private tree status was not the only variable in our two experiments. Russ uploaded his data from his software to Ancestry and I downloaded my experimental tree from Ancestry to my software. In addition, I’m using RootsMagic while Russ is using FamilyTree Maker.

Learning to Use RootsMagic Lists

Research Logs / To Do Lists

When I first started my genealogical research, I had some great mentors that encouraged me to keep a log of all of my research — including finding nothing (NIL). I was fairly successful at this when doing paper genealogy. When I started using PAF (Personal Ancestral File), I continued using my paper logs. However, when I switched to TMG (The Master Genealogist), I began to slack off with this aspect of my research. I tried the tools built into The Master Genealogist, but I never incorporated them into my research process. I have citations written according to the standards of the time, but I don’t have a record of unsuccessful searches.

When I switched to RootsMagic, I elected to use OneNote and a spreadsheet for my research log and todo list. Unfortunately, I was having issues with the syncing of OneNote between devices. Thus, I started looking for other solutions — including Evernote and RootsMagic’s built in tools.

Knowing that RM would keep all of the info together, I decided to try using the Research Manager and To-Do List within the program.

My first major use of the Research Manager was during a trip to the Midwest Genealogy Library in Independence Missouri. As I was working my way thru my Excel To-Do for the library, I discovered that I really liked using RM’s Research Log.

  • Prompted to record info to build a citation
  • Prompted to include repository
  • Transcribed information directly into log

By putting all of this information in the research log, I have everything needed to enter an event into RootsMagic, – including the citation information and ‘detail text’. A second advantage, is that the information is stored within RootsMagic for later usage.

Based on my positive experience with the research log, I decided to expand and use the TO DO list. Knowing that we would be making a research trip to the Kansas State Historical Society, I transferred the information from my Excel To-Do list into tasks on RM’s ToDo list. For my research trip, I printed a report showing only those tasks that could be completed at the KSHS. I quickly learned

  • Task headings need to be more specific: event, name(s), date(s), place(s) and possibly a call number
  • Task details matter
  • Transferring the task to the research log did not mark the task as completed

I do like the feature to transfer the task to the research log. This allowed me to easily transcribe the items directly into the Research log.

For both research trips, I used the iScanner app on my phone to take pictures of the source. I tried the free version but ended up purchasing the full app. I like iScanner because it keeps all of the images from one source together. Thus, I can take a picture of the title page and of desired pages and know that they go together. I can export the images as images or as a PDF document. I included a not that I used iScanner to take the pictures in my Research Log entry.

Even though I’m still learning to use these tools, I hope that I can improve my research skills thru their use.



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.