You are here: Learn > The Library > Daily News Desk > Ancestry Daily News

Ancestry Daily News
11/20/2003 - Archive

•  Ancestry Daily News, 20 November 2003
•  1880 Online Strategies: Part II

Ancestry Daily News, 20 November 2003

In This Issue: November 20, 2003

New Records for Ancestry.com Subscribers

Databases Updated Today
Nashua and Hudson, New Hampshire City Directory, 1955 (Images online)

Historical Newspapers Collection Update
Deming Headlight (Deming, N.Mex.),
Various years ranging 1882-1979

U.K. and Ireland Records Collection Update
Boxford Churchwardens' Accounts, 1530-1561 (Images online)

  Today's Map: Millikens Bend to Vicksburg
  "1880 Online Strategies: Part II"
by Michael John Neill
  Ancestry Quick Tip
  Fast Fact: The Free Research Registry at Ancestry.com
  Clipping of the Day
 

Ancestry Product Specials
Finding Answers in U.S. Census Records,
by Loretto Dennis Szucs and Matthew Wright
1930 U.S. Federal Census Index: Arkansas South (Deluxe Edition)

Find Lost Family and Friends



Use the MyFamily.com People Finder to locate friends you have lost touch with.


People rarely succeed unless they have fun in what they are doing.

—Dale Carnegie

  Ancestry Quick Search: Advanced Search
                                      First Name            Last Name


"1880 Online Strategies: Part II"
by Michael John Neill

Last week's article discussed the free online 1880 census database available at both Ancestry.com and FamilySearch.com. While both sites search the same data at no charge, there are differences in how the search interfaces are constructed, and there are times where one search interface is more effective than another. This week we continue our discussion by looking for various individuals whose names are not all that easy to find.

Misspellings and Locational Stumbling Blocks
Last week's column ended with John Ufkes, enumerated as John Ulkus. Because of the way this last name was transcribed, Soundex and most searches based upon the last name were not effective. Another approach was necessary. In this case, I was reasonably certain of John's 1880 residence.

The FamilySearch interface to the 1880 census allows the user to choose a place of birth from one of the dropdown menus. Germany is one of the choices, but if I search for John with a birthplace of Germany, it will not locate him. In this case, John's place of birth was enumerated as "West Friesland." Natives of this area typically list a place of birth of Hanover, Prussia, or Germany. However, the place of birth listed for John is not in Germany, it is in the Netherlands.

John will only be located if the place of birth is left blank or is set to the Netherlands. One must be careful when searching the 1880 census transcriptions for those born in Germany. FamilySearch will search for multiple parts of the German empire if Germany is chosen as the place of birth from the drop down menu. Those unfamiliar with the locations used in the database are advised to look at the entire list and locate the area where the ancestor was born on both modern and contemporary maps.

Name Close, Residence Uncertain
The desired person in this case is Antje Albers, born in Ostfriesland, Germany, ca. 1811.

The problem with Antje was a common one: I had absolutely no idea where she was living in 1880. This immigrant was known to have lived in Illinois, Missouri, and New Mexico after her 1860s era immigration. People who "get around" are always more difficult to locate in census records and are one of the reasons national databases are so helpful.

Antje was located at FamilySearch by entering her name in as Antje Albers and choosing a year of birth of 1811, with an error of plus or minus five years. Several matches were found. Antje was located in Denver, Colorado, living with her son L.U. Albers.

Antje also could have been located in the Ancestry.com search interface for the 1880 census. In her case, the best search would have been to use wildcards on her first name (Ant*) and her place of birth (Ger*). The Ancestry.com search interface will search only for births in Germany if Germany is entered in the birthplace box. Since there are entries in the database with a place of birth of "Ger" this search term (Ger*) will catch both entries. However, a search at Ancestry.com for Ger* will not catch those entries that list a place of birth as Bavaria, Saxony, etc.

German locations may be entered in the database in one of many ways (typically dependent upon the census entry), including (but not limited to):

