13 May 2015

No Leaves for Benjamin Butler

While generally speaking I am not a fan of the "leaves" at Ancestry.com, there are times when I do check to see if there are suggestions for a person on whom I am really stuck. Sometimes the Ancestry.com leaves float and land in a logical place. Other times they don't.

Benjamin Butler is one of those persons for whom a logically-placed leaf would be appreciated.  He is also one of those person for whom Ancestry.com can find no leaves.

I do have records attached to him in my online tree at Ancestry.com so there is something there to use to find leaves. I have Benjamin in the following census records:

  • 1850-Port Huron, St. Clair County, Michigan--aged 31 born in New York State--apparent wife Margaret
  • 1870-Soap Creek, Davis County, Iowa--aged 51 born in Canada--apparent wife Nancy.
  • 1880-Drywood, Vernon County, Missouri--aged 61 born in New York State--wife Nancy.
I'm not upset nor am I surprised that there are no leaves for my exact Benjamin. He's been a difficult person to find in other records, partially because he moved around quite a bit. However, given that Benjamin Butler is not the most unusual name, I'm a little surprised that there were no leaves (even really moldy ones) at all for him.

I'm even surprised that there were no leaves for a William Butler since that's the name he is enumerated with in 1880.

 There are "suggested" records for Benjamin when looking at his census records on Ancestry.com. The "suggested" records at Ancestry.com are not even for a Benjamin Butler. They are not even for a person with the last name of Butler. They appear to be later records related to Benjamin's children or his children-in-law that another researcher has connected to him.

Benjamin is a good example of one of those people where it can be easy to get "stuck." He was likely born in a state that did not keep vital records at the time he was born, was not a member of a church that practiced infant baptism, moved frequently, and died in a time period and place where good vital records were not being kept. It really is his fault.

I need to revisit what I know about Benjamin and continue my work on his children. Not all of them are reasonably documented and there are several for whom I do not even have approximate dates of death.

It's probably time to stop looking for leaves on the trees and focus on Benjamin's children. 


Giving Credit Where Credit Is Due

A recent post on Germanic script ("Those Were Not Diacritics--They Were Wiggles") included an image from Ernest Thode's German-English Genealogical Dictionary.

It also included a citation and a notation that the image was used with Thode's permission. I'm not even going to concern myself with whether or not the size of my image would have qualified under "fair use." My policy here is to ask permission before using any image anyone else has created.

It's easier that way--and creates fewer problems.

It's also the polite, ethical, and responsible thing to do. Sometimes just because something is legal does not mean that it should be done.

So if you see a  hand drawn image as a blog post illustration that looks like it's been drawn by a child--rest assured I made it. No one usually wants to take credit for those.

FamilySearch: New Canadian Materials

The following Canadian databases are showing as new or updated on FamilySearch since our last Canadian update:

12 May 2015

Free Download of Brick Walls From A to Z--the Final One

Until 11:59 PM 15 May, I'm giving away my "Final" Brick Wall from A to Z webinar for free--just hit "check out with PayPal." You don't need an account or a credit card, just your email to send you the download link.http://bit.ly/1PFLsMZ

This was the 4th in my "Brick Wall" series.

FamilySearch Update: US Passport Applications

The following database is showing as "updated" on FamilySearch  since our last update:

United States Passport Applications, 1795-1925

How updated this is I cannot say.

Those Were Not Diacritics--They Were Wiggles

Sometimes a wiggle is just a wiggle.

Entry 101 in the image accompanying this post was discussed in an earlier blog post, ("When Is It a Diacritic and When Is It Shorthand?").

It turns out that the symbol above the first "a" in "Catharina" is not a diacritic at all. That was how I referred to it in the initial posting--which was incorrect. Instead it is part of the uppercase letter "C."

A reader suggested this to me and, while I was not 100% certain, it certainly made more sense than it being a diacritic. My original blog post focused on the solid line above the "a" in "Ana" and the mention of the script over the "a" in "Catharina" was more parenthetical. In hindsight, I should not have been so quick to assume what it was.

Entries viewed in isolation are just begging to be misinterpreted. Handwriting should be viewed in the context of other records in the same series--hopefully in handwriting made by the same person.

To follow up on premise that the wiggle above the "a" was not a diacritic, I looked at other renderings of an uppercase C by the same minister. The top five entries are from the same page in the baptismal register as the entry of initial interest. They all have the same marking over the vowel following the initial C.

