Thursday, November 3, 2022

Subcarpathian Rus'--Loose Mentions and Misunderstandings

This post is a follow-on to my reviewing of the 1930 census sheets from my grandfather's home village of Nagy Szelmenc and the adjacent village Kis Szelmenc (Czech/Slovak Veľké and Malé Slemence). About two years ago the 1930 census became available online, following a 90-year privacy period.1 I was slow to realize that the information was available, but have now updated several WikiTree pages, including those for my grandfather's brothers and their father, and for my grandmother's sister in Csap. I'll have more to say about that 1930 census itself, including lessons learned, in a later post.

Intending to summarize some of the information, but also wanting to avoid reinventing the wheel, I searched for what other people have been doing with this 1930 census. In the process, which has included following links to descriptions of the history of the area, I've found that many play fast and loose with terms they use to label broad and narrow regions, glossing over context and time, substituting alternatives as if they were equivalent synonyms from a thesaurus. There is a lot of history, with many labels. But my concern for this post is about the early censuses from Czechoslovakia, and thus is limited to two time periods. The first period is 1921-1930, when the censuses were conducted. The second period is now and recent decades, when the information has been made available.

I found this map at wikimedia commons.

The map is from a 1921 history of Czechoslovakia. The broken line boundary through the county of Užhorod separates two parts of Czechoslovakia. On the west is the Slovakia (Slovensko) part. On the east is the Subcarpathian Rus' (Podkarpatská Rus) part. Notable on the map around the city of Užhorod is how the boundary forms a tight nearly three-quarter circle around the city. The term Subcarpathian Rus' has been reasonably applied by many people to a broader area based on their analyses of earlier reported ethnicities. But for the purpose of discussing the census records, it is the area as shown on this map, which was defined in the establishing treaties and founding documents for Czechoslovakia. As I understand, within Podkarpatská Rus there were numerous internal rearrangements of county and district boundaries between 1921 and 1930, but the western boundary of Podkarpatská Rus remained the same in 1930 as it had been in 1921.

Then there is the border today, which has not changed since 1945. When Stalin annexed Transcarpathia to the Ukrainian part of the Soviet Union, the border line was straightened and moved comfortably west of the city of Užhorod. Transcarpathia is slightly larger than Podkarpatská Rus; they are not the same area. Podkarpatská Rus is not Czech for Transcarpathia. According to Google Translate: Czech for Transcarpathia is Zakarpatí; Slovak for Transcarpathis is Zakarpatsko.

It is the position of the Slovak National Archives that census sheets from 1930 stored by them are only from present-day Slovakia.1 Yet it is clear that the 1930 census sheets made available online by the Slovak National Education Center at their Slovakiana site include all of Slovensko as it was in 1930, which includes the far western part of today's Transcarpathia. The Slovakiana site does not include Podkarpatská Rus.1

I don't know if the census sheets for Podkarpatská Rus were at some point transferred from Czechoslovakia to Transcarpathia, or if the Podkarpatská Rus sheets were always stored there and remained there as part of Transcarpathia. At any rate, in 2017 the Budapest Capital Archives went to the Beregszász (Berehove) section of the Transcarpathian State Archives and digitized the 1921 census sheets for Podkarpastká Rus. The digitized sheets are available online. That online collection is not a 1921 census for Transcarpathia. It is the 1921 census for Podkarpatská Rus.

Reference 1. Email responses from the Slovak National Archives archiv.sna@minv.sk and the Slovak National Education Center slovakiana@nocka.sk to questions from Jim Toth, October 2022.

Tuesday, August 9, 2022

Browsing a GEDCOM File

A GEDCOM file is the standard for sharing genealogical information. The version 5.5.1 specification is old, but still widely used. A GEDCOM file is generally understood to be intended for output from one computer program, then input to another computer program. But the GEDCOM file is plain text. The file's contents can be browsed that way, and that may be the only way to see all the details that were output by the generating program.

At GitHub I have a little macOS app that I use to browse GEDCOM files. Some of my GEDCOM files are very old, sent by cousins when I first got into genealogy over 20 years ago. Some of the files were created only recently, when I downloaded information from WikiTree and from Ancestry. (It is the standard, so a GEDCOM file is what you get when you download your tree from somewhere.)

Why not just use a plain-text editor for browsing? Discussion follows this screenshot of the app.