Bad
Baden
Bav
Bayern
Bavaria
Ger
Germany
Hanover
Hannover
Oldenbert
Pru
Prussia

This incomplete list is provided to give the reader an idea of the potential abbreviation and spelling considerations they may face. Census takers did not always follow instructions, so consistency in place names is not to be found in the 1880 census.

For German searching, it usually best to use FamilySearch and choose Germany as the birthplace. Just make certain that your ancestor would have put some German state as his place of birth and not Austria, Bohemia, the Netherlands, etc. instead.

Significant Last Name Problems
Joseph Desmarais should have been listed somewhere in Clinton County, New York. This is an individual where the surname presented significant database search problems. A search at FamilySearch with exact spelling off did not locate him, even though the known county of residence was included. A Soundex search for Joseph Desmarais at Ancestry.com was also unsuccessful. In this case, it was decided that the spelling of the surname was the likely problem.

What to do? In this case, I would use FamilySearch and take advantage of the ability to search based upon family structure. Joseph should have a wife and at least eight children in his household in 1880. Our approach will start with his wife.

Joseph's wife's name, Cesarine, was frequently Anglicized as Sarah. My initial strategy was to search the 1880 census database at FamilySearch for individuals named Sarah living in a household headed by a person named Joseph in Clinton County, New York. Knowing that Cesarine was born in Quebec, I entered Canada as the place of birth. No age or other information was included.

There were only four results, one of which was an entry for Sarah Demarrah. An analysis of the other family members in the household made it clear the correct family had been located. No last names were even used to conduct the search in this case.

Some General Comments
— For Soundex searching, use the Ancestry.com search interface.

— For wildcard searching, use the Ancestry.com search interface. Remember that the wildcard character, *, must be preceded by three letters.

— For household-based searching, use the FamilySearch interface. If other details are sufficiently known, it may be possible to locate the family without even entering the last name.

— For similar names searching, use the FamilySearch interface. Keep in mind that this search will not catch all similar names nor will it catch all Soundex equivalents as we saw in last week's column.

One Last Note
The wildcard feature of the Ancestry.com database is a very nice feature, particularly when the place of birth is relatively unusual. A trick I used at Ancestry.com was to enter only "Ostfriesland" as the place of birth. There were only fifty matches in the entire database—one of which was an uncle I had been unable to locate. This technique will not work with large geographic areas, but in some cases you just may ferret out someone you were trying to find.

Actual census images of entries discussed in this week's column can be viewed here.

Next week, we'll see an 1880 census enumeration that is slightly unusual in that the head of household is the wife. What makes this unusual is the fact that the husband is living and is also enumerated—as the last entry in the household!


Michael John Neill is the Course I Coordinator at the Genealogical Institute of Mid America (GIMA) held annually in Springfield, Illinois, and is also on the faculty of Carl Sandburg College in Galesburg, Illinois. Michael is the Web columnist for the FGS FORUM and is on the editorial board of the Illinois State Genealogical Society Quarterly. He conducts seminars and lectures on a wide variety of genealogical and computer topics and contributes to several genealogical publications, including Ancestry Magazine and Genealogical Computing. You can e-mail him at: mjnrootdig@myfamily.com or visit his website at: www.rootdig.com/, but he regrets that he is unable to assist with personal research.

Copyright 2003, MyFamily.com. All rights reserved.


ACCESS A PRINTER–FRIENDLY VERSION OF THIS ARTICLE, e–mail it to a friend, or submit your feedback on it.

Top

 


Ancestry Quick Tip

Ensure Gravestone Photo Success
When going to photograph gravestones, take a small hand trowel, a whisk broom, a mirror about six inches square, and a friend. Trowel away grass and debris covering the edges of the stone, and whisk away dirt in the engraving. Then have a friend use the mirror to reflect sunlight onto the headstone from an angle that makes the lettering stand out and shoot. Make sure to take photos from more than one position to ensure the best outcome.

If you don't have a friend to help, use a mirror that has a stand.

Good shooting,
Barb


