52 Relatives in 2018 #1 Benjamin F. Squires

While I like the concept presented in 52 Ancestors in 52 weeks, some of the prompt words were just too difficult for me to use as a writing prompt last year.  This year I am modifying it to better fit me and calling it 52 Relatives in 2018!  #52RelativesIn2018

Here are my “requirements”:
1) I will try to pick a relative who had a birthday, marriage, or death in the previous week.

2) Write a short “biography” of the person.

See, it’s pretty simple.  Here’s my first one.

BENJAMIN FRANKLIN SQUIRES
relationship:  Her 2nd great-uncle

birth:  6 January 1883 in Illinois, United States  [the 1880 US census has his parents living in Henry Co, Illinois]  to Marathon Hattis Squires and Nancy Harriet Mc Cann.

death:  11 July 1966 in Long Beach, Los Angeles Co, California, United States

burial:  Montecito Memorial Park in Colton, San Bernardino Co, California, United States 

image taken by me!

marriage:  to Charlotte May “Lottie” Anderson on 3 February 1906 in Knox Co, Illinois, United States

record-image_3QS7-L99D-QNNN (2)

Uncle Ben and his parents and siblings moved from Henry Co, Illinois to Monroe Co, Iowa sometime between 1880 and 1900 (census records).  Uncle Ben moved back to Illinois to work as a Coal Miner near Brereton, Illinois.  He met and married Aunt Lottie and they moved from Henry/Knox County region of Illinois to Monroe Co, Iowa  sometime between 1906 and 1910.  When Uncle Ben registered for WWI, he was living in Monroe Co, Iowa and still working in the mines.

005250253_01909 (2)

Uncle Ben and Aunt Lottie never had children.  They did take in their niece Anne Izetta Gott (my paternal grandfather’s sister).  My Grandmother never knew the full story behind this.  My Aunt has an invitation to Annie’s 6th birthday party which invited my grandfather (who was 17 months younger than Annie).  I wish I had a picture of that!

I am unable to find the 1920 Federal Census for them.  Annie is not with her mother or father in 1920 so I presume she is still living with Uncle Ben and Aunt Lottie.

Sometime between 1927 and 1930, Uncle Ben, Aunt Lottie, and Annie moved to San Bernardino Co, California.   Annie married in 1927 in Iowa so we know they were still in Iowa at that time.

41697_329232-00819 (2)
I found California Voter

In 1930, they were living in Redlands, San Bernardino Co, California.  Annie and her new family were living next door and Uncle Ben’s sister Ruth Ann Squires Hodenfield was in the same town.  Annie died 2 Oct 1932.  Her husband and children moved back to Iowa by 1935.  Sister Ruth and her family also moved back to Iowa by 1935.

Uncle Ben and Aunt Lottie moved into Los Angeles Co, California sometime between 1930 and 1934 – closer to my grandparents/his nephew and continued to live in Los Angeles Co, California until death.

In the 1928-1930 Voter Registration for Redlands, California, Uncle Ben is listed as a Socialist.  In 1934 for Los Angeles Co, he was registered as Democrat.  In 1942, he lived in Azusa, California and worked for Helms Bakery (oh, the memories of the bakery truck!)  On a side note, Uncle Ben’s WWII registration form lists my grandfather as the person who would know his address.

004669333_00552 (2)

I vaguely remember Uncle Ben and Aunt Lottie.  He made me a doll house when I was young and my parents still have the table he made them.  We call it the Uncle Ben table!

When I saw this picture online, I knew the person who posted it must be related – I have the same one!  Here is a picture of Uncle Ben and Aunt Lottie in 1956 at their 50th wedding anniversary.  The family resemblance to my grandfather is remarkable!

Benjamin F Squire and wife Lottie - 50th anniversary (1)
photo from personal collection

 

Citations:

