Thanks to the free online word cloud generator here, which includes a tree shape and the option to customize colors, sizes, and fonts, not just names.
My 1c2r Annie Jacobs died on this day in 1896, only 13 months old. She was the third child of my great uncle Joseph Jacobs (1864-1918) and his wife, Eva Michalovsky Jacobs (1869-1941).
As shown on her death cert above, little Annie died of bronchitis, with other illnesses contributing to her death. She was buried in the Plungianer society plot of Mount Zion Cemetery in Queens, New York.
The Jacobs family suffered many hardships and losses after arriving in New York City from Russia. Joe came first in 1882, bringing his mother Rachel Shuham Jacobs within a few years. He became a US citizen in 1888, and married another immigrant, Eva Michalovsky in New York City on March 2, 1890. He initially worked as a cap-maker and a tailor to support his family, but as his health declined, he later worked as a janitor.
Joe and Eva had four daughters and two sons together. Sadly, Annie was the first of their children to die, followed by Pauline in 1907 (at age 6) and Flora in 1923 (at age 32). Joseph's mother Rachel died in 1915, and he himself died in 1918 of Parkinson's, after being hospitalized for nearly a decade.
Dear cousin Annie, I'm keeping your memory alive as I blog about you, and put your story on public family trees, 127 years after you passed away.
It was postmarked 12 February 1912, sent from Chicago to Cleveland.
The senders were Nellie (Rachel Ellen) Wood Kirby and her second husband, Arthur Kirby.
How many six-year-olds get mail? Wallis (the correct spelling of his given name, not the wrong spelling shown on the card) was probably happy to see this pretty card from relatives!
But what about public family trees that show the wrong individual instead of the person you can now prove is the real ancestor? Or collaborative trees where someone is perpetuating incorrect info? I have some ideas, please read on!
Ask questions, answer questions
Reading that source, I had questions: Why would S.L. Hixon be named that way, rather than with a given name and the surname of Bentley? Also, reading the rest of the page, it seemed clear that S.L. Hixon was male, since he had a first wife named Nancy (above the green arrow) and is mentioned in the final sentence as "Mr. Hixon."
My theory was that the book was naming only the fathers of the first two babies born among settlers in 1835. Digging deeper, I was able to locate and order a death record for Lucinda. Although only an extract was available at that time, it clearly showed Olivia Morgan as the mother's maiden name, NOT S.L. Hixon.
Therefore, I added Olivia Morgan as a new name to my family tree, and uploaded the death cert extract as proof she was Lucinda's mother. Six other people subsequently saved the extract as source to their family trees. Later, Lucinda's actual death cert became available and I attached it as my source, as well. Even though death certs aren't necessarily completely accurate, I felt fairly confident because I found Olivia's name on another child's documents.
BUT you don't have to wait for anyone to ask a question. You can simply post your own comment about proof on a source or on your ancestor's profile. If your tree is public, any researcher can read your comment. Maybe that comment will diminish the spread of incorrect info and encourage the spread of accurate info.
Show your proof as a source
On Family Search, I posted a document and explanation to confirm that Olivia Morgan was indeed the mother of Lucinda Helen Bentley Shank.
This is an easy way to share your source and reasoning with others who are researching the same ancestors--and, hopefully, persuade them to leave the facts intact based on your evidence.
UPDATE: In her comment below, Teresa Eckford recommends using the new "notes/alert" function added to FamilySearch a few months ago. Here's a link to learn more about this easy way to let others know about important research info for a particular ancestor. TY to Teresa for this excellent suggestion!
In Democracy's Data, Dr. Dan Bouk pulls back the curtain on the surprisingly contentious and complicated process of planning and implementing the US Census throughout American history.
No boring, stale history here. His highly readable book puts the 1940 Census under the microscope as a great example of hidden stories of people and the nation--and how to tease out stories from the mass of data collected. Highly recommended!
Chapter 1, "The Question Men," is aptly named because all but two of the people who planned the 1940 US Census questionnaire were male. All were white. Government officials were well represented but so was the world of commerce, with the head of Sears, Roebuck in attendance, insurance execs, union researchers, academics, and more.
Dr. Bouk's exploration of Census design makes a key point clear: "The census 'made' the facts that its columns defined. It hid the facts that its columns denied."
So when immigration was of national concern, the 1920 US Census asked questions about citizenship status, language spoken, etc. By 1940, the Question Men were less concerned about immigration and more concerned about internal migration, one of the effects of the Great Depression, and about income levels. The questions added and removed reflected these changing priorities.
Don't miss the Epilogue, where Dr. Bouk describes his experience with the 2020 US Census, comparing the enumeration process and questions to those of earlier Census years, and explaining the ramifications of various responses.
"I want to be counted so that my individual data (and the story it tells about me and my country) will survive. I appreciate that I and all of my neighbors will have some trace of our existence preserved permanently," he writes. I share this sentiment.
Unfortunately, Dr. Bouk isn't reassured about the "permanence" of today's Census data, because the 2010 and 2020 Census data are being stored only digitally, no paper trail at all, no microfilm either. He's worried about media obsolescence and whether our 2020 Census responses will still be available in 2092, when the individual results are to be publicly revealed. I share his worry.
To hear the author speak about this book, of interest to all genealogy folks who use US Census data in their research, take a look at one of these two videos:
I've been honoring their memory by not only adding them to my family trees but also creating or improving memorial pages on Find a Grave. This includes linking my ancestors' memorial pages to the pages of their parents, siblings, and children.
For the first time yesterday, I discovered that Find a Grave limits how many people a single user can claim in a niece or nephew relationship. At top of this post, you can see the notice displayed on Find a Grave when I attempted to have my niece relationship displayed on the memorial page of an uncle who died in the 1980s--someone I'd known and hugged.
Find a Grave's explanation is:
We limit the number of memorials you can manage within each relationship type to help prevent abuse.
There is an option to appeal to the support center...which I may do at some point. For now, at least I'm the manager of these memorial pages and can add bite-sized bios, photos, etc.
Deep into his 2023 long program, in contention for a gold medal, he slipped on a key jump. Yet by the end of his performance, Jason was smiling (and so was his coach). They knew the rest of his performance was terrific! He earned a silver medal, despite his oops.
Although my genealogy research isn't "live" like a sports performance, the results are very much on display because my family trees are public (except for 2 speculative trees). And as much as I strive for accuracy, I don't always get everything right.
Over the years, cousins (and FAN club members) have been in touch with all kinds of corrections and suggestions--for which I'm truly grateful. They've not only helped me recover from a genealogy oops, they've set me on the path toward additional discoveries.
One example from 10 years ago: My Philly cuz urged me to reconsider a small but critical detail in my research into our Schwartz family. I thought I was looking for "Violet," which sent me down one investigative path, researching someone of that name who was from the same home town as our Schwartz ancestors, had the same maiden name. Violet's story had been well documented but alas, she was not part of our Schwartz branch.
Philly urged me to look for "Viola." When I retraced my research steps, with "Viola" firmly in mind, I saw more had become available since my initial search--leading to an amazing, emotional breakthrough. What had been an "oops" turned into a powerful and enduring connection with my cousins -- even as it strengthened the accuracy of my family tree.
--
"Oops" is this week's #52Ancestors challenge from Amy Johnson Crow.
When I began my genealogical journey 25 years ago, I had only a vague thought that anyone in my family tree had been directly harmed by the Holocaust. My parents and grandparents never spoke of it, mentioned no names.
It is only because of Yad Vashem testimonies, a photo in one testimony that looked so much like an old photo I'd inherited, and a survivor's video interview that I was able to discover how the horrors of the Holocaust stole the lives of too many of my ancestors.
Last week, my wonderful niece Kay said Kaddish for our murdered ancestors during a visit to Auschwitz. She also felt a sense of relief that some imperiled family members ultimately survived.
I now know the Holocaust victims and survivors in my family tree were descendants and in-laws of my great-grandparents, Herman Yehuda Schwartz (1857-1921) and Hani Simonowitz Schwartz (1858-1933). Herman and Hani raised their children and welcomed grandchildren at their home in Ungvar, Hungary (now Uzhhorod, Ukraine).
Schwartz family survivors
Viola Schwartz (1925-2019), a granddaughter of Herman & Hani, who was held at Auschwitz before being transported to a work camp and then being liberated in May of 1945. My sister met Viola and her family in Israel some years ago!
Dezso Gyula Winkler (1900-1995), a grandson of Herman & Hani, who made his way to Israel after World War II and became a citizen before moving to America, where he later became a naturalized US citizen.
Albert Bela Winkler (1912-1993), a grandson of Herman & Hani (and twin brother of Lili Winkler Feldman, who died in Auschwitz). Albert survived, arriving in America after the war and becoming a naturalized US citizen in the 1960s.
Leni Louise Winkler Price (1909-1997), a granddaughter of Herman & Hani, who evaded capture by first fleeing to Belgium and then sailing to America from Portugal, arriving in America in 1941 with her husband and child.
Schwartz family victims
Rezi Schwartz Winkler (1881-1944) was the oldest child of Herman & Hani. Fate unknown of her husband Moritz Winkler. Their son Albert Bela Winkler survived and submitted testimony about his mother's death in Auschwitz and the death of others in the immediate family:
Etel Schwartz Stark (1892-1944), a daughter of Herman & Hani, died in Auschwitz (fate unknown of Etel’s husband Fissel Ferencz Stark and their child Mici Stark).
Paula Schwartz (1898-1944), a younger daughter of Herman & Hani, was killed at Auschwitz. Her daughter Viola survived Auschwitz and also submitted testimony to Yad Vashem, which started me on my quest to learn more a decade ago when I found the written testimony and the photo of Paula.
In-laws who perished in Holocaust include Gyula Preisz (1908-about 1944), who died as a result of being in a forced labor battalion, according to Yad Vashem database. Others were in the Simonowitz side of the family, no specifics known at this time, sorry to say.
May their memories be for a blessing. Never forgotten. Never forget.
That's why I've been looking at the US Library of Congress prints and photos collection. It includes a gazillion digitized images available to view, and sometimes to download, for free. Not just of America, but well beyond.
LOC prints and photographs online catalog
Start by going to the Library of Congress catalog page for prints and photos. One entire area of the collection is devoted to US Civil War images (my husband has 20+ ancestors who served on both sides of that war).
Other featured collections are listed by name on the main page. A tiny sample includes:
It's easy to browse specific collections and check whether any of the images are available for free download.
Search by keyword (place, subject, etc)Another way to find suitable images for family history projects is to use the search box. At top, you can see I searched for "New York City" images and received more than 27,000 results. Most of my immigrant ancestors came through Castle Garden and Ellis Island and remained in the Big Apple, which is why I'm interested in images of the city and its people and institutions.
I found lots of images depicting aspects of daily life in Manhattan during the first decades of the 20th century--when and where my ancestors first lived upon arrival from Eastern Europe.
Another search, for images of Jewish life in New York City, resulted in numerous results, including the collection shown in this image, covering the period when my Jewish ancestors were just getting settled in the city.
This group of images is part of the much larger George Grantham Bain Collection. The Library of Congress notes: "The collection richly documents sports events, theater, celebrities, crime, strikes, disasters, political activities including the woman suffrage campaign, conventions and public celebrations."
Free to use and reuse
The Library of Congress has made free images very accessible with a link at bottom of its home page that leads here.
Down the rabbit hole I go, and if you're interested in images to illuminate your family's history in America (and beyond), do take a look at the Library of Congress.
Did the AI get it right? Let me add two more perspectives on this distinction:
Her inquiry sent me on a quest to learn when, where, and how my paternal grandfather Isaac Burk died. This was the good ole days of cranking microfilm readers and using snail mail to order vital records, so it took a good few years.
When I eventually received his death certificate, I learned he had a heart attack and died in 1943 in Washington, D.C. I didn't discover why Grandpa was in Washington and who the informant was on the death cert for a few more years. Spoiler alert: He and Grandma were visiting her favorite sister, whose husband was the informant.
Still, I didn't know what Grandpa Isaac looked like. I recognized his wife, Henrietta Mahler Burk, in old family photos standing alongside my Dad. However, Grandpa Isaac wasn't in those particular photos.
Once digitized records became available online, I found Grandpa Isaac's face on his petition for naturalization from 1939, along with his signature. It wasn't a great photo (actually kind of faded and faint), but it showed the shape of his face and his features. Going back to older family photos, I could then pick him out, despite changes in weight and age over the years.
Not long ago, I used MyHeritage's photo enhancement/repair tools to fix Grandpa Isaac's photo. There it is at top of this post--my favorite photo because he is the reason I got bitten by the genealogy bug.
"Favorite photo" is Amy Johnson Crow's prompt for week 2 of the #52Ancestors genealogy challenge.
For my tree, I was given an incredible head start by many talented WikiTreers during the December, 2021 challenge when I was extremely fortunate to be the featured guest. Three brick walls smashed on my tree, plus intriguing clues for me to follow up!
Adding hubby's ancestors individually
Now I'm focusing on my husband's tree, entering each ancestor individually. This helps me slow down and analyze all research and relationships carefully, aiming for accuracy and searching for connections.
At top, the profile I created for hubby's 3d great-grandfather John McClure, whose dates are approximate but birth, marriage, and death places are definite.
Trying to add his father, Alexander McClure, I discovered that someone had already created a profile for this ancestor and for his second wife Martha [maiden name unk] McClure.
Connecting to existing profiles
Now my hubby's branch connects to ancestors who have already been documented on WikiTree, for the first time. That means I can collaborate with researchers working on mutual ancestors on WikiTree, examining their sources and building on their previous research while contributing what I've learned.
As I move upward and outward on the McClure branch of the family tree, I'm looking forward to collaborating with other WikiTreers.
Telling more stories
My late mother-in-law Marian McClure Wood (1909-1983) was the first owner of this pin. I'm sad to say she passed away before I joined the family. But fortunately, her granddaughter remembers how Marian loved to wear pins, and she also told that story as the pin's new owner listened intently.
In fact, the family has a number of photos of Marian wearing a pin prominently on her lapel. Not this particular pin, but others. She had personal style as well as an artist's eye. The family has told and retold stories about the small animal statues she made while taking lessons from a world-class ceramicist. Plus I have a box of her needlework creations (tablecloth, gloves, doilies) to share with descendants in the future. My goal is to share heirlooms while telling stories so recipients get a sense of why these items are important to family history.
Keeping her memory alive
How I wish I could have met Marian McClure Wood, a talented, creative woman. I would ask about her creative endeavors and her early life as a much-loved only child. Of course I would ask about her memories of ancestors, with a few specific questions about an in-law who married three times.
Mom-in-law Marian would probably have been amused to know her son married another Marian, who is a needlework enthusiast and a wearer of pins.
Most of all, I hope she would be pleased that her creations are still treasured by the family and accompanied by stories about her life, keeping her memory alive for years to come.
"I'd like to meet" is Amy Johnson Crow's first #52Ancestors prompt of 2023.
This little link can lead to interesting genealogical information! It's there because Find a Grave and Fold3 are both owned by Ancestry.com.
Fold3 memorial pages are FREE
Go ahead and click the link leading to Fold3--because a memorial page is completely free to view (or create or improve).
Above is part of the Fold3 memorial page for Union Army veteran Train C. McClure, which popped up when I clicked the link from Find a Grave. I can navigate to facts (shown in timeline format), stories, gallery, and sources.
In the facts section, you'll see that the sources of both the birth date and birth place are 1 Fgv Document. Translation: one Find a Grave page.
What are the sources?
In the sources section of this memorial page, there are two records attached (see below).
One is Civil War info from Fold3, and the other is the Find a Grave memorial for Pvt Train C. McClure, marked as a Fgv Document. Since Pvt McClure is in my husband's family tree, I examined everything in detail.
Other documents, images, even photos may be attached to a veteran's Fold3 memorial page, so definitely click to see what you can learn. Save whatever you can to your own computer, attach to your family trees, and follow up any clues.
