The News
Dedicated to Austrian-Hungarian Burgenland Family History


THE BURGENLAND BUNCH NEWS - No. 297
May 31, 2019, © 2019 by The Burgenland Bunch
All rights reserved. Permission to copy excerpts granted if credit is provided.

Editor: Thomas Steichen (email: tj.steichen@comcast.net)

BB Home Page: the-burgenland-bunch.org
BB Newsletter Archives: BB Newsletter
BB Facebook Page: TheBurgenlandBunchOFFICIAL

Our 23rd year. The Burgenland Bunch Newsletter is issued monthly online.
The BB was founded in 1997 by Gerald Berghold, who died in August 2008.

Current Status Of The BB:
* Members: 2860 * Surname Entries: 8743 * Query Board Entries: 5771 * Staff Members: 15


This newsletter concerns:

1) THE PRESIDENT'S CORNER

2) THE BURG MAN OF OMSK: TRACKING DOWN A BURGENLÄNDER ANCESTOR IN THE AUSTRO-HUNGARIAN ARMY (by William O’Driscoll)

3) CLUSTERING OF AUTOSOMAL DNA MATCHES (by Frank Paukowits)

4) DNA-BASED COUSINSHIP ESTIMATION - ANCESTRYDNA EDITION

5) HISTORICAL BB NEWSLETTER ARTICLES:
    - HIANZNMUSEUM IN RAABFIDISCH / RÁBAFÜZES

6) ETHNIC EVENTS

7) BURGENLAND EMIGRANT OBITUARIES (courtesy of Bob Strauch)



1) THE PRESIDENT'S CORNER (by Tom Steichen)

Tom SteichenThis month's collection of bits and pieces in Article 1, starts us off with a droll quote from a book, informs you of a new transcription of vital records, points out a couple more edits to our FS Films section, reports on a massive project that BB Surnames and Villages Editor David Hofer and I undertook over the last two months, passes along a link to an interesting article about goulash, shares the monthly BB Facebook report, and terminates with our standard ending bits and pieces (book sales, recipe, cartoon).

Article 2 is an amended version of a story William O’Driscoll first published in his local newspaper. It tells the tale of a man who he calls The Burg Man of Omsk: Tracking Down a Burgenländer Ancestor in the Austro-Hungarian Army. It is both an interesting story and an excellent source of information about researching WW-I Burgenland soldiers. Thanks, Bill!

Article 3 is by Frank Paukowits, who presents for us a new DNA tool that was recently released by MyHeritage called “AutoClusters.” Much as its name indicates, it is a tool for automatic Clustering of Autosomal DNA Matches.

Article 4 is a follow-up to an article I published last May about DNA-Based Cousinship Estimation. That article looked at FamilyTreeDNA's ability to accurately predict the relationship level of my known cousins who had tested on their service. This new article does similarly for the AncestryDNA testing service... but it has its own twists! I call it the AncestryDNA Edition of the article.

The remaining articles are our standard sections: Historical Newsletter Articles (this month providing the origins of two BB features), and the Ethnic Events and Emigrant Obituaries sections.