In this example the opened file is my tree downloaded from Ancestry. That tree was created by me to aid Ancestry-DNA matches in determining common ancestors. Because of that sole purpose this file contains records for only 37 individuals (35 of them my known ancestors) in 18 families. (My private GEDCOM file on my personal computer has about 1500 individuals.) A single record in a GEDCOM file generally contains multiple lines. The beginning of a new record is indicated by, among other things, a zero as the first character on a line. Though not obvious from the screenshot, the entire opened file can be scrolled from beginning to end in the view on the left. I've scrolled to the point where the beginning of the record for Ann Cavanaugh, one of my great-great-grandmothers, is displayed. Having clicked on the "Process" button, the file has been separated into records which are sorted and selectable in the four views on the right. I can easily jump from one record to another. In the list of individual records I've selected Ann Cavanaugh--much easier selecting that one record than searching for and scrolling to Ann in the original file. But what if Ann had been in a file with thousands of individuals? I would have switched temporarily to sort the list of individuals by surname.

Each record in a GEDCOM file starts with a unique cross-reference label. Ancestry has generated very long cross-references for the individual records. Ann's individual record indicates that she is a spouse in family F17. Having selected F17 in the list of families, we can see that that family record is linked back to Ann's individual record--a two-way link between individual and family record, as required by GEDCOM. My little app is oblivious to most of GEDCOM's requirements and recommendations. Basically all it does is display whatever the content happens to be for each record.

While preparing this post and reviewing the earliest version of this screenshot, I noticed that there were too many families and individuals--duplicates and even triplicates, with the extras differing in having mangled links. Here is how I think that happened. Before last December I had already enjoyed connecting with DNA-test-match cousins at other sites. Worried that I might be missing something at Ancestry, last December I took advantage of their DNA test sale. Preparing for anticipated new connections I created for the first time at Ancestry my tree, adding only my ancestors, one at a time. After that I succumbed to the allure of confirming Ancestry's hints. I think that is how the extra, mangled relationships were generated. After several iterations of deletions and repairs, my tree is back to what I originally intended. So the point is, downloading and browsing of a GEDCOM file can help find problems that are not obvious using the vendor's interface.

I prefer WikiTree. These days my genealogical research results get transferred directly to WikiTree, either by updating existing WikiTree profiles, collaboratively if possible, or sometimes by adding new profiles there. The GitHub link for my GEDCOM Browser app has a README file on its main page which contains a screenshot similar to the one on this page. In the GitHub screenshot the file is a GEDCOM that I downloaded from WikiTree. In that file I've also selected Ann Cavanaugh for illustration, so the two screenshots can be compared and contrasted. The contrasts between a WikiTree GEDCOM and an Ancestry GEDCOM illustrate that there is a great deal of flexibility in how information can be organized in a GEDCOM file. That flexibility can be a hindrance when importing a GEDCOM from somewhere else.

There is a problem with GEDCOM files generated by WikiTree that transcends whether WikiTree follows the spirit of the GEDCOM law. The problem is well explained in this Tamura Jones web page from over five years ago. WikiTree exports the entire biographical section of a profile as one long note in the individual's GEDCOM record. A large number of continuation lines are needed. WikiTree breaks a line and continues on the next line when the line length is well short of the limit specified by GEDCOM. All of that is within the letter of the GEDCOM law. The problem comes when a two-byte UTF-8 character (for example, an accented letter in a Hungarian name, or an educated quotation mark) happens to straddle the arbitrary number of bytes where WikiTree breaks the line. A malformed UTF-8 file is generated. Fortunately my Mac text editor of choice follows orders when I tell it to open the file as UTF-8, but it complains and warns me, highlighting the problem spots. So it was relatively easy to manually repair the file. I only recently experimented with downloading GEDCOM from WikiTree, and it was surprising to eventually discover that the malformed UTF-8 problem had been identified five years ago and never fixed.

Tuesday, May 17, 2022

My Grandparents' European Neighborhood

On my mother's side of the family tree there are paper trails going back five generations. And over the last few decades I've visited several of those maternal ancestral locations, both in the United States and in Ireland. My father's side is in some ways simpler, but in many ways much more complex. This post will be about where my paternal grandparents came from.

On that paternal side I am only two generations removed from Europe. When my grandparents left in 1905, each only age 15, their native region was then far from any international border. Today that area is the meeting point of three countries: Ukraine, Slovakia and Hungary. Eight years ago I traveled to Hungary and approached the old neighborhood, getting close to the border but staying on the Hungary side. Since then I had an urge to get closer, but did not feel comfortable about traveling in Ukraine on my own, especially to the rural villages. I eventually signed up for a tour of Ukraine. The tour operator offered an add-on, which I took advantage of. After the regular tour ended in Lviv in late October, a driver and the tour guide took me southwest to Uzhhorod in Transcarpathia, and from there to my grandparents' villages.

