Organize Your Family History

Stay focused and happy while exploring your roots

Time for January 30 x 30 check in!

By 14 Comments

It’s almost the middle of our January 30 x 30 challenge. For those of you who signed up, how is it going? Are you managing 30 minutes of genealogy research (or organizing or scanning or whatever it is you set out to do)?

My challenge was made a little extra challenging by travel. I was in Walla Walla, Washington, visiting my dad from January 3 to 12.  I’m happy to say that I did manage to research every day, but one of those days barely counts. The day I traveled home (a 12-hour journey by car and plane) I thought I’d get research done on the plane, but when I started working I just wasn’t in the right frame of mind. So the ten minutes I put in was barely productive. I give myself credit for at least trying, but execution was not impressive.

One thing that’s helped me get back on track is that yesterday, back at my desk, I decided to pull out my 2nd great grandfather’s Civil War pension file, which I’d received way back in 2015. At the NGS conference that year, I heard Julie Miller talk about these files: what they contain and how to process them. I immediately requested the complete pension files for my three Union veteran ancestors from the National Archives. I’ve already processed the other two but had not focused on the file of Benjamin Franklin Igleheart. Since I’ve turned my attention to the Igleheart line, this is a natural thing for me to work on.

Once I pulled it out of the file (I haven’t yet scanned it), I saw that I’d started by putting the pages in chronological order and created a source citation for the whole pension file. The next step is to create a source citation for each individual document, print the citation on a label and affix the label to the paper document before scanning the whole document. After it’s scanned, I’ll start transcribing it. Yesterday I spent 45 minutes creating the citations and their labels and got through about eleven documents before having to move on to something else. For the near future, this will be the project I’ll be working every day.

I’d forgotten how great it was to have a project like this that I can break down into tiny bites. I love knowing exactly what I’m going to be working on and I love that there are lots of little milestones in this giant project so I can celebrate my progress.

Enough about me. I hope your challenge is going well and I look forward to hearing about it in the comments!

Time of day matters with cemetery photos

By 10 Comments

As I’m processing the photos I took on my Kentucky research trip, I’m realizing an important aspect of research-trip planning that I hadn’t taken into account: the time of day I visit cemeteries.

On my June 2019 trip, I visited two cemeteries I’d seen in October 2014. I took pictures in both cemeteries on both trips–there was more to discover on my second trip, since I knew more about my family tree. One thing I noticed is that my 2014 photos taken at noon at the Sacramento Cumberland Presbyterian Church are so much better than the ones I took at 6 pm in my June 2019 trip to that cemetery. (The I visited the other cemetery, Poplar Grove Cemetery, at the same both trips, about 2 pm.)

Taken 16 Sep 2014, 12:07 pm

grave marker taken in good light

 

Taken 24 June 2019, 6:04 pm

grave marker taken in poor light

I understand there are all sorts of variables that can go into getting a great shot, but you can see that the first photo, taken on a partly cloudy day at noon, is much better than the second photo, taken on sunny June day at 6 pm. It doesn’t help that the grave marker faces east! (Since I knew I had a great shot of that grave marker, I didn’t worry much about the quality of that second photo.)

Here’s another example, of the marker for my second great uncle, Ellsworth McEuen, in the same cemetery:

Taken 16 Sep 2014, 12:35 pm

Taken 24 June 2019, 6:03 pm

 

On my next research trip that includes cemeteries, I will do my best to visit them when the sun is high to avoid these challenges!

Reconnecting with my research

By 4 Comments

Reconnecting with my genealogy researchI was out of town for ten days and I managed to sneak in a little genealogy research. I returned on May 7 to a full client schedule for my organizing business. I’m certainly not complaining about that, but I have not had the energy and time to do any genealogy research for over a week.

I was regretting that state of affairs when I realized I didn’t have to have a large swath of time available to me in order to get some research done. Sometimes just spending a little time on it to reconnect me with my ancestors and get the ball rolling again can be really beneficial.

In the past, a big barrier to my starting a research session was figuring out what to work on. But now I have a few small, systematic projects I can always fall back on. This morning, I decided to set a timer and work on my research for just 15 minutes. I had three choices of easy things to dive into:

For any of these projects, I could make some progress in just 15 minutes. I chose to work on option #1, checking my source documentation. I have a checklist in Evernote in which I check off each source after I’ve made sure that the source citation is good, the multimedia file is attached to the source and the pertinent data from the source was included in Reunion. When I finish a source I check it off so I can always see where I stand.

This morning, the next source on the list was the Compiled Service Record for a different 2nd great grandfather, Benjamin Franklin Igleheart (1845-1913). I hit the jackpot, because I hadn’t done a great job of extracting data to include in his record on Reunion. The 15 minutes flew by as I noted his eye, hair and complexion color, for example. (His eyes were listed as black!)

I didn’t actually finish going through the 16-page record, but I employed a trick I learned years ago: When my timer went off, I stopped, even though I was in the middle of a document. I know that since our brains crave completion, I’ll be anxious to get right back to the document and finished extracting data from it. Then I’ll check it off my source documentation checklist (another satisfying thing to do). I made a note in my research log to remind me where I left off. I’d be willing to bet I’ll be so anxious to finish it that I work on it this evening.

I find that if I spend too much time away from my research I feel disconnected from it. Taking a little snippet of time to work on it this morning will help me get back to it this weekend, when I have more time.

Sometimes you gotta browse

By 19 Comments

Sometimes you gotta browse recordsI was going crazy looking for my great great grandfather, Benjamin Franklin Igleheart, and his family on the 1880 census. None of my searches of various sites turned him up. I really wanted to find that census, because I knew from the 1900 census that his wife, Mattie, had given birth to 11 children, only three of whom were alive in 1900. I had found five of them, but I assumed that finding the 1880 census would reveal the names of more. (Mattie was 25 in 1870.)

So I decided I would browse my way through the census looking for the family. I had a good idea they were living in McLean county, Kentucky, where he lived before the Civil War. (He fought in that war.) I knew that in 1870 they lived in Arkansas, something I initially doubted but was confirmed in his Civil War pension record. But since they had a child born in 1881 in Kentucky, I felt comfortable trying Kentucky first.

I had found Ben’s mother and stepfather in the 1880 census in Sacramento, McLean, Kentucky, so I started there. I browsed forward a page at a time, scanning the handwritten names. After a few pages, I decided to start looking the opposite direction, so I went back to his mother and started scanning a page at a time backward. Sure enough, just two pages behind his mother, there they were! The words “Igleheart, B.F.” jumped right out at me. His age and his family members’ names and ages matched up. Eureka!

So why didn’t they show up on a search? A simple transcription error. The name had been indexed as “Lylehuist.” When I look at it, I can see why. (I bet you can too, if you squint at the image above.) In Ancestry, where I found the document, I edited the record to add the name Igleheart in order to help others. I don’t see that record coming up on a search of Igleheart, though.

The 1880 family included two children, born in the 1870s whose names I didn’t have. They’ve now been added to my family-tree software. I still have four more children to find.

I have to say, it was really exciting to spot this family. I was in a college library among strangers, so I managed to keep from shouting out.  I did raise both arms in victory, though!