For all you Grandparents in the BB
(yes, I'm one of them):

The following quote made me chuckle gently (it is spoken by the narrator of a book about his fictional ex-partner and wife):

"Thanks to their daughter, Ellen, they were grandparents, and were enjoying all the benefits of a small child's company without most of the drawbacks."

                       - from the novel, The Woman in the Woods, by John Connolly, 2018



Vital Records Transcription: BB Member Margaret Roosdahl has contributed her latest transcription set, all 5,810 Catholic birth records, 1,131 Catholic marriage records and 4,644 Catholic death records for the Sankt Nikolaus (Szent Miklós) parish for the 1828 to 1895 period. Margaret previously contributed a similar transcriptions for the Sankt Michael (Pusta Szent Mihály) parish.

We have implemented her Sankt Nikolaus transcriptions in sortable table format, which you can find (directly) here: ChurchRecords/SanktNikolaus/SanktNikolausRecords.htm. Alternatively, you can start on the BB homepage and scroll down to the “Vital Records Transcriptions” section, then follow the appropriate links to her work.

On behalf of all of us, I thank Margaret for sharing her work; it is appreciated!



Correction (again): Our "FamilySearch (LDS) Microfilms and Digital Collections" section continues to be refined as we find needed additions or edits... and this is the third month in a row that I have a correction to report...

In this case, we discovered that the Catholic parish for Tobaj changed during 1874. We had the parish listed as Deutsch Tschantschendorf for the full 1828 to 1895 period, but that proved to be wrong. Roughly mid-year 1874, recording of Tobaj vital events moved to the Güssing parish. This was discovered while searching for an 1874 baptism of a person known to have been born in Tobaj... yet the FamilySearch index service listed Güssing parish for her baptism. A closer look at both the Deutsch Tschantschendorf and Güssing records revealed the recording changeover. We have updated our listings to reflect this new knowledge.

Do keep in mind that there were quite a few changes made to church and civil recording locations over the years. While we strive to be accurate in our listings, some of the changes eluded us... but we will research and, if appropriate, edit our listings if you notify us of an apparent problem. We, and the BB membership, we thank you for helping improve accuracy!



Separate from the above, Richard Potetz provided some information concerning the location of early records for Alsószölnök (Unterzeming), Hungary. Alsószölnök is an oddity for a current-era Hungarian parish in that its earlier records [pre-1816] were in a village (Sankt Martin an der Raab) now in the Eisenstadt diocese. Most other current-era Burgenland border Hungarian parishes had their earliest records in a village still in Hungary, so their records were microfilmed and are available in digital form online. While we can't point to the actual records for Alsószölnök, we have added a note reporting their location, should someone wonder where those records are.



Members, Surnames and Villages Re-Synced: BB Surnames and Villages Editor, David Hofer, prompted a recent project to get all of our member-related pages back into sync. What that means is that any member mentioned on one of these pages is referred to similarly on each of the other pages, as appropriate, and all email-address errors are fixed.

I say "as appropriate" because we have a number of what we call "research only" members, who have a general interest in Burgenland but do not list surnames and villages, or have an interest in a particular village (so are listed there) but again list no surnames. People in the second category often offer to assist our members with research related to that village. We also have many "regular" members who list surnames but do not know the specific village where they were from, so can't list a village.

With over 2800 members listed in Members, over 8700 surnames listed in Surnames, and over 4700 entries in Villages, that was a lot of entries to get back in sync!

Before I explain more about why we needed to re-sync our pages, I'll tell you that the member count on our Members pages rose from 2755 to 2859 due to the re-sync project, an increase of 104, and the count of surnames on our Surnames pages rose from 8623 to 8739, an increase of 116. However, these higher counts do not represent a real increase in either category; rather they represent errors in our recording of the entries. All of these member names and surnames were already somewhere on our pages... it's just that not all of them were on every page they should have been on and therefore were not properly counted! While I don't have precise counts for Villages, entries for about 120 members were missing on those pages and now have been added in.

So what caused these discrepancies?

The BB has been recording member data for nearly 20 years. During this time we have had numerous page editors come and go, and even had a few times where we had to suspend entry because we did not have an editor for a page. Each of these editors had their own way of doing things, which sometimes led to non-matching entries between our pages. All of these editors (myself included) made errors, sometimes forgot to make entries, and/or sometimes chose not to enter the data for a potential new member (while the editors of the other pages did make the entry).

And some of you members contributed to the discrepancies by "joining" more than once but with sufficiently different information that not all editors recognized that you were already a member... so you were on our pages twice. Or you sent in changes with a variation of your name or email address that was sufficient different that we again had differing interpretations of who you were by our multiple editors.

Further, in our early days, Gerry Berghold received all member data via email and forwarded those emails to the actual page editors. Later, we went to forms and a system that turned your data into an email that was automatically sent to our editors. All of these emails were subject to being blocked by spam detectors or dropped due to network errors so some never made it to every editor. Thus some editors never had a chance to enter your data.

Lastly, over the years we have changed our requirements about the data that needed to be shared by you to become a member. Our various editors did not always agree that you met those requirements so some entered your data while others did not. Likewise, our rules about what to do when members canceled changed over the years; our various editors handled such situations differently too.

In reality, I was rather surprised at how few differences actually existed... and how much effort it took to fix everything! David and I worked on this project over a six-week period, not full time, of course, but we put in a lot of hours overall! I know I'm happy it is completed and I expect David is too. Regardless, it was a project that badly needed to be done and I thank David for pushing us into it.

When all was said and done, we discovered that, before this month's entries were added, we had 2,719 active members, 103 inactive members, and we carry data from 27 deceased members, for a total of 2,849 members on our pages. These members list 8,739 surnames, of which 532 belong to the 130 inactive or deceased members.

Unfortunately, there is a "related" project waiting to be done... we need to verify that all the email addresses we have listed for our members are valid. One "quick" check has already been done: a comparison of the addresses on our pages to those in our Newsletter notification mailing list. That comparison eliminated the need to further check over 1700 addresses ...but still leaves about 1100 that need validation. We'll get to that when we work up some more motivation!



Goulash Recipe: Member Bob Chapman sent a short message to me pointing out a nice article about goulash, be it the traditional Hungarian soup studded with meat that was favored by the Hungarian herdsmen that gave it its name (gulyás = herdsman) or the spicy meat stew known in its homeland as pörkölt or paprikás (depending on the use of sour cream).

Bob writes:

Tom: If you haven’t previously seen it, you might enjoy the goulash article by Felicity Cloake at the hyperlink below.

theguardian.com/.../how-to-cook-perfect-goulash-hungarian

Cordially, Bob Chapman

I did enjoy the article, Bob, and I expect our BB members will too, so I'm passing it along.



The Facebook Bunch (from Vanessa Sandhu):

Greetings, dear Burgenland Bunch family!

May has been a very busy month in our Facebook group. We had 63 new posts, which led to 1004 comments and 1054 reactionstagging a post with a 'like' (etc.) without commenting on itand we welcomed our 937th member!

Many FamilySearch record look-ups were completed. Our members shared many beautiful family photos and lots of photo translations were done. We discussed obtaining citizenship in Austria and Hungarysome members have completed this, while others have been considering starting the process. Several members are currently on trips to Burgenland, so we are anxiously awaiting their return. We are excited to see photos and hear all about their villages and family members!

Complements of member Werner Schoenfeldinger, we bring you the Burgenländisches Volksliedwerk song of the month: “Marica, Rožica,” a Croatian song about a girl named Mary, is sung by the students of the bilingual high school in Oberwart. Enjoy!
youtube.com/watch?v=ahk8qKgCNyA

As always, if you haven’t joined us on Facebook (at TheBurgenlandBunchOFFICIAL), please consider doing so. We are always willing to help!

Have a great day! Vanessa



Book coverUpdate for book "The Burgenländer Emigration to America": Here is this month's update on purchases of the English issue of the 3rd edition of Dr. Walter Dujmovits' book "Die Amerika-Wanderung Der Burgenländer."

Current total sales are 1416 copies, as interested people purchased 8 more books during this past month.

As always, the book remains available for online purchase at a list price of $7.41 (which is the production charge for the book, as we purposely choose not to make a profit so we can avoid dealing with the income tax consequences and so you can obtain the book at as low a cost as possible!), plus tax & shipping. See the BB homepage for a link to the information / ordering page and for information about current discounts (there is at least one discount on price or shipping available most of the time... if not, wait a few days and there will be one!).



Burgenland Recipes: This month's recipe is again from Allentown's St. Peter's Evangelical Lutheran Church, provided by Louise Fielding. I always wondered what these were called, and if I would ever find a recipe for them. They look like small dumplings, and Bende sells a product called Tarhonya Egg Drop Noodles, which look very similar to what I remember. My grandmother used to make these as one of two noodle options for chicken soup at Sunday dinner. The other option, of course, were the really thin, long noodles; my grandmother would make the dough, but my grandfather took great pride in how thin he could cut them, so he reserved that job for himself. A true chef!

EGG NOODLES (Gersten) (from St. Peter's Church)

Ingredients:
5 large eggs
5 cups flour (approx., depending on egg size)
1 tsp salt

Preparation:
Knead until a firm dough forms, then grate on a medium grater to form pea-size dough pieces. Have boiling water ready; add salt and the Gerstels. Boil for about 5 minutes, then drain.

Serving:
Add to chicken or beef broth for a filling soup.


[Editorial note: Gerste is the German word for barley, with Gersten being its plural. So I'd guess that Gerstels is "little barleys." Given the appearance of the final product, I can see how it received its name!]



Note: We again have a "regular" source for Burgenland recipes.

Nonetheless, if you have a favorite family recipe, please consider sharing it with us. Our older relatives, sadly, aren't with us forever, so don't allow your favorite ethnic dish to be lost to future generations.

You can send your recipe to BB Recipes Editor, Alan Varga. Thanks!



Cartoon of the Month:



2) THE BURG MAN OF OMSK: TRACKING DOWN A BURGENLÄNDER ANCESTOR IN THE AUSTRO-HUNGARIAN ARMY (by William O’Driscoll)

Family stories about my wife’s grandfather, Alois Muhr, were almost legendary. Born in Burg, Burgenland, on the present border between Austria and Hungary, Alois had fought in World War I on the Eastern Front. Alois was captured by the Russians and interned in a Siberian prison camp. While in the prison camp, Alois met a newly married man, Frank Tissinai, from the neighboring village of Dürnbach (Incéd), and they had become good friends. When Frank realized he was dying, Frank made Alois promise to return to Dürnbach and take care of his wife, Elizabeth. After some time in the prison camp, Alois was sent to a Siberian farm to work in place of the farmer, who had been called up by the Russian Army. Alois reportedly worked the farm for several years, and replaced the farmer in every sense of the word. Could there be Muhr relatives somewhere in western Russia? When World War I ended for Russia and the Russian Civil War commenced, Alois spent several years with the Whites, running from the Reds, and only was able to return to his home in Austria years after he left. In the final chapter of the family story, Alois followed Frank’s widow Elizabeth to America and married her in Chicago.

Wow!” I thought, when I heard these stories for the first time. “Can any of this be true?”

After much investigation, I have confirmed more than half of it and have disproved none of it.


Figure 1 Excerpt from Military Record of Alois Muhr – Name & Description

What follows is my reconstructed investigation into these stories.

Where to start was my first hurdle. Since Austria-Hungary had a history of military conscription, I decided to start with military records. I knew the date and location of Alois’ birth to be April 21, 1889, in the village of Burg. At the time, Burg lay in western Hungary and was called Pinkaóvár. Burg/Pinkaóvár was located near Felsöór (Oberwart) in the county of Vas, Hungary.

I soon learned that much of Austria’s military records were intact and held in the Österreichisches Staatsarchiv Kriegsarchiv (Austrian State Archive, War Archive) in Vienna (the address I used was Kriegsarchiv, Nottendorfergasse 2-4, A-1030 Wien, Austria). But Muhr is a common name, and Alois, the English counterpart of Louis, is also fairly common.  Even though there were many professionals in the Archives who I could ask to do the search, I needed to provide more information to avoid a long and potentially fruitless effort.

I started trying to determine which military unit Alois would have been in. Most useful was a website (www.austrianphilately.com/dixnut/) on stamp collecting! This website provided a comprehensive explanation of the structure of the Austro-Hungarian Army, breaking that structure into regiments (the proper term is actually “k.u.k. Ergänzungsbezirke” [Imperial and Royal Supplementary/Replacement Districts] but ‘regiment’ makes more sense to me) which recruited in specific geographic areas.

This was great!  All I had to do was identify the regiment recruiting the village of Burg in the present-day Burgenland area of Austria, and I could probably find Alois’ military records. Unfortunately, it was not as easy to identify the regiment as you would expect.  Eventually, I determined that the nearest k.u.k. Ergänzungsbezirke appeared to be that of Regiment 83, whose area of responsibility is Pozsony (Preßburg), W. Hungary. Moreover, Regiment 83 had been associated with that area for an extended period of time preceding World War I.

[Editorial note: The 83rd Regiment (Infanterieregiment Schikofsky Nr.83) recruitment was based in Köszeg (Güns) and in Szombathely (Steinamanger) (per BB newsletter 253 #04). Of these, Szombathely was the closer to Burg so more likely its recruiting Battalion. Page www.austro-hungarian-army.co.uk/infantry.htm says the Regiment headquarters was at Komárom (but this data was circa Feb 1914, not 1912). Page www.austro-hungarian-army.co.uk/infdep14.htm, indicates that the 83rd reported through V Corps, so there would have been a “higher-command” Pozsony connection (but not a direct recruitment connection). The reporting structure had the 83rd regiment as part of the 66th Brigade of the 33rd Division of V Corps, 1st Army (Northern Front).

As for the easiest way to determine the exact recruiting district for a Burgenland village, the 1913 Hungarian
Gazetteer lists the numbers for the Military Supplementary district, the Honvéd brigade, and the Landsturm district that each town was part of... the appropriate section in the gazetteer entry for Burg (Pinkaóvár) is highlighted above, and it indicates the 83rd (the 1913 Gazetteer can be accessed from the BB website).]

Now I felt confident enough to contact an expert in the Kriegsarchiv in Vienna, Oberrat Dr. Christoph Tepperberg. My alternative would have been to fly to Austria and do the research myself, but paying an archivist about $100 was a lot more economical than a trip to Europe.

In short order, Dr. Tepperberg provided me with copies of roughly a ten-page file on Alois Muhr. Alois’ village of Burg was variously called Pinkaóvár and Oberwart [Ed: probably referring to the district Burg is in: Oberwart = Felsöór], and you will see Alois Muhr identified in Figure 1’s excerpt as being born in 1889 and residing in Pinkaóvár. The file, partly shown in Figure 2, confirmed that Alois was conscripted by the Austro-Hungarian Army in 1912, then called up for service at the start of WW-I.


Figure 2. Excerpt from Military Record of Alois Muhr - Conscription

As best as I can tell, Regiment 83 was part of the V Korps in the August 1914 structure of the Austro-Hungarian Army (see www.austrianphilately.com/dixnut/dn3.htm, Chapter 3, Appendix A). V Korps was involved in the Battle of Galicia (aka, the Battle of Lemberg) where the Austro-Hungarian and Russian forces faced each other in a series of confrontations in August and September of 1914. Ultimately, the Austro-Hungarian forces were routed with Austro-Hungary losing an estimated total of 324,000 men including Russian forces capturing between 100,000 and 130,000 Austro-Hungarian soldiers.

It is very likely that Alois was captured in this first major engagement of the Great War on the Eastern Front and the file seems to say Alois was captured 9 Sep 1914 at the Battle of Biechawa (see Figure 3 below). However, I have, as yet, been unable to identify this Battle other than I am fairly certain it fell within the Battle of Galicia. In any event, the capture of Alois probably was the best thing that could have happened to him since I think his odds of surviving four years of World War One would have been slim.


Figure 3. Excerpt from Military Record of Alois Muhr - Capture

[Editorial comment: The text in Figure 3 says only that Alois became a POW on 9/9/2014 “in the fighting near Biechawa.” Bychawa (correct current spelling) was quite near (or even in) the initial battle line for what is recorded as the Battle at Krasnik (which is part of the Galician/Lemberg battles) and took place 23-25 Aug 1914. A map at www.historycentral.com/ww1/Galicia.html shows the full Battle of Galicia.

I show a small clip  from the full map here: note the heavy blue dotted line, which was the initial
Krasnik battle line just SW of Lublin (Krasnik is somewhat obscured but visible under the red markings). At the bottom of the clip is text "FIRST, DANKL" in red.

Viktor Dankl was Commander of the 1st Army, and V Corps and its 33rd Infantry Division (of which Regiment 83 was a part) were in that battle.

In a
GoogleMaps blow-up of that area, shown to the left, you can see Lublin, Krasnik and Bychawa. As the battle ended August 25 and Alois was captured September 9, it seems apparent that Alois wandered free for a number of days before being gathered in as a POW or that his capture was not reported for a short while.]

The file confirmed that Alois remained a prisoner of war until at least 1919. We know this because the Russian government sent an annual postcard to the Austrian government confirming that Alois was a POW in either Omsk or Nikolsk Ussuriysk.

[Editorial comment: Actually, the Russians provided lists, which the Red Cross turned into index cards and forwarded to the various governments.]

Three of these postcards were part of the file. The 1919 postcard is shown in Figure 4, indicating that Alois was held in Omsk, in the far east of Russia, near Siberia. The other postcards identified Alois’ location as Nikolsk Ussuriysk, a small town north of Vladivostok near both the Pacific Ocean and the Russian border with China. The file, particularly the postcards, essentially confirm more of the family story.


Figure 4: Prisoner of War index card for Alois Muhr

Regarding the wife of Frank Tissinai, Elizabeth emigrated to Chicago on the SS Seydlitz, arriving in New York on 18 May 1922. Alois followed on the SS Oropesa, arriving in New York on 31 Oct 1922, and marrying the widow Elizabeth Tissinai on 21 April 1923 in Chicago. Elizabeth’s maiden name was originally Elizabeth Golacz, basically confirming that Elizabeth had a first marriage to Frank Tissinai! In the course of writing this article, I learned that Frank and Elizabeth had married on 9 November 1912 in Dürnbach.

Alois’ involvement in the aftermath of the Russian revolution is not as clear. The October Revolution terminated Russia's participation in the World War I, with the Bolsheviks signing the Treaty of Brest-Litovsk with Germany in March 1918. A civil war for control of Russia followed, with the Red Army ultimately winning control of Russia after over-coming opposition from a loosely-allied diversity of interests known as the White Army.

The postcard of Figure 4 confirms that Alois was still a prisoner of war in January 1919, some months after the Treaty. Was Alois being moved around by White Russians, was Russia simply slow to repatriate prisoners in the chaos of the Revolution, or was Russia reluctant to give up the free labor of provided by these prisoners? This we may never know.

Regarding Alois and his relationship with the farmer’s wife, I am not presently aware of any known records which could confirm or refute this part of the family story, although I am certainly interested in learning of any extant Russian records. Alternatively, perhaps DNA tests may some day turn up a relative in Siberia.

So Alois, who journeyed from Burgenland to Siberia and ultimately to Chicago, lived the rest of his life in Chicago, passing away at the venerable age of 92. His son fought for the United States in World War II, and his grandson still resides in the Chicago area. For the Muhr family, it is great that most of the family stories about Alois Muhr have been confirmed.
___________________________

Note: if you are interested in the military records of Austro-Hungary, another site to review is ahmilitary.blogspot.com. I found this site after I recovered Alois’ records so I did not use it then, but the site has a good description of research in this area. This site also indicates that Dr. Tepperberg has written a book "Sources for Genealogical Research at the Austrian War Archives in Vienna."


3) CLUSTERING OF AUTOSOMAL DNA MATCHES (by Frank Paukowits)

There are a number of companies that provide autosomal DNA testing for the public. The major ones include: Ancestry.com, 23andMe, FamilyTreeDNA, Geno 2.0 and MyHeritage. This is the group that is leading the field in the development of new tools to assist people who are researching their family roots.

One of the tools that was rolled out by MyHeritage in March 2019 is called “AutoClusters.” Essentially, it analyzes your matches and groups those matches that form clusters, where everyone in the cluster will likely be on the same ancestral line. As an example, it might identify your matches in your grandmother’s paternal line, or your great-grandfather’s maternal line. Having this information might help you identify new familial lines and relationships, especially where family trees are included in your matches’ analyses, or other relationships that have already been established in your own family tree.

My wife, brother and I had all been tested at FamilyTreeDNA, but we uploaded our results to MyHeritage to see how this new tool worked. There was no cost to do this since I maintain an account with MyHeritage. The results were tabulated two ways: in a visual/graphic presentation, and a more-traditional line-by-line format. To the right is an example (dummy) graph, taken from the MyHeritage website, where each color group represents a cluster.

MyHeritage has established minimum criteria as the cutoffs for inclusion in a cluster: matching of at least 20cM in the aggregate between the person tested (for example, me) and one of my DNA matches, and at least 15 cM between everyone else in the same cluster. The 15cM cutoff eliminates fifth and greater cousins and helps reduce the time needed to calculate the clustering.

There is also a maximum cutoff: 360 cM, used to eliminate people closer than second cousins to the person tested, as such people would logically belong to many of my clusters and could not be placed in just one cluster (even with this max cutoff, some closer cousins may still belong to a couple of clusters, so they are shown in darker gray squares... see the example graph).

The percentage of total matches that were identified as part of a cluster were 4.8% (75 of 1,576) for my wife, 4.5% (105 of 2,329) for my brother, and 3.2% (71 of 2,204) for me. The average cluster size was between 3 and 4 people. At first blush, those would seem to be relatively small numbers but, considering that it could lead to establishing familial lines that you never knew existed, it still is an important tool for effectively targeting your research efforts, especially where substantive family trees are available.

My recommendation would be for people to look at incorporating DNA clustering into their research toolkit, especially when they have already been tested by MyHeritage (as there would be no additional cost). For those tested by another vendor, you might want to consider uploading your data anyway (it is only a $35 fee). Doing so will give you a larger collection of people to match with (I could identify less than 1% of my 2,200 MyHeritage matches as being people matching me at FamilyTreeDNA)... and, if you also use the auto-clustering tool, you may gain new knowledge!
 

4) DNA-BASED COUSINSHIP ESTIMATION - ANCESTRYDNA EDITION

A year ago, I wrote an article with title DNA-Based Cousinship Estimation that discussed my observations about the ability of FamilyTreeDNA autosomal tests to accurately detect the cousinship level for a predicted DNA cousin; for example, is a predicted third cousin a true third cousin? In this question, predicted means the level of cousinship indicated by the DNA test and true being the cousinship level shown by a well-documented family tree (which I have for my lines).

My investigation was driven by my reading of various reviews of the autosomal tests from the "big three" testing companies, AncestryDNA, 23andMe, and FamilyTreeDNA. What I observed was that a common "complaint" about FamilyTreeDNA was that its test over-estimates the nearness of a family relationship... for example, a true third-cousin may be predicted as a second cousin.

At the time, I had 14 relationships on FamilyTreeDNA that I could use to "test" whether this complaint was true (that is, I could document the true relationship for a predicted cousin). What I reported was that, among the 14 relationships:

 -- 4 predictions were accurate, matching the true relationship
 -- 2 predictions under-predicted (true relationship closer than predicted)
 -- 8 predictions over-predicted (true relationship more distant than predicted)

Thus I concluded, by a simple count, that FamilyTreeDNA tended to over-estimate the nearness of a family relationship, just as the critics claimed. The rest of the article, however, examined more deeply why this over-prediction occurred, with much of the reason explained by the graph below:

    

The data points in the graph are my 14 relationships, with the measured amount of common DNA (between me and the cousin) along the vertical axis (titled Total cM) and the amount expected for each true relationship along the horizontal axis (titled Expected Total cM). For each prediction to be totally accurate, each data point would need be on the red line (the "one-to-one" line, where Total cM = Expected Total cM).

Thus you should see that the measured amounts of "Total cM" between me and my cousins frequently well-exceeded the amount that was expected for our true relationships. No wonder FamilyTreeDNA overestimated the nearness of the relationship. In fact, based on the measured amounts, one would think that my cousins and I were even nearer than FamilyTreeDNA predicted.

The article went on to surmise why my measured amounts were so high... but I'll not rehash that here.



Instead, I'll move on to the real topic of this article, that being a similar discussion for the AncestryDNA autosomal test.

At some point, when AncestryDNA offered their test on-sale, I decided to have my DNA analyzed by them too. While I no longer recall any "complaints" about the accuracy of their predictions, I do recall many complaints about the limited information AncestryDNA shares, especially the lack of a "chromosome browser" and details on which segments of DNA are shared with a specific cousin. These, to me, are valid complaints and limit the value of the AncestryDNA test.

One big advantage, though, is that with their extensive advertising, the AncestryDNA pool of customers is much larger than that of any other testing company; thus you have a much greater chance of finding a cousin via their test (conversely, you have zero chance of finding cousins if their data is not in the testing company's pool of customers!). Further, if you pay extra for a subscription to access their genealogical data and family trees, you can document true relationships much easier via their combined resources.

To date, I have documented 42 true relationships for predicted cousins via the AncestryDNA test (which is three times the number of relationships I could document via FamilyTreeDNA; this is, I expect, a direct consequence of the size of the customer pools). [By the way, only two of these are among the 14 from the FamilyTreeDNA test, so there was little redundancy (which is nice!).]

These relationships range from a true 4th cousin to two true grandnephews. I'll not list all the data here but I will show it in a graph (below). The underpinnings of this graph are laid out the same as the FamilyTreeDNA graph I showed above, with the measured amounts of common DNA along the vertical access and the expected amounts (for a given relationship level) along the horizontal access. However, there is quite a bit more information that somewhat complicated the graph (which I'll not explain until after I make a few general observations about the base data [the blue points]).

  

First, you should see in the above graph that there is a tendency for my measured amounts of common DNA to exceed the expected amounts (just as in the FamilyTreeDNA data). Also like in the FamilyTreeDNA graph, the "extra" measured DNA seems to affect the more-distant relationships [i.e., those with less Total cM] more than the closer relationships [those with greater Total cM]. Said differently, the data for closer relationships appears to be better clustered about the red "expected" line than the data for more-distant relationships, which cluster above the red line.

One added piece to this graph is the thin dark line, which is a linear best-fit line between Total cM and Expected Total cM. This should give you a better idea of the average deviation of the data from the red one-to-one line.

Another added piece to this graph are the green lines running across the graph and the green labels along the left side. The lines represent the "cut points" for Total cM that AncestryDNA uses to divide their predictions into the different cousinship levels; the green labels are the predicted levels, with 3C (for example) being my short notation for 3rd Cousins. Thus any data points falling between the green lines directly above and below the green 3C label are predicted as third cousins. You should read the other lines and labels similarly.

The final piece of added information is the red labels at the top. Again, 3C would represent a 3rd Cousin. The 1R notation tacked on indicates Once-Removed, 2R, Twice-Removed, etc. Lastly, the -d notation indicates that this is a Double cousin (of the indicated type). My grandnephews fall outside this notation scheme and are simply labeled GNe.

You should observe that the three "middle" categories (horizontally) have more than one red cousinship label listed. That is because these categories can (and do) represent more than one cousinship level. For example, the data in the third-from-the-left category is for one 2C2R, six 3Cs, and one 3C1R-d. These cousinship levels have exactly the same Expected Total cM so are indistinguishable by an autosomal DNA test.

Another thing well-worth noting is that AncestryDNA sets their ranges of measured DNA for predicting a cousinship level quite high relative to the expected levels. Let's used 3C as an example... as noted in the paragraph above, a true 3C falls in that third-from-the-left red category. If you find that red 3C label in the graph above and follow down vertically to the red line (the expected amount for a 3C) and then look left to the green labels, you'll see that the expected amount for a true 3C falls in Ancestry's predicted 4C range. That is, AncestryDNA requires the measured amount for a 3C to be well above the expected amount before it will predict that it is a 3C! This same requirement holds for a true 4C and the expected level for a true 2C is quite low in its prediction range. I do not show a 1C relationship (but it's expected amount would be fairly centered in AncestryDNA's prediction range).

So, what is the take-a-way from the above paragraph? Simply that AncestryDNA is compensating for the phenomenon that caused so many of my FamilyTreeDNA relationships to be over-estimated by raising their prediction ranges for the more-distant relationships... and that is a reasonable thing to do.



You probably are asking, how did AncestryDNA do on predicting my known relationships? I'll answer that in two ways.

First, I need to provide a little background: in online article the-science-behind-a-more-precise-dna-matching-algorithm, AncestryDNA provides the following table of ranges for Total cM that they use to assign a predicted cousinship level:
 

Amount, cM Predicted Relationship
3,475 cM parent, child, or identical twin
2,400-2,800 cM immediate family: full sibling
1,450-2,050 cM close family: grandparent, aunt, uncle, half-sibling
680-1,150 cM 1st cousin, great-grandparent
200-620 cM 2nd cousin
90-180 cM 3rd cousin
20-85 cM 4th cousin
6-20 cM distant cousin: 5th to 8th cousins

Based on this table, here is how my 42 relationships scored:

 -- 33 predictions were accurate, matching the true relationship
 --  8 predictions under-predicted (true relationship closer than predicted)
 --  1 prediction over-predicted (true relationship more distant than predicted)

By this standard, AncestryDNA tends to be quite accurate overall, with a slight tendency to under-predict (rather than to over-predict like FamilyTreeDNA) when they are wrong.



You may have noticed that I "qualified" my comments above by saying "based on this table" and "by this standard" ...I did that for a good reason. I want you to look again at the AncestryDNA graph that I showed (I've repeated it below so you do not have to scroll back). Did you note red categories 3C1R, 2C1R/3C-d, and 1C1R?

  

These categories each have an Expected Total cM value that is not the same as any of those for 4C, 3C, 2C or 1C. That means it should be possible to predict these categories separately from the 4 main "whole-cousin" categories that AncestryDNA currently predicts for us... but they do not. Instead, they lump them into the "standard" predictions based on the green ranges I showed above. That means that most 3C1Rs are predicted as 4th Cousins, 2C1Rs as 3rd Cousins, and 1C1Rs as 2nd Cousins.

However, it is apparent from another AncestryDNA online article, DNA-Matching-White-Paper.pdf, that they may have sufficient information to attempt to separately predict these "xC1R" categories.

Again, a little background is needed... the biological process responsible for the transmission of chromosomes from parents to child is called meiosis. And the random selection of chromosome fragments during meiosis is called recombination. Although we get exactly 50% of our DNA from our mother and 50% from our father, that "random assortment of chromosome fragments" during recombination means that we do not get exactly 25% from each of our grandparents. Yes, the amount is quite close to 25% "on average" across many people but can deviate significantly during a "specific" recombination for a given person. This "25%" average value is what gives us an "expected" Total cM level for a given relationship level... but the deviations from that exact 25% during recombination is what forces DNA testing companies to use ranges when predicting a cousinship level.

However, testing has become good enough that AncestryDNA can distinguish the levels generated from up to 10 meioses... after that, the errors in the biologic process overwhelm the small differences in expected cM levels.

Based on data presented in a graph in the AncestryDNA white paper, I have created the following table. It shows the ranges of amounts of DNA that are present in real subjects at each meiosis level, along with a selection of relationships that result from that number of meioses:

Amount, cM Relationship Meioses
> 3,300 cM parent, child, or identical twin 1
2,200-3,300 cM full sibling 2
1,300-2,200 cM grandparent, aunt, uncle, nephew, half-sibling 3
650-1,300 cM 1C, great-grandparent, grandnephew 4
340-650 cM 1C1R

2C, 1C2R

5
200-340 cM 6
90-200 cM 2C1R

3C

7
75-90 cM 8
40-75 cM 3C1R

4C

9
< 40 cM 10


[Please note that I have purposely deleted a few dividing lines in this table to show where AncestryDNA currently groups data when making predictions.]

The graph I based my table on was quite similar to the one below (mine is rotated into a horizontal layout and has some added labeling):

    

From this graph, you should be able to see where the cM range amounts come from. AncestryDNA did a "best fit" algorithm to divide the data into ranges. It should be apparent to you from the graph that there are cM values that can fall into more than one meiosis grouping, and that the overlap gets greater as more meioses occur. Nonetheless, the 3, 5 and 7 meioses levels appear fairly distinct from the even-number levels around them... these three "odd" levels are for the 1C1R, 2C1R and 3C1R cousinship categories, respectively.



As I said above, it seems apparent that AncestryDNA may have sufficient information to attempt to separately predict these three Once-Removed categories. Had I held them to a standard of also properly predicting these three extra levels, here is how my 42 relationships would have scored:

 -- 18 predictions were accurate, matching the true relationship
 -- 23 predictions under-predicted (true relationship closer than predicted)
 --  1 prediction over-predicted (true relationship more distant than predicted)

Not surprisingly, they do not fair so well and their tendency to under-predict becomes far more apparent (as most of my once-removed cousins are predicted as too distant).



There you have it...  so do you prefer AncestryDNA's conservative tendency to under-predict or FamilyTreeDNA's liberal tendency to over-predict? ...just another "pick your poison" choice!
 


5) HISTORICAL BB NEWSLETTER ARTICLES

Editor: This is part of our series designed to recycle interesting articles from the BB Newsletters of 10 years ago.

For this month, I pulled a piece from May 2009 that tells us about the Hianzn Museum in Rábafüzes, Hungary. You may recall two articles a few months back that discussed the Hianzn and the Hianzisch dialect. This seemed an appropriate "follow-up" (even though it originated 10 years ago!).



THE BURGENLAND BUNCH NEWS - No. 187
May 31, 2009

HIANZNMUSEUM IN RAABFIDISCH / RÁBAFÜZES

"Do not forget that tomorrow, today's tool is already history." / Franz Dankovics

In Burgenland today there are several ethnic groups, among them Croatian and Hungarian. But German-speaking Hianzn still live behind the Hungarian border. A museum in Rábafüzes tells their story. The first Hianznmuseum in Raabfidisch (Rábafüzes) was opened in Hungary.

The village (of approximately 400 inhabitants) is today a part of the town Szentgotthárd. There are still about 50 people who speak "Hianzisch". A museum was devoted to them and their forefathers in what was formerly the village school.

Memorial to the farmer culture and the Hianzn

The ethnological collection's foundation stone was laid by the former principal Ferenc Dankovics and his wife in the sixties. On 26th May 1986 the collection was opened to the public in the school building. After Ferenc Dankovics' death, the collection was also extended and, after years of hardship, it came under the maintenance of the Local Government of the German Minority and the Branch Library in Rábafüzes. The present exhibition room was provided by the local government as a final place and, after being redesigned, opened its gates to the public.

In the meantime, 500 exhibits have been assembled with years of hard work. The whole inventory is labeled in Hungarian, German, and Hianzisch.

Contacts in Burgenland

Until World War II, the population of Rábafüzes had close contact with their neighbors in Burgenland. The place was pulsing, says the village eldest, 86-year-old Paula Nagy Vincené.

"There were 5 guesthouses in our village, 3 were outside in Bergen. Then there was another guest house next to the border that already belonged to Burgenland - we also went there to dance", says the 86-year-old.

Female Choir of Rábafüzes

In 1976 the Female Choir in Rábafüzes was formed, which has faithfully maintained the song lore of the village and the surrounding areas ever since then. The songs are also presented in vernacular "Hianzisch". The founder and leader of the choir is Magdolna Unger, and its harmonica accompanist is her sister, Edit Unger. The choir has 2 albums so far.

Hianznmuseum, Rábafüzes/Raabfidisch, Kodály Zoltán út 2
Open hours: Wednesday: 11 am - 4 pm; Friday: 12 noon - 6 pm
 

6) ETHNIC EVENTS