Thanks to Barb for today's Quick Tip! If you have a tip you would like to share with researchers, you can send it to: ADNeditor@ancestry.com

Quick Tips may be reprinted, with credit to the submitter, in other Ancestry publications, so if you do not want your tip included in a publication other than the Ancestry Daily News and Ancestry Weekly Digest, please state so clearly in your message.

ACCESS A PRINTER–FRIENDLY VERSION OF THIS QUICK TIP, e–mail it to a friend, or submit your feedback on it.

Top

 


Fast Fact:

Ancestry.com's Free Research Registry

Search the Research Registry to find out who else is researching the same surname(s) that you are, and contact them via e-mail, OR create and modify your own Research Profile so that others researching your family tree can contact you! The Research Registry is a free service of Ancestry.com and can be accessed here.

Top

Search ADN Archives




Top


Clipping of the Day


From the
Grand Traverse Herald
(Traverse City, Mich.), 20 November 1863, page 3:

TERRIBLE CATASTROPHY IN CHICAGO.--THE RUSH STREET BRIDGE DESTROYED.

On Tuesday afternoon a frightful accident occurred in Chicago in the failing of the Rush Street Bridge erected over the Chicago river. At five o'clock, while the regular tender was peddling copperhead tickets, 100 head of cattle were driven on the bridge. At the same time a horse and buggy, a horse and wagon, and several gentlemen together with a young girls were [on?] the bridge.

A tag whistle two blocks above the bridge, the cattle crowded to the south end of it, and against the earnest remonstrances of the gentlemen, the feckless substitute of the tender swung the bridge from the abutment. In an instant the north end of the bridge was elevated 20 feet in the air, there was a snapping of iron, a cracking and crashing of timbers, a shriek of horror from the bystanders, and Rush street bridge breaking in two across the centre pier, fell into the river a total ruin. Affrighted and horror-stricken, the crowd on either side of the river, stood motionless for more than a minute; there was a rush of people from the streets and for a quarter of an hour there was a cry for boats, and a running hither and thither for planks, and a confusion which rendered useless all attempts to save those who when down with the bridge. At last a tug steamed up to the scene of the disaster, and rescued all except the girl. Their escape was almost miraculous. One gentleman caught hold of the horns of a large steer, as did also the drover, and alternately floated and sunk until the tug came up. A few moments more and they would have drowned. A teamster and sub-tenders caught some planks and floated to the tug. The girl had not been seen nor heard of at nine o'clock in the evening at which time her brother had given her up as lost. About two-thirds of the cattle were either drowned or crushed to death among the timbers.

Rush street bridge was erected in 1859 at a cost to the city of $30,000, and at a severe loss to the builders. It was considered one of the staunchest and strongest of all the bridges in Chicago. But a structure of ten times its strength would have broken down under the circumstances which destroyed it. At the increased price of iron and labor the bridge cannot be replaced by a new one at a less cost than $50,000. Of course the city will be obliged to indemnify the losses of the owners of the horses and cattle.

Note: For more on the collapse of the Rush Street bridge, see the following:

Deaths, Disturbances, Disasters and Disorders in Chicago: 1863, November 3: Rush Street Bridge Collapse (Chicago Public Library)


Subscribers with access to the Historical Newspapers Collection can view this entire clipping.

Subscribe to the Historical Newspapers Collection
at Ancestry.com.

 Top



Ancestry Product Specials


Finding Answers in U.S. Census Records,
by Loretto Dennis Szucs and Matthew Wright



Normally Finding Answers in U.S. Census Records retails for $16.95, but today you can buy it in The Shops@Ancestry.com for $13.95.


 


1930 U.S. Federal Census Index: Arkansas South (Deluxe Edition)



Normally this CD retails for $49.95, but today you can buy it in The Shops@Ancestry.com
for $39.95.

Top



 

 


  Printer Friendly
 
E-mail to a friend

Search The Library



Weekly Journal

Sign up for the Ancestry Weekly Discovery and get free family history tips, news and updates in your inbox.