“Illinois, County Marriages, 1810-1940,”  database, FamilySearch (https://familysearch.org/ark:/61903/3:1:3QS7-L99D-QNNN?cc=1803970&wc=326F-BZS%3A146199201 : 3 March 2016), 1412063 (004031824) > image 448 of 1362; county offices, Illinois.
Year: 1880; Census Place: Hanna, Henry, Illinois; Roll: 213; Family History Film: 1254213; Page: 345A; Enumeration District: 112
Ancestry.com and The Church of Jesus Christ of Latter-day Saints. 1880 United States Federal Census[database on-line]. Lehi, UT, USA: Ancestry.com Operations Inc, 2010.
Year: 1900; Census Place: Pleasant, Monroe, Iowa; Roll: 449; Page: 11A; Enumeration District: 0088; FHL microfilm: 1240449
Ancestry.com. 1900 United States Federal Census [database on-line]. Provo, UT, USA: Ancestry.com Operations Inc, 2004.
Year: 1910; Census Place: Mantua, Monroe, Iowa; Roll: T624_414; Page: 11A; Enumeration District: 0099; FHL microfilm: 1374427
Ancestry.com. 1910 United States Federal Census [database on-line]. Lehi, UT, USA: Ancestry.com Operations Inc, 2006.
Registration State: Iowa; Registration County: Monroe; Roll: 1643221
Ancestry.com. U.S., World War I Draft Registration Cards, 1917-1918 [database on-line]. Provo, UT, USA: Ancestry.com Operations Inc, 2005.
Original data: United States, Selective Service System. World War I Selective Service System Draft Registration Cards, 1917-1918. Washington, D.C.: National Archives and Records Administration. M1509, 4,582 rolls. Imaged from Family History Library microfilm
Iowa Department of Public Health; Des Moines, Iowa; Series Title: Iowa Marriage Records, 1923–1937; Record Type: Microfilm Records
Ancestry.com. Iowa, Marriage Records, 1880-1940 [database on-line]. Lehi, UT, USA: Ancestry.com Operations, Inc., 2014
Year: 1930; Census Place: Redlands, San Bernardino, California; Roll: 188; Page: 11A; Enumeration District: 0070; FHL microfilm: 2339923
Ancestry.com. 1930 United States Federal Census [database on-line]. Provo, UT, USA: Ancestry.com Operations Inc, 2002.
The National Archives at St. Louis; St. Louis, Missouri; World War II Draft Cards (4th Registration) for the State of California; Record Group Title: Records of the Selective Service System, 1926-1975; Record Group Number: 147
Ancestry.com. U.S., World War II Draft Registration Cards, 1942 [database on-line]. Lehi, UT, USA: Ancestry.com Operations, Inc., 2010.
California State Library; Sacramento, California; Great Register of Voters, 1900-1968
Ancestry.com. California, Voter Registrations, 1900-1968 [database on-line]. Provo, UT, USA: Ancestry.com Operations Inc, 2017.

 

 

 

 

Advertisements

Error Report Drama!

So here it is – the error report is kind of messed up.

For the first 2 people with “sex unknown” I changed their sex to female – which they are.  Since the report was generating in FTM, I made the change in Ancestry to prevent messing with the FTM tree while is was working.

When the report was finished, I also made the change in FTM.  I then synced the trees.

Guess what?  Those same 2 people now show up on the new data report as having duplicate events!  Guess the category yet??  Sex!

I assumed when I synced that it would notice that both trees have the sex as female.  Guess again!

Maybe some of my merging duplication isn’t necessarily my doing!

This is going to be a long haul!  I have decided changing it online is easier if I will need to search for supporting documents but things like sex changes are easier in FTM.

 

Is Error Report Accurate??

This has been one of the most frustrating exercises proposed as a “Saturday Night Genealogy Fun”.  My first run of the data error report yielded 48 pages.  I’ve spent close to 100 hours since that fateful report trying to clean up the stupid duplicate entries – a much needed thing but it has been a real chore.

The duplicates arose from 2 probable events.
1) at the beginning of this genealogy journey, I had each of my grandparents as a separate tree.  After several situations of not remembering how I was related to someone, I decided to merge them.  Merging gave duplicates since I didn’t want to remove any events.  I then decided to merge my line with hubby’s line. Another set of duplicates.

2) I received a GEDCOM from a cousin who is the genealogist for the family association.  I merged my tree with this one and MANY of my duplicates were from this.  This merge also gave me most of the errors of “person’s sex is unknown” and “individual has same last name as spouse”.  To think the “genealogist” would have such a messy tree was mind boggling.

So I have rerun the error report and somehow I still have 17 pages of errors.  I know that some of the “Sex Unknown” are legitimate – a baby died before death certificates were mandatory and no one remembered what sex the baby was.  Understood.

So know I question the accuracy of the error report.  I compared some of the names that I know I didn’t touch on the 48 pages of errors and now they show up as an error.   How do I trust this??