Three entries on the following page convinced me that the marking was not a diacritic--it's also over the "L" in Clara, and the "h" in Christine and Charlotte. The same diacritic would not be over teh consonants as well. Looking at samples of uppercase "C" as shown in the image from Ernest Thode's German-English Genealogical Dictionary, made it a little more clear that there could be a "hook" on the upper right hand portion of an uppercase "C." 

Pastor's "C"'s don't look exactly like those in the illustration from Thode's book, but then again few pastors write the way they were taught in school. Record clerks are not much better. Interpreting handwriting is more an art than a science.

And it takes practice.

And sometimes one has to admit that there can be some wiggle room in an interpretation.

Thanks to reader Nancy P. for gently pointing this out to me and getting me in the right direction. And thanks to Ernest Thode for graciously allowing me to use this image from his German-English Genealogical Dictionary. I've got a copy of Thode's book myself.





Blog Update and Genealogy Event Email

Periodically I send out updates on old blog posts, upcoming genealogical events, and a summary of what's been going on with my other blogs. If you'd like to get on that list--which is separate from this one--visit this page. Emails are not shared and you can unsubscribe at any time.

A. Trautvetter in the Oregon Vehicle Registrations 1911-1946

Ancestry.com recently released a database of Oregon vehicle registrations from 1911-1946 on their website.

The database is indexed and links to color scans of the pages. The registrations appear to have been printed on an ongoing basis and organized numerically within each volume.

The entry shown in this image comes from April of 1919 and is for "A. Trautfether."

A. apparently resided at 48 N. Orange in Medford, Oregon--in Jackson County. He had a Packard with motor number 48193, it was a 1914 model, 2-ton truck  ("tk 2 tn").

Users of this database are encouraged to read the prefatory materials accompanying each volume.

Part of that prefatory material is included as a part of this blog post.

An interesting database for those with Oregon connections. Individuals who do not appear in city directories may appear in this listing and it may be possible to track their changes in residence using this database.

It can be searched here for those with an Ancestry.com  subscription.

Now to find out who A. Trautfether is--which reminds me that names can get spelled a variety of ways.






11 May 2015

Seeing if Mom's Recent Obituary is in GenealogyBank


I don't know how quickly GenealogyBank updates their database of current obituaries on their site. It must be fairly regularly.

A search today on GenealogyBank's Obituaries page brought up two results for my mother's obituary. One with a publication date of 29 April and another on 22 April 2015. I'm not certain how long the obituary has been in GenealogyBank's  Obituaries database as I today was the first day I performed a search for her obituary online--more out of curiosity than anything else.

The obits that come up when the hits are viewed, do not contain any pictures. Users of GenealogyBank's Obituaries may wish to see if the original newspaper obituary is online in order to determine if a picture was also published. Googling the name of the newspaper is a great way to find out if it available online.

Of course, the GenealogyBank's Obituaries database does not search every obituary published.


The Neighbors Are Not Always On the Next Page

In June of 1892, Christ Troutfetter received a patent for 160 acres in Thomas County, Kansas.

In an attempt to ferret out neighbors who may have filed homestead claims near Troutfetter, I decided to search for his parcel in the tract books from the Bureau of Land Management. The patent gave me the legal description which is necessary to search the unindexed books. I've worked with land records long enough to know that section 5 is close to the border--the township border. Fully searching for Troutfetter's neighbors will require that I search not only the tract book for several sections in the same township as his homestead, but three nearby townships as well. 

Troutfetter had neighbors less than two miles away living in potentially four townships as shown on the illustration

I will need to search part of the tract books for parts of:

  • township 7 S 33 W--the township in which Troutfetter's patent is located
  • township 6 S 33 W--the township to the north
  • township 6 S 34 W-the township to the northwest
  • township 7 S 33 W-the township to the west

Searching the book for Troutfetter's entry and then going a "few pages before and a few pages after" won't be sufficient to get at all his potential neighbors. I'll have to have my section maps handy to make certain that I'm actually getting the pages for the townships and sections within those townships that are closest to Troutfetter's claim.

It's not always about just turning the page.

---------------------------
Note: A blog post linking to the FamilySearch image of these tracts books can be found here. We'll have an update later on Troutfetter's entry in the BLM tract book.


Am I Down On the ELCA Records?

I've never been a fan of "reviews" that were nothing more than cursory glances at the material or were merely rephrasings of promotional items sent to potential "reviewers." Discussions of that type do the reader a disservice and often only serve as veiled advertisements. The same goes for reviews of genealogical databases, software and the like.