LEHIGH VALLEY, PA


Friday–Saturday, June 7-8: Sommerfest at the Lancaster Liederkranz. Entertainment by Maria & John, Die Alpenländer, The Bratwurst Boys, folk dancers and singers. Info: www.lancasterliederkranz.com

Sunday, June 16: Edelweiss Schuhplattlers Fundraiser Clambake at the Reading Liederkranz. Music by Maria & John. Info: www.readingliederkranz.com

Sunday, June 23: 102nd Stiftungsfest at the Coplay Sängerbund. Entertainment by The Emil Schanta Band and Austrian/German choral groups. Info: www.coplaysaengerbund.com

Sunday, June 23: Parish Festival at Queenship of Mary Catholic Church (formerly Our Lady of Hungary) in Northampton. Music by MountainXpress. Info: queenshipofmary.weconnect.com

Saturday, June 29: Wurstfest at the Reading Liederkranz. Music by Mountain Xpress. Info: www.readingliederkranz.com


NEW BRITAIN, CT

Friday, Jun 1, 7 pm: Heimat Abend. Austrian Donau Club, 545 Arch Street, $3. Music by Frank Billowitz.

Friday, June 15, 7:30 pm: Heurigan Abend. Austrian Donau Club, 545 Arch Street, $3. Music by Schachtelgebirger Musikanten.