About five months ago, in the previous post here, I focused on the topography of the Carpathian Mountains, zooming in on the rural area which the regular tour had visited. When writing that previous post I had been intending that for this post at this point I would simply share recent pictures from western Transcarpathia. But in the meantime Russia began attacking Ukraine. We've been reminded that the four countries bordering Transcarpathia are all members of NATO. Autocratic leaders in Russia and in Hungary have amplified their nationalistic xenophobic propaganda to justify and maintain their corrupt holds on power. So it now seems impossible to show recent pictures without dwelling a bit on the history and politics of the area. I'll do the travelogue and the ruminating together, intermingled, beginning by going back to the previous post.

I'm kind of proud of how the first figure in that previous post, the unzoomed-in version, displays the broad arc of the Carpathians while at the same time highlighting small-scale drainage features. You might want to click on that image in the previous post and keep the image open in a separate window. From now on I'll call that image "the topo map." The area of the topo map was mostly beyond the influence of the Roman Empire, even at its greatest extent. As Christianity expanded, missionaries entered the area. Over several centuries they obtained mixed and limited results. Ultimately, over a period of only three decades ending in the year 1000, the Pope and his counterpart in Constantinople made individual deals with each of the rulers of three kingdoms. Each of the three kingdoms extended beyond the topo map to broader areas: Poland to the northwest, Russia to the northeast, and Hungary to the southwest. Thus the topo map is comprised of what were fringe territories of the three newly recognized kingdoms. The kingdom of Russia was headquartered at Kyiv; Moscow was then just a backwoods trading post, and remained that way for another 500 years. The part of today's Ukraine that is on the topo map (excluding Transcarpathia) first came under the yoke of Moscow's tyranny in September 1939 (see for example Timothy Snyder's Bloodlands).

As I've gotten into genealogy and DNA testing for genealogy, I realize more and more that there is a difference between ethnicity and ancestry composition. My grandparents and their relatives and friends who immigrated to America over a hundred years ago were very much ethnic Hungarian. They had grown up in the southwest part of the area that today is Ukraine's Transcarpathia. But from 1867 until the end of World War I the area that is today's Transcarpathia was in the Hungarian part of Austria-Hungary. In 1867 Austria had turned the clock back to the year 1000 by granting a great deal of autonomy to a partially restored Kingdom of Hungary. The Hungarian part of Austria-Hungary covered all of Sub-Carpathia (the inside of the arc of the Carpathians) including not just today's Transcarpathia but today's Slovakia and the northwest part of today's Romania. Enlightened Hungarian leaders of the 1870's recognized that their Kingdom was multi-ethnic and multi-cultural, and required respect for everyone. But by the time my grandparents were born, a policy of Magyarization (Hungarianization) had taken hold.

Tensions were already rising before 1918, and after 1918 many things happened in the area that is today's Transcarpathia. My grandparents never went back after 1905. A few old papers remain, financial and vital records, that document international mail exchanges into the 1920's. But after that decade contact was lost between my grandparents and the old country.

In today's Uzhhorod I saw no evidence of accomodating two languages. But in the villages closer to the border with Hungary it's clear that to this day many consider themselves ethnic Hungarian. It was fun to pretend to be trilingual, at least for the purpose of reading the place names and "Welcome To Our Community."

My grandmother was born in Chop (Чoп, Csap), and her mother was born across the river in Zahony. Eight years ago on the rental agreement I specified that I would not take the car out of Hungary. My plan had been that after parking the car in Zahony, Hungary, I would take the very short local train ride across the river and then from the train station walk the old main street of Csap. But the ticket agent at the Zahony station said that nothing was available until three days later, and I had plans to be across the country by then. This past October I finally made it to Csap. Below are views looking both directions along the street from near the corner where I think my grandmother's family lived.

It was a very quiet fall Saturday morning. The JewishGen page for Chop has map links, a historical summary and many old and new photos, including some of the Roman Catholic church which my grandmother would have attended. The current church is dated 1903 by the inscription above the main entrance. The morning sun gave a glare to the picture there; I like this one better from the side. I'm standing on the grounds of a very large building that is labeled community center, but looks like it could have once been a school.

Szürte is situated about halfway between my grandmother's Csap and my grandfather's Szelmenc. My grandfather's mother was Barbara Meszaros; we don't know anything else about her, presumably from Szürte like the other Meszaros's. Except for getting out for the picture earlier above with the west side entrance sign, my other pictures of Szürte were taken through the window of the car. I'll leave detailing Szürte itself to my Meszaros cousins.

Szürte is near the north-south main highway connecting Uzhhorod with the border crossing at Csap/Zahony. As in Csap, the buildings in Szürte appear from the outside to be well maintained. But that gets left behind when heading to my grandfather's area. Getting there requires traveling west from Szürte, and very quickly you are in the middle of nowhere. In the two pictures below, especially the first one, the Carpathian mountains can be seen on the distant horizon.

Some potholes were so large that if Russia were to bomb the road it would be hard to tell. Speaking of Moscow, visible in the second photo are the remains of a collective farm, out in the middle of nowhere. Previously the tour guide had pointed out other such remnants, but they were close to main roads, with houses around. I knew that when the Soviet Union took control of Transcarpathia after World War II resistance had been violently suppressed. For example, Greek Catholic priests had been murdered. Still it was disturbing, and remains so, to see physical remnants of that time so close to locales on my family tree. I can even see what looks like a guard tower at a prison. It's reminders like that that have Ukrainians determined to recover their territory currently occupied by Russia. The Ukrainians concern is about more than just which accent or dictionary will prevail.

The name Szelmenc is not derived from Hungarian. Instead, according to the town history a Polish Count received a grant of land from the Pope in the 1300's. The Count's name as it was converted into Hungarian became Szelmenc. (In Hungarian, the combination sz is pronounced s; an s without a z is pronounced sh. The c at the end gets a ts sound). As often happened with other villages in Hungary, over time the Count's property was developed into two adjacent settlements: Little Szelmenc and Big Szelmenc, in Hungarian Kis- and Nagy-. My grandfather's birthplace was Nagy Szelmenc, which is Veľké Slemence in today's Slovakia. Big and Little have experienced a complicated national history, together before 1945 and separate since. Between the two World Wars what is now known as Transcarpathia was a part of, an eastern extension of Czechoslovakia. With Hitler's blessing in November 1938 Hungary annexed about 15% each of today's Slovakia and today's Transcarpathia (see for example Paul Lendvai's The Hungarians). All of the annexed territory, which included both Szelmenc's, had been part of Czechoslovakia since 1919. In March 1939 Hungary annexed the other 85% of today's Transcarpathia, despite the fact that the population of that 85% area had always been predominately non-Hungarian. After World War II Hungary's border was reset to where it had been established after World War I. The Soviet Union annexed Transcarpathia, creating a new eastern border for Czechoslovakia. The new border started out from Hungary extending north-northeast. Most towns fell easily east or west of the straight line, but at Szelmenc there was a problem. A slight dogleg was inserted into the straight line to put all of Little Szelmenc in the Soviet Union and all of Big Szelmenc in Czechoslovakia. Almost 20 years ago a border crossing for pedestrians only was established between the two Szelmenc's. I could not cross there with just my USA passport. I knew that, but had thought that I would be able to see across the border. Unfortunately buildings and other structures have grown to block the view. I was told that without crossing papers I could not pass the limits of Little Szelmenc, marked by the sign in the first photo below. The entire roof of the building on my right was in even worse shape than the corner. The building behind it, with the blue wall, was signed near the top, in English, Shopping Center. In the background of the second image you can see Ukraine, and then Slovak Republic (Slovakia). Someday I'll visit Slovakia, entering with my USA passport, and then find someone to escort me to the border on the other side.

So back to there being a difference between ethnicity and ancestry composition. The genealogical DNA test companies all provide percentage "ethnicity" estimates. For example, my autosomal DNA yields estimates of roughly 47% Irish and 45% Eastern Europe, with leftover percentages for Scotland, the Baltics and about 5% Mediterranean (the specific areas bounce around from the Adriatic to Spain to The Levant). Some companies properly avoid the term ethnicity. For example 23andMe substitutes a bland but more suitable "ancestry composition." Usually when a DNA match is selected you can also see the match's "ethnicity" estimate, the reasoning being that the common ancestor must be in one of the overlapping "components." For my matches where the overlapping component is Eastern Europe, those who specify known ancestors from there are more likely to specify Ukraine, Poland or Slovakia as their ancestral location rather than Hungary. For my grandfather I specify Hungary because, I say, "That is what it was when he left there." It's no more than ethnicity. My YDNA tells an interesting story about ancestry composition. But, aside from a link to this project page, I'll save discussing YDNA for a future post.