It may seem that I'm "down" on the "Evangelical Lutheran Church of America, Records, 1875-1940"  at Ancestry.com. The reality is that I am not--not by a long shot. We've featured some really interesting finds in these records--because there are some wonderful discoveries to be made. However, there are some limitations. I want readers of this blog to be aware of them. Informed users are better users. There are wonderful gems hidden in those records and I've tried to share with readers some ways to get at the best of what those records have to offer.

I write about what I use, generally as I'm using it. I've never been a big fan of superficial blog posts written about items merely to generate web traffic.

One reason I'm writing about them so much is that I'm using them regularly now that Ancestry.com has posted them--and that I have "discovered" them. It's also one of the first Ancestry.com  databases that includes significant information on my Ostfriesen immigrant ancestors in the United States--and that's one-half of my ancestry. Sometimes I write about things as soon as they are released and other times it takes me a long time to get around to using something. I don't always run out and search the newest database the moment it is released just so I can be the first to write about it.

Many concerns are general 


The concerns that have been noticed on this database are not limited to this database specifically and not limited to just Ancestry.com. With every post about these records, I try and make general points about researching online regardless of the database. Those warnings are not limited to the "Evangelical Lutheran Church of America, Records, 1875-1940." These concerns and pitfalls are ones that researchers should be aware of regardless of what database is being queried.






10 May 2015

When Is It a Diacritic and When Is It Shorthand?

It never dawned on me to think of it as a tilde. That's probably because I knew what it meant and seeing no wiggle in the mark above the "n" told me there was no wiggle room in how that line should be interpreted. 

The pastor who made out the 1887 christening entry in the Christ Lutheran Church in Gothenburg, Nebraska, used shorthand when writing her first name. The line above the "n" in her first name indicates that the letter is actually to be written twice. The pastor used the convention elsewhere as well. The pastor used the same notation on her father's name in the same entry to avoid repeating the letter "m." The name was Tamme Tammen, not Tame Tamen.

It is interesting to see how these names were transcribed in the at "Evangelical Lutheran Church of America, Records, 1875-1940" Ancestry.com.


There is the same notation in the name of the christening entry 100--Oltmann Ulfers. The Ancestry.com transcription does not indicate any tilde over the final "n" in Oltman's name, while there is one in Anna's. My suspicion is that this is likely because tildes are not often used at the end of any word. The tildes are not used in the transcription of Tamme Tammen's name. This may be because tildes are not usually used with the letter "m."

The interpretation of the line above the letter is inconsistent and it's pretty clear that the same symbol is being used in "Oltmann," "Anna," and "Tamme Tammen."

The diacritic did get transcribed over the letter "a" in Catharina. [Turns out this is not a diacritic. See our followup post.] 

Learning various writing conventions and shorthand takes time. Understanding these conventions also requires some knowledge of local names so that these conventions can be interpreted correctly. I can't overemphasize the importance of becoming familiar with the records being used and manually searching those records--even when indexes are available.

Have you thought about dropping the second double letter in a name when querying a database? Did the creator of the record you are using an index for use a notation that a transcriber handled incorrectly? These sorts of issues are not only encountered with church records written in the German script.

Note: Screen shorts of Ancestry.com screens are current as of the date this post is published. 

Do You Make Certain the Digital Images are Complete? Christ Lutheran Church in Gothenburg at Ancestry.com

[all discussion is current as of 9 May 2015]

I easily found the 1882 christening for Tjode Anna Goldenstein in Gothenburg, Nebraska's Christ Lutheran Church by searching for her name in the index to "Evangelical Lutheran Church of America, Records, 1875-1940" at Ancestry.com. It was easy.

To streamline my search for her younger Nebraska-born brothers, I decided to expand my search of the database to include all Goldensteins in Nebraska. After all, there should not be too many Goldensteins in the database with an event in Gothenburg, Nebraska.

There weren't many. 

There was only Tjode. 

And that was strange. It was strange because four of Tjode's younger brothers were born in Dawson County, Nebraska. In fact, years ago I wrote the church directly and obtained a transcription of their baptismal entry. So I knew they were there. 

Because the church was small it was decided to manually search the records. I started with the entries for 1882 which started on page 29 of the baptismal register. That's the place to start as Tjode was the oldest child in the family. Page 29 is Ancestry.com's image number 15 in the digital images from Christ Lutheran Church.


When I moved to image 16 I realized why I could not find the entries for the other children in the database. There were gaps in the baptismal entries. Image 16 contained page 36 of the baptismal register and contained entries beginning in April of 1887. Image 15--which contained page 29 of the register contained images through early December of 1882.