7) BURGENLAND EMIGRANT OBITUARIES

Maria Habetler (née Rajkovac)

Maria Habetler, 88, of Northampton, Pennsylvania, passed away peacefully on Wednesday, May 15, 2019 in Cedarbrook Nursing Home.

She was the wife of the late Ignac Habetler.

Born June 4, 1930 in Horvátlövo (Hrvatske Šice/Kroatisch Schützen), Vas Megye, Hungary, she was the daughter of the late Simon and Etelka (Cseri) Rajkovac.

Maria worked as a seamstress for many years. She enjoyed cooking and baking for her family. She was a member of the former St Michael’s Catholic Church in Northampton.

Survivors: sons, John Habetler, Mr. & Mrs. Steve Habetler; grandchildren, Tracy, wife of Simon Dragovits, Steve Habetler and his wife Rachel; great grandchildren, Courtney, Autumn, Kendall; sisters, Stella Pock and Goldie Skrapits. Maria was predeceased by 6 siblings.

Services: A Prayer Service will be held on Tuesday, May 21st at 11:00 a.m. in the Reichel Funeral Home, 326 E. 21st St., Northampton. Family and friends may call 10 -11:00 a.m. Burial will follow in Our Lady of Hungary Cemetery. Online condolences may be submitted at www.reichelfuneralhome.com.