So I’m off to fix the 17 pages of errors and will not add any individuals – just fix the error, run the report again and see what happens.

I’ll let you know what happens!

Christmas Came Early!

My husband got tired of listening to me complain about switching tabs while trying to clean up my main tree.   The problem solver that he is – a second monitor for my computer would make my life easier (and his quieter!).  After purchasing the second monitor, he couldn’t contain himself (since I have 48 pages of weird duplicate entry errors) and gave it to me yesterday!

My genealogy endeavor just got easier!!  Thank you husband!!

IMG_4348

Cleaning up the tree!

After finding out I had over 1,400 “issues, I’ve spent about 6 hours so far “cleaning” up my tree and have only eliminated about 60 from my list.  (I didn’t count – it was 2 pages worth.)  It has also caused the addition of about 30 people to my tree (those darn census records!)

Things I’ve discovered during that 6ish hours:
1) expect to spend time not just fixing the issue but looking at the hints on Ancestry.
2) those darn hints are addictive, especially when they link to real documents that you just have to look at and confirm they are really for that person.
3) most of my “errors” are duplicate entries for residence, birth, name, and death.
4) when a cousin sent me a copy of the family association tree, merging created MANY of those errors – for some reason the information was added to the existing people instead of merged.
5) I may be at fault for the duplications – I’m sure my thinking was “I want to verify the documents instead of assuming they are correct.”
6) I must have been crazy that day!!  Yet I would rather have to do this cleanup that to find I have true errors that aren’t as easily fixed.

7) I envy those with just a few errors!!

 

Genealogy Database Problem Report

Saturday Night Genealogy Fun — Genealogy Database Problem Report

 It’s Saturday Night – time for more Genealogy Fun!

Your mission, should you decide to accept it (cue the Mission Impossible! music) is to:

1)  Is your genealogy software family tree database perfect?  With no errors or inconsistencies?  Yep, mine isn’t either!  Big time.  With over 49,000 persons there are bound to be some errors in my tree.  Even 1% would be 490 persons or 1,500 events!

2)  This week, find your genealogy software’s “Problem Report” or something similar.  Tell us how you found it, and what it tells you about the problems in your family tree database.

3)  Share your results with us in your own blog post, in a comment to this post, or in a Facebook post.

So here’s mine:
1) I’m hoping for less than 10% of my tree to have errors.  My tree has 21,389 people so 10% would be 2,139 – yep, I’m rounding properly!!
2) To gather this information using Family Tree Maker 2017:
  • go to Publish, Collection, Person Report, Data Errors Report, Create Reportcapture 1_LI
  • Click All Individuals, then Errors to Include  Capture 2_LI
  • A pop-up screen will show all the possible errors the program will look for.  Here is the before and after pop-up for mine.   Capture 3
  • The first report took several minutes to generate – that can’t be a good sign!  It generated 265 pages – I’m not even going to try to count the number of people!  As you can see, most are missing birth date and missing marriage date.Capture 5
  • I ran the report again after  I removed Name Contains Nickname, Name Contains Title, Name Contains Invalid Characters, Name Contains Misplaced Dash, Birth Date missing, Person does not have a preferred spouse set, Person does not have a preferred parent set, and Burial Date before Death Date. Capture 6
  • This report generated 141 pages.  Better but I’m still not going to count them all!Capture 7
  • Then I ran it to remove marriage date is missing.  Now I’m down to 49 pages.  So looking at Leta Violet AGEE, the report says a possible duplicate event: Name.  What the heck does that mean?  Is there another person with the same name? Did her name somehow get entered twice ??  She is now going to be my first research question today!  PROBLEM ANSWERED!  Evidently when I merged 2 trees, it put the same information in twice for her!Capture 8
  • I counted the individuals on the first 12 pages and got 364 individuals; 48 pages + 3 on page 49 would be approximately 1,459 individuals with errors.  That is about 6.8%.  Now I have something to do hahaha

Grandma’s Photo Album #3

Here’s the next picture in the photo album.  This one has no identifying marks on front or back.

The photo album belonged to my great-grandmother Lottie Smith Fetherkile.  We found it while cleaning out my great-grandfather’s house after his death.  Grandma Lottie died in 1926 so we know all were taken before this date.  I figure if I put them out there, maybe someone will recognize a relative and let me know who it is.

Anyone have a guess as to approximate date???

IMAG0005-page-001 (2)