There is a gap in the records as displayed on Ancestry.com. At this point, I'm not certain if that gap is from:
  • a gap in the original records--were pages gone from the register when it was filmed?
  • records that simply were not filmed--Ancestry.com did not microfilm these records. 
  • an digitization error on the part of Ancestry.com
As this point, I'm inclined to not believe there is a gap in the records The records were microfilmed in 1984 by the American Lutheran Church (according to the title sheet in the image set for Christ Lutheran Church which does not indicate any gap in coverage). The American Lutheran Church was a forerunner of the ELCA (Evangelical Lutheran Church in America). It is possible that there was some irregularity with the filming. The records were still extant in 1986 when I wrote to the church requesting information from the baptismal records. 

We'll see if we can get to the bottom of this missing baptismal record mystery.

The general lesson here is to search manually when necessary and check for the completeness of the records. One cannot find what is not there.

Stay tuned. We'll post an update when we've got one.

Ken and Martha: A Lesson in Data Preservation

[I originally wrote this nearly fifteen years ago. Consequently some of it is a little dated...however, there is some food for thought here. It last ran on the blog a few years ago.]

Ken and Martha: A Lesson in Data Preservation


It's 1968. Two genealogists are madly obtaining and compiling family history information. Ken is converting all his data to punch cards. "State-of-the-art" he says. Locals at the genealogical society brag about how "modern" Ken is. He's been asked to discuss his technique with several groups. Martha insists on using her old manual, "it worked for Donald Lines Jacobus," she states, ignoring the blank stare she gets in return. Ken jokes, "why Martha, you probably don't have running water." Martha calmly replies "I most certainly do…packing water from the creek would take away from time at the courthouse."

Martha uses good paper and good ribbons, but that doesn't matter to the others. "Living back in the '30s," they say. Martha remembers using court documents from the 1890s and the ease with which sixty years later she read the judge's typewritten conclusions. She smiles to herself and carries on. After all, her research has shown she's descended from a stubborn, independent lot and a little ribbing won't sway Martha.

It's 1998. Ken and Martha have been gone for years, the society members who lauded Ken and ribbed Martha are mostly gone, current members are largely unaware the two former members. Ken's heirs and Martha's too have found their genealogical compilations in their respective attics and have wisely donated them to the local genealogical society. The acquisitions chairman quickly appoints someone to inventory and catalog Martha's typewritten charts, forms, and histories before they are added to the society's collection.


The society is still trying to find someone to do the same with Ken's cards. The comment "why don't we sell them as bookmarks at our annual workshop" is initially laughed at but does generate some serious interest. Pictures are also a part of Ken and Martha's collection. Martha's black and whites have stood the test of time rather well. Some of the original stones are gone, but Martha's pictures remain and will be archivally preserved by the society. Ken's color photographs have faded and they, in addition to his punch cards, are still awaiting a decision.