Published in Morning Call on May 17, 2019



John I. Unger

John I. Unger, 98, resident at Tuscan Garden, Palm Coast, Florida, passed peacefully on May 9, 2019.

Born on June 23, 1920 in Deutsch Schützen, Austria, he was a son of the late Johann and Anna (Standor) Unger. He arrivied in the US in 1931.

He enlisted in the US Navy in 1939, graduating both Navy and Marine Corps boot camps, and was assigned a Corpsman with 1st Defense Battalion, US Marine Corps. This unit was assigned the defense of Wake Island that was attacked by the Japanese starting on December 8, 1941 and finally surrendering on December 23rd. John was a Prisoner of War for 44 months in camps in China, Japan and Korea providing aid and comfort to other POW's. Released at the end of WWII, he returned home and continued to serve 20 years, retiring a Navy Chief.

John and Alice fell in love in 1939 and enjoyed 74 years filled with joyous times among family and friends in the San Francisco Bay Area.

They "started it all" and are survived by sons, John W Unger and Brian L (Jacki) Unger, grand-children Johnny (Stephanie), Tim (Diane), Julie (Alan), Brian P (Kendra), Rachel (Jamil), and Alison (Antonio) as well as coast-to-coast great-grand-children including Michelle (Kyle), Erin, Allyson, Tyler, Jack, Julia, Molly, Timothy, Maddie, Giuliana, Hayden, Jackson and Hayes.

