My 1950 U.S. Census Release To-Do List: "Who Was There" List

With my eye on the public release of the 1950 U.S. Census in less than a year, I'm preparing to look for ancestors I'm particularly interested in.

No indexing will be available on April 1, 2022, so the only way to find these ancestors at first will be to browse enumeration districts where they were living. The catch is, I need some idea of where each ancestor was residing in 1950. 

Generating a RootsMagic "Who Was There" List

As an experiment, I opened my RootsMagic7 genealogy software and looked for a report that might give me a head start in grouping ancestors who were (1) alive in 1950 and (2) living in a certain area.

At top is a screen shot showing me preparing to generate a list of "Who Was There" in Ohio in 1950. I set the parameters for everyone in that particular tree (my husband's Wood family). 

I could have narrowed the parameters to everyone in Cleveland, Ohio, for instance. 

In this case, the list for Ohio ran for a dozen pages. It was initially organized alphabetically by surname, showed birth and death dates, and showed in detail each person's residence and key facts. A bit too much detail, but I expect to learn how to refine the list as I gain experience.

Next, Save and Sort the List

Importantly, I was able to save this list in my choice of formats. I selected .rtf so I can open it in Word and then sort as I please, choosing to sort by any of the columns. 

Here is an excerpt of the Wood list for 1950, sorted by "place" (the final column). This gives me a starting point for seeing where each ancestor was in 1940 and then researching a more specific residential location to search in the 1950 Census. Only a starting point, because I'm also looking for more recent directories and other sources to bring me closer to the 1950 address.

About the column marked "age"--it indicates the ancestor's age in 1950, not the ancestor's age at death.

This experiment encourages me to explore more ways to use the software and learn more of its functions on the road to the 1950 Census release next year.

--

For more posts about prepping, please see my special page on the 1950 Census.

Where the Bodies Are Buried, Part 3

I don't want future generations to forget where our ancestors are buried. In Part 1 of this series, I found out how extremely fast and easy it is to create a virtual cemetery on Find a Grave. I've now created 3 virtual cemeteries and still keep clicking to add ancestors to each one. This is also an incentive for me to be sure more of my ancestors are represented on Find a Grave.

In Part 2, I highlighted a printed workbook for documenting death and burial details for ancestors. Also, I experimented with an illustrated pedigree-style listing of final resting places--not a big success, but a learning experience. 

Now I've created one of my favorite tools for recording genealogical details: A Word document with details typed into a table, sortable by column.

Sort by surname, sort by cemetery

Shown above is an excerpt from my document "Wood Family Burial Places." I entered information in three columns, thinking ahead to how I might want to view the details for various reasons.

Each ancestor is entered: SURNAME, GIVEN & MIDDLE NAMES. That allows me to digitally sort the table according to surname--handy for when I'm only interested in the Wood line, not the Slatter line (in-laws) and so on.

I also listed cemeteries with complete address info. Some day, I or another descendant might want to visit. This makes it quick and easy to sort by name of cemetery. VARIATION: I could have listed a separate column for city/state. In this case, I didn't--but I will for my next iteration. Then I can sort by city/state, and within city/state, by cemetery, if I'm planning a visit.

My preference: Find a Grave

After reviewing all my options, and testing a number of different methods, I am happiest with my virtual cemeteries on Find a Grave. In fact, while creating my Word document, I consulted Find a Grave for details. Ideally, Find a Grave would someday allow me to download my virtual cemetery in a spreadsheet or pdf format. Wouldn't that be even easier?

So I'm going to add to my virtual cemeteries on Find a Grave AND then transfer each family's cemetery (one name at a time) to a Word document that can be sorted and printed for distribution to relatives. I'll also put a copy into my files for future descendants to see.

NOTE: RootsMagic7 is the genealogy software I use, but I'm not as proficient as I'd like. It would have allowed me to print a custom report if I had entered burial places for the people in my family tree. I didn't do that from the start, which means any report I create now would be incomplete. That's why I'm investigating these other methods of recording and distributing burial information so my family will not forget where the bodies are buried.

Fact List Reveals Gaps in My Genealogy Research

This week's "Saturday Night Genealogy Fun" challenge from Randy Seaver is to create a fact list using genealogy software and share the results.

Since I use the same software that Randy uses -- RootsMagic7 -- I simply followed his instructions. I prepared a fact list of marriage facts in my Wood family tree. Above is an excerpt from this 38-page report. (I didn't print it--to save trees, I saved it in digital format.)

As I'm still learning to use my RM7 after 3 years, Randy's challenge was an opportunity to identify gaps in my research. Above, I have no marriage date for one ancestor but I do have a place. For another ancestor, I have a year but no marriage place. And for two ancestors, I have only a city or county name without the state.

I ran this fact list for marriages...now I'll run one for births and one for deaths. Those are the very bare basics, but I can drill down further when I'm ready. Thanks to Randy, I'm be able to see at a glance where I need to focus my research to fill in the gaps!

Which of Hubby's Ancestors Were in the Civil War? Part 1

The 1910 US Census asked about veteran status.
UA = Union Army service during the Civil War.

Thank you, Ken Burns, for getting the younger generation interested in ancestors who fought in the U.S. Civil War!

A young relative just mentioned watching the popular Ken Burns documentary series The Civil War for the first time.

Me: "Hey, I'm writing a family history booklet about your Civil War ancestors."

Young relative: "Wow, we had ancestors in the Civil War?"

Me: "More than one! Wait till you hear their stories." [Doing the genealogy happy dance--a descendant asking about ancestor stories!]

First Step: Who Was Old Enough to Serve?

From previous research, I'd already identified 10 ancestors of my husband who served in the Union Army. That was just a start.

Now I needed to go through his family tree in a systematic way to see who else might have served in the Civil War. Given the migration patterns in my husband's family (including Ohio Fever that attracted Northeastern ancestors to settle the Ohio River area), I expected to find NO service for the Confederacy, only for the Union side.

My first step was to use RootsMagic7 to sort the family tree by birthdate. I printed the report and used a red pen to mark men eligible for the draft or enlistment. As a rough guide, I was going to investigate those born between the mid-1820s and the late 1840s.

The initial list included 71 men of eligible age for military service.

Second Step: Ancestral Relationship and Location

After deleting a few male ancestors who died just before the Civil War, I examined ancestral relationships and locations. My goal was to eliminate men who had an indirect connection to the family tree and men who lived in another country during the Civil War years.

Name by name, I dropped ancestors such as "father-in-law of niece of 1c2r" as well as ancestors who arrived in America after 1865.

This shortened the list to 33 male cousins and great-great-uncles of eligible age who were living in the United States from 1860 to 1865.

Third Step: The 1910 US Census Clue

Before doing serious Civil War research, I took a quick shortcut to see, as a clue in the 1910 US Census, which of the men on the list had indicated they were veterans.

This clue only works if the male ancestor was still alive in 1910 (he served as late as 1865, so he would not be a spring chicken). And of course it only works if the man or his relative knew enough to tell the enumerator about his military service. Remember, this is a CLUE, still to be verified by further research.

See the snippet at top? The 3d column from the far right on the 1910 Census was a question about whether the person was a veteran.

For Union Army veterans, like my husband's ancestor in this example, the enumerator would write "UA." The National Archives posted this list of veterans' codes for 1910:

• "UN" for Union Navy
• "UA" for Union Army
• "CA" for Confederate Army
• "CN" for Confederate Navy

In Part 2, I'll describe my next steps in determining which of my husband's ancestors were in the Civil War, where, and when.

June 1 = Backup Day

Old backup technology

Today is backup day.

After a computer glitch deleted hundreds of my photos a few years ago, I restored most of them by rummaging in my old backup CDs. Old-fashioned by 2020 standards, but they worked exactly as they were intended!

These days, I safeguard my 22 years of genealogy research with automated backups and backups of my backups.

Plus, on the first of every month, another backup ritual.

Automated:  My Mac's Time Machine backs up every day to a dedicated external hard drive. In addition, I have a BackBlaze account that backs up files and photos and letters (not applications) to the cloud on a daily basis.

Not automated: Every time I open my RootsMagic 7 genealogy software, I first sync with my multiple Ancestry trees. Then I backup these trees to my external hard drive before I close the software.

On the first day of every month, I manually download my Ancestry trees as Gedcoms and back them up on my Mac and in the cloud.

Plus I have a separate external hard drive backup just for photos, scanned images, and other genealogy data.

When I prepare a family history booklet or scan an album or some old letters, I put copies (works in progress and finished products) on this drive.

How do you backup your #FamilyHistory?

Backup Is Cheap, Family Trees Are Priceless

Ancestry's instructions for downloading a family tree

One big reason I use RootsMagic7 genealogy software is to be able to sync with the family trees I've created on Ancestry.

Although I back up my RootsMagic trees every month or whenever I make major changes, I also like to download my Ancestry trees periodically.

It's easy to download a tree as a gedcom, as you can see from the above Ancestry screen shot. I give each downloaded tree a distinctive name AND date, so I can distinguish the "Wood" family tree download of February, 2020 from the "Farkas" family tree download of December, 2019.**

Keeping my family history safe is a top priority. Multiple backup processes (both RootsMagic and Ancestry trees backed up, stored on two hard drives, and stored daily in the cloud) may seem like a lot of duplication, but it offers me more options for restoring my trees, if ever the need arises.

Backup drives and cloud storage are relatively cheap -- carefully researched and documented family trees are priceless and deserve protection.

**RootsMagic will also download an Ancestry tree for me, including all media attached to the individuals--very convenient! I do this as well, but also like to keep a separate gedcom downloaded directly from Ancestry in case I need to recover.

DNA Plus Trees Equals Cousin Bait

MyHeritage profile is temporarily empty, soon to be filled!

This week's #52Ancestors prompt is DNA. For years, my main genealogy site has been Ancestry, in part because of the size of its DNA base and because my multiple, ever-growing family trees are all housed there. Thousands of ancestors, counting his and her trees, some with thousands of hints to be examined.

My DNA and hubby's DNA also appear on Gedmatch, because of the tools available for analysis and because we can fish for matches among all people using that site, regardless of where they originally tested.

I created a basic tree for him and for me on Gedmatch, and also listed major surnames so people browsing matches can quickly see how we might match, as cousin bait.

New Site for DNA Cousin Bait

Now I admit, I'm often frustrated by how many Ancestry DNA matches have no family tree, or only a few names, or a private tree only.

So now that I just subscribed to MyHeritage, to more intensively research my husband's British, Irish, and Scottish ancestry, I'm transferring my DNA and hubby's DNA there too.

With the new site, I need to complete my profile (sadly empty, as shown above) and plant my family trees as cousin bait. I began with a photo and basics...

More Hints Too

Since I sync my Ancestry trees with my RootsMagic 7 software, I will be able to upload an updated Gedcom tree for myself and my hubby onto MyHeritage with little effort. Thanks to the RootsMagic Users group on Facebook, I learned how to export a Gedcom with living people marked as private.

Now I can take advantage of both Ancestry and MyHeritage hints through RootsMagic, as shown here.

Make it easy for DNA matches to see the family tree(s), and we just might get better answers to our notes or possibly hear from matches who take the initiative to reach out to us! Cousin bait.

Why I Use Genealogy Software (It's Not Why You Think)

RootsMagic is my genealogy software of choice for one big reason: It syncs with Ancestry, my research/tree site of choice.

But unlike most researchers, I don't do my work in the software and then upload to Ancestry.

On the contrary, I prefer to work in Ancestry (including research and uploading photos/documents) and then download to my computer, via my sync with RootsMagic.

My Technology May Not Be Their Technology

Why? My mind is constantly thinking way ahead to what happens when I someday join my ancestors.

On that faraway day, even though my Mac computer will remain on my desk, it may as well be a pile of bricks as far as my genealogy heir(s) are concerned.

I'll bet none of the next generation will be bothered to open my genealogy software, let alone learn how it works. They'll have their own technology preferences, and any specialized genealogy software on my desktop Mac is unlikely to appeal to the mobile-first younger generation. Just ask your younger relatives and see if they agree.

With this in mind, I don't think of my genealogy software as the primary place to keep my tree and media. In a sense, my computer-based software acts like a backup to my Ancestry tree.

A Family Tree Grows Online

I believe descendants and relatives (and cousins I don't yet know about) are far more likely to find my public family tree on Ancestry, if they have any interest at all.

As I wrote in my book, Planning a Future for Your Family's Past, online trees should be noted in any genealogical "will." For my part, I'm leaving my genealogical heirs a bit of money for an Ancestry subscription so they can noodle around and see how the tree works. They can use mobile or desktop devices, whatever suits their fancy.

Of course, I sync with RootsMagic very frequently so I always have the latest version of my tree on my computer, including all media. This is because I work on the Ancestry tree (multiple trees, actually) every week, sometimes every day. New documents become available, or new photos surface in the family--those are good reasons to add to my online tree and share with those who have been invited to see it. Also, I like to look at DNA hints and compare those trees with mine on Ancestry. It's just convenient to have the latest tree online.

Way in the future, my heirs can decide if they want their own genealogy software. If not, they and I can rest easy, knowing the tree and documentation are on Ancestry for the family to see at any time.

More Winter Weddings in the Wood Family Tree

My husband's Wood family tree has lots of December marriages. Here are three more of the many that popped up when I used RootsMagic's calendar report.

• December 18: Mary Shehen and John Slatter. Mary (1837-1889) was my hubby's great-grandma, and the saddest figure in his family tree. Born into terrible poverty in London, she married great-grandpa John Slatter (1838-1901) 159 years ago, and had 6 children with him. As the years went on, she and the children were in and out of workhouses, seemingly abandoned. Eventually, Mary was admitted to an insane asylum due to depression. She died there 15 years later, of TB. John, meanwhile, left for Cleveland, Ohio and a new life, with a new wife and a new occupation. He died at his youngest daughter's home in Cleveland, having been widowed again and chronically ill. I'm still trying to get back a generation and learn more about Mary's parents, who were themselves born in Ireland around 1801.  
• December 19: William Smith and Janet "Jean" UNK. Born in Ireland, Smith (1724-1786) and his wife Janet (?-1805) were hubby's 5th great-grandparents. Alas, I know very little about either of them, although it appears they were married in 1751, which is 267 years ago. A Smith researcher whose work I respect indicates that two of William and Janet's sons were doctors. Not sure I'll be able to learn more about these long-ago ancestors, given the "Smith" name and the dates/places.
• December 24: Francis "Frank" Ellery Wood and Louisa Mary Schultz. Frank (1857-1933) and his bride Louisa (1860-1948) were married on Christmas Eve, 1883, in Toledo, Ohio, where Frank and most of his brothers were working as carpenters. Frank was my husband's great uncle. The snippet at top from the Lucas county ledger shows their marriage a mere 135 years ago, when he was 26 and she was 23. Frank died after an operation in 1933...then 17 months later, his widow Louisa married his younger brother, Marion Elton Wood. (Unfortunately, Marion had lost two wives by then, as well as one of his two children.) Louisa was again widowed in December, 1947; she lived just 5 months longer.

Winter Weddings in the Wood Family

The list of December weddings in my husband's Wood family tree is quite long. Here are just a few of the marriages in the calendar report generated by my RootsMagic software. Marriages from later in December will be shown in another post soon!

• December 5: William Steiner and Catherine Evans Coder. Steiner (1827-1899) was my husband's 2d great uncle, born on the eve of Christmas Eve and married just weeks before his 22nd birthday. He was one of 6 boys and 3 girls, and worked as a plasterer in Tod, Crawford county, Ohio. The Steiner-Coder wedding took place 168 years ago today. In June of 1863, William registered for the Civil War Draft (see excerpt from ledger above) but did not serve, so far as I can determine.
• December 11: Edson Larimer Everitt and Maggie Derr. Everitt (1862-1927) was hubby's 2d cousin, 3x removed. He was a farmer and married in Hocking, Ohio, at age 40, 116 years ago. His middle name, Larimer, comes from his great-grandfather, Isaac M. Larimer, a son of the original Larimer immigrant ancestor who was shipwrecked after leaving Northern Ireland.
• December 18: Isaac Larimer Everitt and Ellen Smith. Isaac Everitt (1827-1892) was my husband's 1st cousin, 4x removed. He was also Edson's father...and he got married in December, as did his son 51 years later. Isaac registered for the Civil War Draft in 1863, listing his occupation as farmer.
• December 12: Jessie Steiner and John R. Rummel. Jessie Steiner (1880-1947) was my husband's 1st cousin, 1x removed. Her marriage took place 117 years ago today, exactly one week and one day after her 21st birthday. She was a magazine agent, married to a druggist. She died one day after her 67th birthday. 
• December 16: Emma O. Larimer and James Freeland. Emma (1848-1923) was hubby's 2d great aunt, the oldest daughter of Brice S. Larimer and Lucy E. Bentley. Emma was brought up in the rural town of Goshen, Indiana, married at the age of 21 and later, the family moved to New York City. Their wedding was 149 years ago.

Thanks to Amy Johnson Crow for this week's #52Ancestors prompt of "winter."

John and Mary Appear HOW Many Times in the Wood Tree?

Do you know exactly how many times certain common names appear in your family tree?

For this week's #52Ancestors challenge, I set out to count the number of males named John and the number of females named Mary in my husband's ancestry.  I knew there were a lot, but I was surprised at the actual number.

Using RootsMagic's Explorer function, I searched my husband's family tree (combining mother's and father's sides), which contains 2,665 people in all.

First, I searched for "Mary" in the given name field. As shown above, the software found "Mary" as either a first given name or a second given name. "Mary Elizabeth" was counted, as were entries like "Margaret Mary," because both have "Mary" in the given name field.

Then I searched for "John, which brought up "John" and "Johnathan" plus entries like "Thomas John" because "John" appeared somewhere in the field for given name.

In all, the software found:

• 121 Mary entries            and
• 139 John entries

So there really are a lot of John and Mary names in the tree! (Five "Mary Wood" entries and five "John Larimer" entries show how multiple generations followed this naming tradition.)

Try it for yourself and see how many "John" and "Mary" names are on your tree!

By the way, I noticed some less common given names for females in the Wood tree: Elvea, Perlina, Floyda, Melvina, Zula, Asenath, Ora, Sophronia, Capitola, and Tatsy.

Among the less common given names for males in the Wood tree are: Restcomb, Train, Green, Ormond, Degory, and Glynn.

Thanks to Amy Johnson Crow for this week's #52Ancestors prompt of "random fact."

Father and Son Share a Birthday

My Facebook genealogy persona, Benjamin McClure, is my husband's great-great-grandfather.

Benjamin was born on April 30, 1812, only 6 weeks before the start of the War of 1812. He died on February 21, 1896.

Benjamin married Sarah Denning (1811-1888) on July 30, 1831. Both were 19 years old.

Who else in this family tree was born or married in April? Getting an answer was a cinch, using my RootsMagic 7 software.

On the "reports" part of the menu, I selected "calendar" and entered April, as shown in the screen shot at top. I requested both birthdays and anniversaries.

Turns out that Sarah and Benjamin's son, Theodore Wilson McClure (1834-1927) was born on his father's 22nd birthday, which was April 30, 1834.

Theodore was baptized in June of 1835, in West Union, Ohio, I learned from the Presbyterian Church records on Ancestry (snippet above).

And, thanks to the calendar function on my RM7 software, I could see at a glance that Theodore Wilson McClure got married on April 15, 1858, to Louisa Jane Austin (1837-1924). He was 23, she was 21. I imagine his parents both attended the ceremony, which was in Wabash, Indiana, where Benjamin was a well-respected landowner, farmer, and civic leader.

Following the prompts for Amy Johnson Crow's #52Ancestors series has encouraged me to use more functions of my software and to consider so many different aspects of my ancestors' lives. Thank you!

Looking for Youngest Brides and Grooms Reveals Gaps

Thanks to the #52Ancestors prompts from Amy Johnson Crow, I'm learning more about the features available in my genealogy software of choice, RootsMagic7. Only with the help of the various reports and lists in this software can I identify the "youngest" of anything, which is this week's prompt.

At top, the "statistics" list I generated for my father's Burk - Mahler family tree. Here, I learned that the youngest age at marriage of anyone in that tree was 18 for a female and 19 for a male. This is only for marriages where I know the birth dates/marriage ages of bride and groom, so the software can calculate statistics. As shown at top, there are 184 people with marriage ages included in this tree.

Directly above, the statistics list I generated for my mother's Schwartz - Farkas family tree, showing 117 people with marriage age noted in the tree. The youngest age for a woman at marriage was 15 1/2, compared with 17 for a man. Since some of these marriages took place in Eastern Europe in the mid-1800s, it's not too surprising that a bride would be this young.

Learning to use the reports is going to help me find anomalies and correct mistakes. For instance, a statistics list I generated for my husband's Wood family indicated that the minimum age for a male at marriage was 17.41. That's such a specific number. It could be correct, but I want to double-check. And I need to look more closely at missing marriage ages to see whether I can fill some of the gaps in my records. More research is in my future.

Jane: The Name in the Middle

Margaret Jane Larimer McClure at right, with daughter Lucille Ethel McClure
and son-in-law Edward DeVeld

My sis-in-law has always told me that Jane is the traditional middle name for females in her family.

Not in the family tree of my late father-in-law, Edgar James Wood (1903-1986). One of Edgar's aunts was Jane Ann Wood Black (1846-1936), the eldest child of my husband's great-grandparents (Thomas Haskell Wood and Mary Amanda Demarest). None of the earlier Wood family females carry this middle name, so far as I can discover.

We learned that Jane is the most popular middle name in both sides of the family of the mother-in-law I unfortunately never met, Marian Jane McClure (1909-1983). She gave her daughter that middle name, and in turn my sis-in-law gave her daughter that middle name.

Marian's mother Margaret Jane Larimer (1859-1913) and grandmother Elizabeth Jane Rinehart (1834-1905) both had Jane as their middle name. Larimer and McClure ancestors often gave Jane as the middle name of one girl in each generation.

The McKibbin family, which intermarried with Larimer ancestors, included a number of women with Jane as their middle name. Same tradition in the Hilborn family, which intermarried with the Rinehart family.

By the way, I identified all the ancestors with "Jane" as a first or middle name by doing a search with my RootsMagic7 software. Very convenient way to prep for this #52Ancestors post.

Going to the Chapel - His Side of the Family

So many ancestors were married in June, in my husband's family tree and in my tree! I used RootsMagic7's calendar report to see who was married, when, and how long ago, tree by tree. This is a good opportunity to revisit my research, summarize what I know, see what's missing, and take the next step. Thanks to Amy Johnson Crow for this #52 Ancestors prompt.

Here are some of the early June marriages in my husband's tree:

June 3, 1903: Hubby's great-aunt Mary Amanda Wood married August Jacob Carsten 115 years ago in Toledo, Ohio. Sadly, Mary Amanda died at age 32, just months after giving birth to their fourth child. Mary Amanda was named for her mother, Mary Amanda Demarest Wood.

June 10, 1903: At top, the license application for hubby's Grandma Floyda Mabel Steiner and Grandpa Brice Larimer McClure, who married 115 years ago in Wyandot county, Ohio. Only through this record did I discover that Floyda had been married before. She was brave enough to divorce the first husband, who called her vile names and threatened her. Plus she won an alimony settlement!

June 12, 1856: My husband's 2d great-uncle Samuel D. Steiner married Maria L. Forrest 162 years ago in Crawford county, Ohio. While researching the Steiner family in Wyandot county a few years ago, I discovered that Samuel had been arrested for aiding/abetting burglary and not showing up in court. What happened? Don't know yet, but I did find Samuel at home in the 1880 census. 

June 13, 1847: My husband's 3d great-aunt, Elizabeth E. Bentley, married Emanuel Light 171 years ago in Elkhart, Indiana, as shown on the marriage license below. During the 1850s, Elizabeth and Emanuel left their home and traveled west, as her father had done in 1848 early in the Gold Rush. The Light family farmed in California. Despite years of research, the Bentley family's ancestors are still a bit of a mystery, one of my genealogical works in progress.

Chicken Post or Egg Post?

Genealogy blogging feels like a chicken or egg thing.

• When I want to write a post, I research someone or try a new research tool. (Chicken post)

• When I research someone or learn a new research technique, I want to write a blog post. (Egg post)

Which comes first? It depends on what I want to accomplish. Chicken or egg, I always learn something.

During January, I'm participating in Amy Johnson Crow's #52Ancestors challenges, which will provide blog prompts and ideas every week. Weeks #1 and #2 are crossed off my list already. Only 50 more to go, meaning I'll be doing more research on 50 more ancestors. These are chicken posts ;) And I'm participating in the Genealogy Blog Party, which is hosted by Elizabeth O'Neal--more prompts to give me ideas for chicken posts.

Other bloggers also inspire me. I've been reading Janice Sellers' "Events in my family tree" series. And reading Randy Seaver's occasional posts about using RootsMagic features. These gave me the idea for a chicken post, a post where I start by wanting to write and use that as the impetus to learn something or research someone.

I originally wanted to find something timely in the family tree to write about. To do that, I had to learn how to use my RootsMagic "calendar report" function, which I've never investigated. With multiple family trees, I need multiple calendars.

The software allows me to check a box and get a calendar with only living people, as a reminder to send birthday or anniversary greetings. However, I wish the software would also let me check a box and have no living people on the calendar.

The results: My maternal Schwartz tree calendar for January has a few birthdays and wedding anniversaries. My husband's Wood tree for January is so crowded with names and occasions that the software had to print more than 20 names and dates on a separate piece of paper! This makes sense, since his tree has more than 2,700 names, and my maternal tree has fewer than 1,000 names.

On January 13th, the Wood tree shows the marriage of Thomas Short and Margaret Larimer, 176 years ago. I have Margaret's death date, not her birth date (still can't find it, despite an hour of searching this morning), and I have Thomas's birth date but not his death date (still can't find it, darn it). They're on my list to continue researching.

But as part of my research into these two Wood ancestors, I tried out the search function of Elephind, that wonderful free newspaper website--it's searchable from the home page!

In addition, I forced myself to search using the new Find A Grave interface, which I dislike. Unfortunately, no sign of Thomas and Margaret, but at least I'm getting used to the new interface. A little.

This is what a chicken post looks like. I also like egg posts. Both are fun and keep me excited about #genealogy blogging.

Ancestor Timeline Reveals Gaps (Gasp)

Randy Seaver's Saturday Night Genealogy Fun this week was to create a timeline for one ancestor and explain how we created it, along with the image.

Since I'm still a RootsMagic7 newbie (less than 4 months' experience), I was delighted to follow Randy's detailed directions for how he created his ancestor's timeline in RM7. I did the same for my 2d great uncle, Bela Bernard Roth (1865-1941). His first wife was Sali/Zali Kunstler (? - 1895), sister to my great-grandma Leni Kunstler Farkas (1865-1938). Bela's parents were Shlomo/Salomon Roth and Hannah Klein.

After I created the timeline in RM7, I took a screen shot with my "Preview" function for Mac. To do that, I selected just the timeline itself as it appeared on my screen and saved it as a .jpg. There is more info available in the timeline, but I didn't include all in this screen shot.

As Randy indicates, the look is bare-bones but practical. At a glance, I can see how old Bela is during each moment on the timeline. When his children were born, when he came to America the first and second times, at the point of each census, when he died.

This timeline reveals (gasp!) gaps for me to research. For instance, Bela had four more children with his second wife (Bertha Batia Weiss, 1885-1967), including one mentioned in a 1907 passenger manifest and a 1914 passenger manifest.

This son, Imre (or Emery) Roth, vanished before the 1920 U.S. Census. He's a gap that I'd like to fill with more information so I can record him and honor his memory. For now, Bela's timeline will have to state that son Imre/Emery died "before 1920."

Family History Month: Top 10 Surnames on the Family Tree

Picking up a great idea from Colleen G. Brown Pasquale at her Leaves & Branches blog, I learned how to use the "surname statistics list" report function on my Roots Magic 7 software. No surprise that for my husband's family tree, Wood was the top surname by frequency, followed by Larimer.

But I also realized, with a pang, how many people appear without surnames in that tree. Uh oh. These are mainly missing maiden names, stretching back to the 1500s. This means I'll have to intensify my Genealogy Go-Over to see how many missing surnames I can identify. Perhaps new information has become available since I added some people to the tree? Turns out that these statistics can also reveal gaps in research...

The top 10 surnames that appear most frequently on the Wood tree are:

1. Wood (earliest instance: 1551)
2. Larimer (earliest instance: 1719)
3. McClure (earliest instance: 1660)
4. Steiner (earliest instance: 1802)
5. Slatter (earliest instance: 1811)
6. McKibbin (earliest instance: 1766)
7. Hilborn (earliest instance: 1794)
8. Denning (earliest instance: 1775)
9. Smith (earliest instance: 1724)
10. Cushman (earliest instance: 1578)

PS: Randy Seaver made this "top 10 surnames" theme the subject of his Oct. 21 Saturday Night Genea-Fun.

Family History Month: It's Backup Day

Happy Family History Month! A great time to think about backups. The first day of every month is backup day--in reality, every day is my backup day. To avoid losing any tiny bit of my precious genealogy research, I use a "suspenders and belt" system.

Let me suggest not just suspenders, not just a belt, but both and more to keep those pants up! Multiple backup methods can do a good job of protecting your valuable files: (1) back up your genealogy software, (2) backup your hard drive daily, (3) do intraday backups of your hard drive if possible, and (4) backup your backups once a month.

One of the things I like about RootsMagic 7 (shown above) is that I can open it, open Ancestry, synch all of my trees, and then back up all my RM7 trees with a couple of clicks. So not only is Ancestry always up to date, my RM7 trees are up to date and safe in multiple places. No matter what software you use, please check on how to back up your trees.

For extra safety, I back up my entire hard drive into the cloud once every day, automatically, using Mozy.

Not to mention my hourly Time Machine backups, as a Mac user, also automatic so I just set it and forget it. If something goes wrong during the day, I can return to the version of my file an hour earlier and go from there.

Being super-duper cautious, I have an extra hard drive for once-monthly backup of my backups. Today is that day. I have nearly 20 years' worth of details on my trees. Keeping all those details safe is a high priority.

Are your files safe? Are your backups safe? For peace of mind, consider suspenders and belt backups.

Saturday Night Genea-Fun: How Many in My Genea-Database?

Randy Seaver's latest Saturday Night Genealogy Fun challenge this week is: How many people are in your gen software database or online tree(s)?

Since I'm a new user of RootsMagic 7, I tried this challenge using the largest tree in my database: Hubby's Wood/Larimer/Slatter/McClure/Steiner tree.

As shown above, this tree has 2665 people and--I'm happy to see--19,084 citations. I'm going to organize my citations and format them correctly, without being too slavish. Sure, I want other people to be able to replicate my research and locate specific records or details. But I agree with the philosophy of Nancy Messier's "My Ancestors and Me" blog: "Done is better than perfect."

Shown at right, my Ancestry tree overview for the same family tree. Number of people is identical, because the synch is up-to-date. I try not to add people until I've investigated the relationship and sources to be reasonably certain these ancestors really belong on the tree.

Note that the number of hints is three times the number of people! When I have a moment, I'll whittle that down by clicking to "ignore" hints for ancestors like "wife of brother-in-law of third cousin once removed of husband's uncle." Then I can concentrate on vetting the hints of people more closely aligned with the tree.