While the "old way" of doing things is not necessarily the best way (I'm partial to running water and electricity myself), Ken and Martha's story makes a point about the use of technology. The blond hair in the photograph of me at three years of age has faded. Today the photo makes me look as if I've always had a receding hairline. I have a stack of 5 1/4" floppies sitting on my desk, gathering dust. They all contain state-of-the-art software, and corresponding data files. The only computer I have that reads 5 1/4" floppies sits in my garage. With a null-modem I could transfer the files to the machine I currently use. That works today and the machine in the garage is thirteen years old. What about fifty years from now? If I had my "complete" genealogy on one of these disks could it be read and used in fifty years? What if the data is readable, but the software won't run? Will someone have a working copy of the software?


If not, will there be any way to convert the data to a modern format? Even if they had a machine that could read the disks, what is the chance a machine of that age is in working order in fifty years? And what if it needs parts? It took the auto-body shop two weeks to find parts for my five-year old car. Obtaining parts for a fifty-year old computer is likely to be even more problematic. That does not matter, the technical ones say. There will be ways to convert any data format to any other data format at that point in time. Maybe, but maybe not.


If you take a look at 30-year old genealogical magazines, there are ads for various specialized record-keeping systems, with special charts, forms, and numbering schemes. For how many of these can you still buy forms? Heaven help you if Great-aunt Myrtle used one of these systems and misplaced the manual. And in the ever-changing world of technology, whose to say which data format or operating system will eventually win out? Ten years ago we lived in the world of MS-DOS and every computer user (except for Mac people!) had to enter in text commands in order to maneuver data and software files. Ten years ago, all genealogy software was written for DOS and windows had curtains. If Sun and others have their way, it will be curtains for Windows. Regardless of who comes out on top, change is the only thing that never changes.


In the rush to computerize and to digitize, it must be remembered that relatively speaking, these technologies are in their infancy and that file formats are still constantly changing. It's also necessary to remember that computers and digital technologies originated as a means of communicating and processing information faster, not as a way to preserve information for hundreds of years. Electronic forms of publishing and data storage should not be abandoned. The days of paper and printing are not yet over. Remember the phrase "paperless office?" From what I see as I look at the clutter surrounding my desk, I realize we have a long way to go. In fact, computers make it easier to generate reports and forms.


Computers were never meant to be archival, they were a means to process information more quickly (at least in theory). And when a computer geek says they "archived" something they aren't storing if forever. They made a backup copy in case their hard drive fails in the next few years. They are not planning on saving a copy for the next hundred years. The school where I work occasionally receives donations of old software. Software for Windows 3.1 is essentially useless, especially if we are preparing students for technologies they will encounter in the workplace. When my office was moved from one building to another, I threw out countless old software manuals and programs. We are not a software archives and there's no practical reason to retain five and six year old software.


It's important to remember that a significant amount of the fascination with this new technology is hype. It's important to remember the word "hype" is related to the word "hyper." A hyper person is usually too excited to be unable to focus and concentrate. Also remember that software and hardware companies benefit from new products being put on the market every six months and that "new" is not a synonym for "better" (my word processor confirmed this, just in case I was not aware of it myself). It should also be remembered that recent trends have made genealogists more of a market than they were five or so years ago.


Make no mistake. Information technology affords genealogists opportunities never before available. Significant amounts of data are available via computer and communication can be greatly facilitated. In fact, the editor of this e-zine and I have never met, never talked on the phone, never faxed, and never U.S. mailed. Also, on my end nearly half the articles never see a sheet of paper until the completed e-zine is e-mailed to me when it is "published." Let's also remember that the greatest information processor of all time is not archival. The human mind still has advantages over the computer. If we are really lucky, it lasts one hundred years and no one ever claims the brain should be used for long-term data storage. After all, I have enough trouble remembering where I put my keys fifteen minutes ago. Printed, typed, or written pages, once transcribed by a human, may last for much longer if preserved correctly. As we research, compile, and create, let's not forget the lesson of Ken and Martha.

09 May 2015

An 1884 Witness: What It Means and What It Does Not

On the list of things I wished they had indexed in the "Evangelical Lutheran Church of America, Records, 1875-1940" at Ancestry.com are the witnesses. This 1884 marriage reference makes the case pretty clearly.

Being a witness to a marriage is not proof of a biological connection between the witness and the marrying party, but the notation that someone is a witness is evidence that there was at least some connection between the couple getting married and the witness.

This 1884 marriage entry from Christ Lutheran Church in Gothenburg, Nebraska, indicates that Tamme Tammen and Eke Borcherts were married on 29 March 1884. Two of the witnesses were Fokke Goldenstein and his wife.

Focke Goldenstein is known to have had a nephew Tamme Focken Tamme born in May of 1856 in Velde, Ostfriesland, Germany.

Does this mean that this Tamme Tammen is the same one who was the nephew of Fokke Goldenstein? No. After all, no where on the record does it state that Tamme is Focke's nephew? It does not--and researchers need to be constantly cognizant in terms of what a record states and what it does not state.

But, Tamme Tammen on the marriage record has an age consistent with a date of birth in May of 1856, when Fokke's nephew was born and the presence of Fokke Goldenstein as a witness does indicate that the two men knew likely each other.

Of course it doesn't hurt that the names are not all that common either-that helps in this case.

In some cases, witnesses to a marriage were other "warm bodies" who were hanging around the marriage location. In this case, that does not appear to have been the case.

Note: This image was obtained in the "Evangelical Lutheran Church of America, Records, 1875-1940" database on the Ancestry.com site. As of this writing the names of witnesses to marriages are not a part of the index. My advice is to manually view the church registers to see if you person of interest appeared as a witness to any marriage within the church. The names of the groom and bride could be pivotal to your research.  This marriage reference was located by searching for references to Tammens in the "Evangelical Lutheran Church of America, Records, 1875-1940" in Nebraska.

A Card From 1967 Brings Connections in 2015

I've written about my relatives enough that blogging as "cousin bait" is something I don't do intentionally.


However, those who have never written a blog post in hopes of catching a cousin or making a connection might want to consider doing it.

A recent post to Genealogy Tip of the Day mentioned a card my parents received from an Ola Howes when they married. I didn't give much thought to the tip after I wrote it--after all there's always another day looming for which a tip needs to be written and I only wrote the tip because I needed a tip and for some reason the memory of the card popped into my head.

A day later a reader graciously sent me a digital image of a picture of Ola and her husband. The reader is a relative of Ola's husband, John Howes.

Regular readers know that I only write about my children's ancestors. That's enough to keep my occupied for the duration of my time on this planet and generally allows me to write about a wide variety of material (the curious can view an incomplete copy of my ancestor table here).

If you've not considered blogging, I'd suggest it. Don't consider it as a way to permanently preserve your genealogy, but rather as a way to share and connect with others who may be researching the same families--or the same general geographic area. I've gotten good information and leads from researchers with whom I shared a geographic connection and not a biological one. And as a last warning, not every one who reads your blog or "uses" information you post will contact you and some may "use" your information without asking.

Thanks to the reader who sent me the photo--I don't post names publicly on this blog and I forgot to ask her if she  minded me posting her name, so I didn't. She and I had a further email discussion and we have other "relatives of mine who married relatives of hers," which often happens in rural areas.

Ola's grandmother was Barbara (Siefert) Bieger Fennan Haase Haase (about 1825 Germany-1903 Warsaw, Hancock County, Illinois). There was something of a falling out when her estate was settled, but that's a story for another day.



08 May 2015

In Hastings Nebraska They Have a Flock of Geese...Not Sheep

As my work colleague from west Texas used to say "Good Honk!"

I was browsing the on Ancestry.com to see if they had records for any Lutheran churches in Hastings, Nebraska.

They do.

For the Goos Shepherd Lutheran Church.

It's an obvious typographical error in the name of the church, but it makes a good point about citations of information we find in online databases.
It's "Goos" on the drop down list of churches in Hastings, but it's pretty clear from the microfilm that the name of the church is Good Shepherd Lutheran Church. And that's what I suspected the name actually was the minute I saw it.



If I were to use any of these digital images at Ancestry.com of ELCA records in my own genealogical database, my citation should comment that Ancestry.com has named the church in the database as the "Goos[sic] Shepherd Lutheran Church." I should comment in my notes what the correct name is. I should not use that name for the church when entering information into my genealogical records--for that I should use Good Shepherd Lutheran Church as that's the actual name of the church.

I have an inkling that Ancestry.com will change the name of the database upon learning of the error.

So if I make any discoveries in the records for the Good Shepherd Lutheran Church in Hastings, Nebraska, I'll wait until the name of the church has been corrected.

If you've not browsed the "Evangelical Lutheran Church of America, Records, 1875-1940," do so. They are an excellent set of records. Even if there is the occasional goose lurking around.

Note: All images were taken at approximately 4:45 central time 8 May 2015. Except for the image of the goose. That was taken around 9:00 am central time 8 May 2015. I had no idea it was going to be an illustration for a blog post.

A Seventy Year Old Child Lives on the Hard Road

This post started out about an Ancestry.com transcription error and morphed into one about highway numbers. Genealogy is like that sometimes.

The transcriptionist for the 1940 census at Ancestry.com indicated that 70-year-old Edward Heidbreeder[sic] is listed as a son in the household.

That sounded a little off to me, but it was possible that he was living with a parent who was still living in their nineties.

Turns out he wasn't.

He is listed in the enumeration as a father-in-law of the head of household, Walter F. Bode.

The transcriptionist most likely grabbed the "daughter" relationship from the previous entry and assigned it to Edward.

The Bodes were farmers in Marion County and the street address seemed a little unusual. Virtually all my relatively close relatives in 1940 were farmers in rural Illinois and Missouri and I don't think I've ever seen a street address listed for any of them.

Reading the actual entry again answered the question. Their "street" was not "W S 36" it was "U S 36." And I'm reasonably certain locals didn't refer to it as a "street," but it's easy to see how transcribers would enter it in as the street on which the family lived. I'm also pretty certain they didn't have house numbers either.

The immediate lesson here is the one we've mentioned before:
look at the original

Personally now I 'm curious.

My paternal grandparents were living in a farm on the "hard road" in 1940 (State Highway 94) north of Carthage. My maternal grandmother was living in 1940 with her parents on the "hard road" west of Carthage (US Highway 136). I'll have to see if their 1940 census enumerations make any reference to the highways.

Census takers may have had some discretion about using highways when there were no house numbers. The answer to whether or not they were to use the names/numbers of roads when there were no house numbers would probably be answered in the enumerator's instructions.



He's A Murphy...But Which One?

This was posted to the group page I have for Genealogy Tip of the Day on Facebook and it generated some discussion about how the first name could be reasonably interpreted. Our discussion was somewhat hypothetical as other handwriting on the page was not viewed. This was done intentionally as many indexes are created in just this way. The researcher who fails to acknowledge how some indexes are actually created are sometimes limited in their ability to utilize those indexes effectively.

It was fairly clear to me that the intended name here was "Danl"--- for Daniel. In looking at it myself, I could see how someone might think is was Saul.

Readers mentioned that it's also possible to interpret it as "Saml" or "Darel" It's difficult to seriously argue against Saml in this case if one has already indicated Saul is a reasonable interpretation. I would not have rendered it as "Darel," but it's easy to see that as well. No doubt there are other reasonable renderings of the name.

Handwriting is always best interpreted in context and when compared to other handwriting on the same page or document. However, even when other handwriting is available it's often easy to justify more than one interpretation. And sometimes, especially when analyzing signatures on original documents, other handwriting is not available for comparison.

It's also easy to get stuck in an original interpretation of something and to occasionally fail to realize that there may be another equally valid way to view a piece or handwriting or a piece of information.

And if this Murphy man had brothers named Saul and Samuel--then that's a whole 'nuther problem.




FamilySearch Update: MO Deaths, MN Births, Salt Lake City Cemetery, and UT Obits

The following databases are showing as new or updated on FamilySearch:

Utah, Salt Lake City Cemetery Records, 1847-1976

Utah, Obituaries from Utah Newspapers, 1850-2005

Minnesota, County Birth Records, 1863-1983

Missouri, Deaths, 1835-1976

Note: The Missouri deaths on FamilySearch  are county records--which start earlier than the state records which are online for 1910-1964.

07 May 2015

August 2015 Allen County Library Research Trip


Any questions about registering? Email Michael at mjnrootdig@gmail.com

Join Michael John Neill for 3 days of research at the Allen County Public Library in Ft. Wayne, Indiana--one of the largest genealogical collections in the United States.

Registration open!

Trip includes:


  • assistance with pre-trip planning. Participants are encouraged to submit at least one (and no more than three) personal problems to Michael for assistance and suggestions before the trip
  • Morning lectures on intermediate topics.
  • On site consultation with Michael during library time. Each participant gets one 20 minute consultation with Michael on a specific research problem. There may be additional sessions if time allows. Michael will also be available for shorter, on-the-fly suggestions as well.
  • Handout. Lecture material, general information, and no more than two pages of research problem per participant will be included in the trip handout.

Days:

  • 10 August-no presentation, but I will arrive in the afternoon and we can schedule consultations in the afternoon as time allows.
  • 11 August- presentation in library at 9:00 am--until 10 am. Library research time and consultations with Michael (scheduled) until library closes at 9 pm.
  • 12 August- presentation in library at 9:00 am.--until 10 am. Library research time and consultations with Michael (scheduled) until library closes at 9 pm. 
  • 13 August- presentation in library at 9:00 am.--until 10 am. Library research time and consultations with Michael (scheduled) until library closes at 9 pm.


Registration is limited and is on a first come, first served basis.



Lodging and Travel:

Participants are responsible for their own travel, lodging, and other expenses. There's no hotel you are forced to use and we don't have a long list of "group" activities that you are paying for as a part of the "package." We are all about the research. Our approach is informal, laid-back, and focused on helping you make the most of your time at the library. We will have optional group dinners on Friday and Saturday for those who are interested. Participants can stay at hotels in the downtown Ft. Wayne area or in less expensive lodging further from the downtown area

About Michael:



Michael has researched his own ancestors and those of his children for over thirty years. He has lectured on genealogical topics to groups across the United States and has lead research trips to the Allen County Public Library and the Family History Library in Salt Lake City for fifteen years.

A Personal FindAGrave Suggestion

FindAGrave memorials for immediate family members can be a sensitive area.

There are people, some with good intentions, who create memorials for deceased people upon seeing their obituary or death notice in the newspaper. They've never been to the cemetery to take a picture of their stone (which may or may not even be erected by the time the person dies) and they create a memorial page for that person based upon the information in the obituary.

This post isn't about whether obituaries are correct and can contain errors or whether the practice of posting memorials before the burial should be allowed. I don't edit or proofread every obituary published and I don't run FindAGrave.

Sometimes the creators of these memorials readily transfer them to immediate family members in a very gracious fashion and sometimes they don't. I also do not control the creators of those memorials nor do I control the transfer process.

That's not what this post is about.

This post is about the early bird getting the worm and about how different people handle grief differently. And it's okay to handle grief differently and it's okay to not use the approach to FindAGrave that I did.

I created a FindAGrave memorial for my mother within hours of her passing. Yes, within hours. In fact, it was what I did shortly after I made the phone calls to necessary relatives. Some may find creating the memorial the day she died morbid. I didn't. I found it somewhat therapeutic as it was a way of telling people she had passed without having to express it verbally. Sometimes that is easier.

When initially creating the memorial, I only entered in the date and place of her birth and death and the location of her burial. Just enough to "create" it. The funeral date had not been set and her obituary had not yet been written. Of course she hadn't even been buried yet, but we knew where that was going to be. I left the rest of the memorial blank, largely because I wasn't quite ready to write that part of it.

So here's a suggestion for those who have family members who may pass.

I realize that creating a FindAGrave memorial the day a relative passes is not something everyone can do. That's ok.

But the early bird does get the worm.

If you are concerned that "someone else" may create a memorial for your family member, consider this:
Find a genealogical friend or relative that you trust and ask them to create a FindAGrave memorial for you when your relative dies. That friend or relative can transfer the memorial to you when you are ready. At that point you can add to it or change or modify information as necessary. All you'll have to do to get it started is to let the friend or relative know when your loved one has passed. You may even offer to do the same service for your friend

You'll just have to tell the person about the passing before death notices or other information has been posted online or in the newspaper.

Or, if you think you can do it...creating the memorial yourself is always an option.


Thanks!

Thanks to readers who sent notes to me in reference to my Mom's passing a few weeks ago. I have read them all, but haven't had time to respond individually as of yet.

Know that your thoughts and concern are greatly appreciated.

Why Can't We Browse on GenealogyBank?

I have made good discoveries on GenealogyBank. There are newspapers in their collection that other online sites do not have.

However.

It is not possible to easily "read" the issues at GenealogyBank one after the other online like can be done at many other sites. I can't browse and I don't like it.

To read the paper for a specific date, one has to:

  • start at the state list on GenealogyBank.
  • click on the state of interest
  • choose the newspaper of interest
  • enter a date in the search box:
    • a year range
    • a date range

Then use the search results to maneuver to the date of interest. The process has to be repeated for additional dates. 

I tried this with the "Idaho Statesmen" from Boise, Idaho. It took some experimentation with the dates to find something that GenealogyBank had for that paper in 1864. Apparently there was nothing for January through February of 1864. Note: leave the name blank when performing this search as dates are the only search term needed. 

Apparently there are no 1864 newspapers in this collection until July of 1864--and apparently 26 July at that.


Then I clicked on the first hit "Taxes Due" so that I could get to one "hit" in the 26 July 1864 issue.


Then I clicked on "List all pages in this issue" which altered my page to the following:

Then I could browse the other pages in that issue.

But there's no "link" to the next issue or the previous issue--I'll have to go through the same search process again.

And, I can't see an inventory or a listing of what issues are available for a given newspaper.

I use GenealogyBan and make discoveries there regularly, but the site's setup seems to encourage search only and not browse.

I like to browse and I like to read for myself.

I also like to know what extant issues have been put in digital form on a website.

-----------------------
Readers can enter the "newspaper portal" at GenealogyBank here.

1940 Era Fountain County, Indiana Marriage Record Provides Birth Place, Occupation, and Residence of Parents

This is a wonderful document from 6 July 1946 in Fountain County, Indiana: the marriage record of Bernard Henry Goldenstein and Lydia Leeora Nelson. 

Not only did it provide information on the bride and groom, but it provided the following information on their parents:
  • Name
  • Place of birth
  • Occupation
  • Residence

Bernard's father, Tonjes Goldenstein was my uncle. This application doesn't really provide any new information on Tonjes, but the potential was there. The information is not overly specific and is only as accurate as the knowledge of the provider, but still could be helpful.

And the residence of the parents could be helpful as well.

Always good to know that the bride and groom had not recently been in the county asylum or home for indigent persons.

And it just goes to show that searching for records on collateral relatives can be helpful.

Even if they drive all the way across the state of Illinois to get married in Indiana, which is apparently what this welder from Quincy, Illinois and his bride to be did.