He is predeceased and joins Alice and so many that he touched in a life well lived that is shared in the book "The Last Corpsman" written by Juan Carlos Marcos.

Family and friends may visit on Monday, May 13, from 10:00-11:00AM at the chapel of Craig-Flagler Palms Funeral Home, 511 Old Kings Road South, Flagler Beach. A celebration of his life will begin at 11:00AM. He will be laid to rest at Queen of Heaven Cemetery in California where he will receive his military honors. In lieu of flowers, kindly consider Veterans of Foreign Wars in his memory. For online condolences go to: www.craigflaglerpalms.com. Arrangements are in the care and trust of Craig-Flagler Palms Funeral Home.

Published in Daytona Beach News-Journal from May 11 to May 12, 2019



Agnes Badar (née Magyar)

Agnes Julianna Badar, 82, of South Bend, Indiana passed away on Saturday, April 27, 2019.

Born on January 17, 1937, in Ólmod (Plajgor/Bleigraben), Hungary, she was a daughter of the late Thomas and Julianna (Poropatich) Magyar.

On July 23, 1960, in Our Lady of Hungary Catholic Church, South Bend, Indiana, she married Victor Badar, who preceded her in death on August 14, 2011.

Agnes is survived by two daughters, Mary Shuler of Plymouth, MI and Monica (John) Hehl of Plainfield, IL; one son, Anthony Badar of South Bend, IN; two grandchildren, Matthew Hehl and Victoria Badar; two sisters, Anna Hedl of South Bend, IN and Frieda Botelho of Novi, MI; two brothers, Anthony (Donna) Magyar and Steve (Connie) Magyar, both of South Bend, IN; and by many nieces and nephews. She was preceded in death by two infant sons, Joseph and Victor, Jr.

Agnes was a “mom to many” working in the dining hall at St. Mary's College for 37 years. Agnes enjoyed baking, gardening, and was very devoted to her church. Her family was her greatest joy in life.

Visitation will be held on Wednesday, May 1, 2019 from 3:00 until 8:00 p.m. at the Kaniewski Funeral Home, 3545 N. Bendix Dr., where a parish Rosary will be prayed at 4:00 p.m. A Mass of Christian Burial will be celebrated on Thursday, May 2, 2019 at 12 Noon in Corpus Christi Catholic Church. Burial will follow in Highland Cemetery. Memorial contributions may be made in Agnes' honor to the American Cancer Society or the Juvenile Diabetes Research Foundation. Online condolences may be left at www.kaniewski.com.

Published in South Bend Tribune on Apr. 30, 2019

END OF NEWSLETTER (Even good things must end!)


NOTICE (Informal Terms and Conditions)
: The Burgenland Bunch (BB) was formed and exists to assist Burgenland descendants in their research into their heritage and, toward that end, reserves the right to use any communication you have with us (email, letter, phone conversation, data upload, etc.) as part of our information exchange and educational research efforts.
    ● If you do not want your communication to be used for this purpose, indicate that it is "confidential" and we will attempt to abide by that request.
    ● Correspondents who communicate with the BB without requesting confidentiality retain their copyright but give a non-exclusive license to the BB allowing us to forward to BB members, publish in our monthly newsletter or on our website, and/or subsequently and permanently archive all or parts of such communications.

The formal Burgenland Bunch Website Usage Agreement can be found here: Agreement

The Burgenland Bunch homepage (website) can be found at: the-burgenland-bunch.org

Burgenland Bunch Newsletter, copyright © 2019 by The Burgenland Bunch
All rights reserved. Permission to copy excerpts granted if credit is provided.