Jewish Genealogy Basics: Yizkor Books

It is a bit sad to have to include Yizkor Books under my ‘Jewish Genealogy Basics’ category on this blog, but unfortunately most Jewish people have relatives who perished in the Holocaust, and there is no getting past that fact. Yizkor Books are an important resource for those people whose relatives came from the towns and regions covered by these books, mainly because these towns don’t exist anymore or have no Jewish remnants in any case. These books are the last memories of the people who lived in these communities.

Yizkor Books were generally books put together by survivors of a specific community, usually a town or city, although sometimes books were put together for larger regions. These were Holocaust survivors who wanted to share what their community had been like before the Holocaust, and what happened to it during the Holocaust. In most cases the Jewish communities described in these books completely ceased to exist after the war, and the survivors made their way to different countries including the US, Israel and various South American countries. Thus these books were published in the years following the war, in the 50s, 60s and 70s mostly (although some were published even in the 80s and 90s), in a mix of languages that may include Hebrew, Yiddish, English and more. Many of the books list the names of those people from the town that were killed during the war (these are called necrologies).

It’s important to remember that Yizkor Books were put together by members of the destroyed community, usually only for members of that community. They were generally printed privately in small quantities, and thus most of these books are not widely available. Some libraries have made an effort to build collections of Yizkor books, to preserve them and to make them available to the public. JewishGen keeps a list of libraries with Yizkor Book collections, and lets you search for specific towns and see which libraries hold their Yizkor Books. I don’t know if any library has every Yizkor book published, although it’s a good bet that Yad Vashem (which lists 1040 Yizkor Books in their collection) is about as comprehensive a collection as you will find. I suspect the publishers of these books all donated copies to Yad Vashem to insure there was at least one copy available there.

In the US, one of the largest collections of Yizkor Books is at the NY Public Library, in their Dorot Jewish Division. The library has over 750 Yizkor Books available for viewing, but more interestingly for those who do not live in NY (or even for those who do), is that they have digitized some 650 of those books and made them available for viewing online. On the web site you can choose a book and browse through the pages of each book, but they are not searchable. Keep in mind most of these books are in either Hebrew (if published in Israel) or Yiddish (if published in the US). Some of the books have small English sections, but usually the majority of the books are in either Hebrew or Yiddish.

Some of the Yizkor books can be searched via the GenealogyIndexer.org web site, which indexes many books and makes them searchable online, including directories and Yizkor Books. Keep in mind that this search is based on computer software which tries to automatically transcribe each page, so it is not perfect, and although it indexes Hebrew and Yiddish, you will need to search in Hebrew or Yiddish to find those words in the index. If you’re searching for a last name, you can search in both English and Hebrew, for example, by including both the name in Hebrew and English and eparating them with the Boolean OR, for example:

Traurig OR טראוריג

Keep in mind that even if you know the spelling of a name in Hebrew, it may have been different in Yiddish.

In addition to the NYPL and GenealogyIndexer.org, JewishGen has an ongoing project to transcribe (English sections) and translate all (non-English sections) of Yizkor Books and place the text online. In addition, as books are transcribed and translated, all the names listed in the books are added to their Necrology Database which is searchable on their web site. Keep in mind that not all books have been fully translated, so even if your relative is mentioned in one of the books on their site, their name may not yet show up in the database. You can see which parts of each book have been translated so far, and which are still let to be translated. If you have a lot of family from a particular town that has a Yizkor Book, you might consider donating to the translation expenses for that Yizkor Book to help get it translated faster.

Lastly, I should mention that although many of the books are hard to find, it is possible to buy many of these books, either in used book stores or as reprints. Some specialist booksellers like Dan Wyman Books in Brooklyn, NY, Broder Books in Waterbury, CT, Henry Hollander Books in San Francisco, CA and Book Gallery in Jerusalem carry Yizkor Books, or can help you find them. The Yiddish Book Center, in Amherst, MA, which saves Yiddish books of all kinds has, with the help of Steven Spielberg, created on online library of 11,000 scanned Yiddish books, and also offers a specific service that sells reprints of the Yizkor Books in their collection for $48 each.

New versions of MacFamilyTree and FamilyTreeMaker for Mac

In the past couple of days both MacFamilyTree and FamilyTreeMaker for Mac have received updates.

MacFamilyTree was updated to version 6.0.11 which offers some minor web-output related fixes and some localization updates. You can download the update from their website, and for those who bought it via the App Store presumably it will show up there soon.

FamilyTreeMaker for Mac was updated to version 19.2.1.241 (yeah I don’t understand their numbering system either) and fixes ‘numerous stability issues’ and adds support for the GEDCOM 5.5.1 draft among other fixes. I’m surprised about the GEDCOM update, by which I mean I’m surprised FTM for Mac didn’t already support the 5.5.1 draft which was released in 1999 and has some very important updates like support for Unicode. If you have the retail version, this update should pop up when you launch the program or select ‘Check for Updates…’ from the menu. If you have the version from the App Store, again this will probably show up soon.

I own both of these programs, but do not use them very much because of two factors:

1) It’s hard to switch from one genealogy program to another, no matter how well they support GEDCOM.
2) As outdated as the Reunion is, and how much I complain about it, I still like the general user interface of Reunion and how it displays families in the program.

I’ve written previously about trying to switch to FTM for Mac, but I was unsuccessful mainly because of the difficulty of importing all the media files, and my general confusion over the user interface which I find very cluttered. In addition, I find the Internet features, while appealing, to be very slow.

I haven’t given MacFamilyTree its due I suppose, and many people like, but as I received it as part of a software bundle and didn’t actually buy it directly, I guess it hasn’t gotten enough mindshare from me. One day I’ll have to put it through its paces.

GRAMPS 3.2.5 released for Mac, but not ready for primetime

I really like the idea of an open-source genealogy program. The only real open-source genealogy program that runs on the desktop seems to be GRAMPS. GRAMPS stands for Genealogical Research and Analysis Management Program System. Yeah, I’ll stick with GRAMPS. Originally developed for Linux, it now has versions that run on Windows and on the Mac. I’ve tried it in the past but never really gotten it to work. When I saw a new version released today I installed it and tried again.

Unfortunately, I ran into error messages right from the beginning. I suspect this has to do with running the program on a Mac, a platform they claim to support, but which is not supported very well. After I got past the initial error messages (which prompted me to submit a bug report, but the bug reporter feature led to an error as well) I tried to import a GEDCOM, but found that the Import function didn’t do anything.

I suspect GRAMPS run significantly better on Linux, but alas most people don’t use Linux. As with most open-source projects, the development of the project is directed by those developers who choose to do the actual work. In the beginning, all the developers of GRAMPS were on Linux, and the goal was to create a genealogy program for that platform. It is common sense that under such a situation Linux would be the focus. Over the years GRAMPS has added developers who have chosen to make GRAMPS work on other platforms.

In a recent blog post by one of the developers in response to a post in their own forum about a two-year old blog posting on GRAMPS for Windows, the general ideals of this (and many other) open-source project is revealed, that the developers decide what is best, and if you don’t agree then become a developer for the project and then you can’t have an opinion. In this case, the original two-year-old blog posting was recommending a very specific technical route to take, which I would agree if you’re not going to contribute to the development efforts, is probably a silly thing to do. Developers don’t listen to outside suggestions – they listen to inside suggestions, so even if a developer working inside the project made the same exact technical suggestion, it would be better received than from an outsider. Why a developer decided to bring this up two years later, when the technical issues being discussed are very different than they were in 2008, however, is beyond me.

I would agree with the original sentiment of the two-year-old posting, however, that if you are going to port your application to platforms like Windows and Mac, you should be prepared to use the interface tools available natively on that platform. The look of GRAMPS on the Mac, while familiar to a Linux user, is totally foreign to a Mac user. If I was going to make a suggestion to the GRAMPS developers, it would probably be to look at a cross-platform GUI toolkit like wxPython which lets one use native GUI widgets for each platform, so on Windows the buttons are Windows buttons and on the Mac they’re Mac buttons. If they really wanted to support the Mac natively they could look at PyObjC, but that wouldn’t help them for Linux or Windows, so wxPython is probably a better choice. Of course, I’m not a developer, and I am not offering to become one, so my opinion doesn’t really count here.

The hopefully good news here is that in that same developer blog posting, he says the forthcoming 3.3 version has the best support for multiple platforms GRAMPS has ever had. It’s planned to release in March, so I guess we’ll see then how GRAMPS has improved. When GRAMPS 3.3 is released, I expect to try it again, and post the results here.

Anyone reading this using GRAMPS? I’d love to hear your thoughts in the comments.

[June 27, 2011 – I’ve posted a follow-up to this post on a newer version of GRAMPS, 3.3.0, which is improved in terms of stability, but is not yet ready to use on a regular basis on the Mac in my opinion.]

A sample genealogy folder hierarchy

Genealogy Folder Organization: The B&F System

[This organization system works great on my Mac, in my opinion, but may not work well when using the Windows operating system, which apparently has restrictions on the total length of the file path (path from disk through all the folders and subfolders, plus the file name) that would limit the number of sub-folders you could use. It’s possible to fix this in Windows 10, but I don’t want to recommend something beyond the capabilities of most users.]

When doing genealogy research one tends to collect a lot of documents and photos. There are birth certificate, census records, naturalization papers, passenger manifests, marriage records, death certificates, etc. Keeping track of everything can be a daunting task.

To make matters worse, most genealogy programs will not manage your files themselves. Even if they could, you wouldn’t necessarily want your genealogy program to manage everything, because you might one day want to switch programs, and you don’t want to lock your files into one program. As such, most genealogy programs will link to documents elsewhere on your hard drive. If you organize them well, it’s easy to find them and link them. What happens when you move files around though? That can cause big problems for genealogy programs that are expecting to find a file in a particular location. Different programs deal with this issue in different ways – some will show you which files are missing, some will help you find the files, etc. but in general you want to minimize such issues by putting your files in a place that will not change very often.

I’ve come up with a system for organizing my files that seems to work pretty well for me. It helps me find things quickly, lets me add new folders for new branches of the family without moving other folders and it is flexible enough for me to mix it up a bit if I need to for different situations.

I start with a main folder for my genealogy documents. Let’s call that Genealogy. You want to put that someplace where you know it will not move. I keep it in my Documents folder (on Windows that would be your My Documents directory).

Inside the Genealogy folders called Surnames, Photos, and Documents. In Surnames I create folders with the surnames of each of my great-grandparents, so eight folders in all.

Photos and Documents are not just to dump all my photos and documents, but are special folders where I keep large collections of photos and documents that are not associated with one person. Thus if I scan a hundred photos from a cousin that covered a large portion of my family, I would put those in a folder under Photos. If I retrieve a large batch of vital records from an archive in Poland, I create a folder for those in the Documents folder. In some situations it’s very helpful to keep these kind of collections together in individual folders not attached to one family.

Back to the Surnames folder. So there are eight surnames each with their own folder. You can of course choose to add more surnames. You might want to add a spouse’s surname, either your own or one of your siblings. In the picture below you can see the folder structure I’m describing, and each surname folder is labeled FFF (for Father’s Father’s Father’s) Surname, FFM (Father’s Father’s Mother’s) Surname, etc. Within each of these folders, I again put Documents and Pictures folders and I add one more called Mysteries. Mysteries is for records you find of people that you think are related, but you haven’t found a connection to yet. I just create sub-folders in there with different leads I’m following on different people, so I have a place to keep research that is not linked to my family tree yet.

This is where I do something that might seem confusing, but I then add a folder which is for the oldest known ancestor with that surname (in the diagram I call him/her OAFFF – Oldest Ancestor of Father’s Father’s Father). Within that folder I add folders for each child, and within each of those folders their children, etc. Within each person’s folder I also add a Documents and Photos folder, although with each person I can change my mind on how to organize the folder. With some people I might have a lot of newspaper clippings so that might deserve it’s own folder called Newspapers, and in some folders I might only have a single photo so I might forgo the sub-folders altogether (except for the children’s folders obviously).

A sample genealogy folder hierarchy
A sample genealogy folder hierarchy

Keep in mind that the advantage of this system is that whenever you discover a new child or a new sibling of someone in your tree, you can add them to the folder hierarchy without having to move any other folder. The only time you will need to move a folder is if you discover a relative that is from an earlier generation than your current oldest ancestor. Hopefully you do find new oldest ancestors all the time, but in the scheme of things, it doesn’t happen so often that this should be a major problem.

I usually label a folder that represents the child with that child’s full name and all the name of their spouse. If the child was born Jane Doe and married John Deer, then the folder would be named:

Jane Doe & John Deer

I always put the name of the child first and the spouse second. Of course when there are multiple marriages this can be complicated. In some cases (even without mutliple marriages) I will only name a folder with the person’s name, and then create a sub-folder for the spouse (or more than one folder if there is more than one spouse).

You might be asking, why do you start with the oldest ancestor and work your way down? Why not start with the current generation and work your way up? That would eliminate the need to move folders once you find a new oldest ancestor. The problem is that what happens when you want to add siblings? If I add a folder for myself, and then underneath it I put folders for each of my parents, where do the siblings go? Also, for each generation that I go up I’m splitting surnames. When I move down everyone is a descendant of a single surname. It only works when you’re moving down, which is why you need to start at the top.

There’s probably more to say on this topic, but I’ll stop here for now. I welcome comments on this system, explanations of your own folder organization systems, etc. in the comments.

Religious marriages, civil marriages and surnames from mothers

For many Jewish genealogists, there is a kind of ultimate brick wall of reaching past the institution of surnames around two hundred years ago. Surnames were instituted in different areas at different times, but the Austro-Hungarian Empire, for example, instituted surnames by declaration of their emperor in 1787. When the empire expanded in 1795 absorbing part of Poland, it took in a large Jewish population which were for the first time required to take on surnames. Depending on where they lived, some Jews were not required to take on names for another decade or more after that, so if you have successfully tracked back your family to the point where they adopted surnames, it’s not so easy to reach past that point. There are some patronymic records, which are records that only list the first name of a person and the name of their father, that exist in these areas going further back, and it may be possible to track your family back for a generation before surnames, but that’s really the maximum most people will be able to accomplish if their families did not have surnames earlier (which some rabbinic families did, as did many Sephardim).

Adding to the difficulty of tracking back that far is that many Jews had little use for their assigned surnames in the 19th century. Thus, even though they had assigned surnames which the government used to assess taxes, conscript men into the army, etc., in terms of everyday usage Jews really didn’t care about their surnames. In addition, civil marriage was largely ignored by many Jews, as it generally was expensive. Jews tended to have religious marriages and only got civilly married if they or their children for some reason needed it. This thus lead to many civil marriages long after a couple had their children, something which might seem strange at first glance, but you need to realize thati n most cases these people did get married (religiously) before they had children, they were just not married from the perspective of the state.

So what happened if your parents did not have a civil marriage? In some cases it meant you would need to take your mother’s maiden name as your surname. That’s because even if your father was listed on your birth certificate, he was not legally married to your mother, and thus you needed to take on your mother’s last name for legal purposes. If you parents were legally married at a later date, a note could be written on your birth certificate in the town records showing that your parents were legally married, and thus declaring you as legitimate (and able to take your father’s name).

In the late 19th and early 20th century, civil marriage became easier for Jews, and thus around this time if you look at marriage records you will see a large number of marriages that seem to be relatively old people. In many cases these married couples already had children and grandchildren. As their children and grandchildren became more mobile and wanted to travel out of the small towns they had been in, they needed travel documents, and in some cases this was only made possible if their older parents got married (at least if they wanted to get travel documents with their father’s surname instead of their mothers).

I have a number of examples of children taking on their mother’s surnames in my own family.

In one case two sons took on their mother’s surname when born. One traveled through Europe and eventually ended up in the US, where the passenger manifest for the ship he arrived in the US on shows he and his children still with his mother’s surname. When he became a naturalized citizen a number of years later, however, he had already changed his surname to that of his father (as did his children). The second son moved to Israel, where he kept his mother’s surname. Thus two brothers living in different countries with different surnames.

Another case was utterly confusing for a long time, until I was finally able to put the pieces together. I had the birth record for a woman named Taube Traurig. I had birth records for children of Taube Traurig and a man named Wigdor Kessler. It seemed likely that the Taube Traurig from the original birth record and the Taube Traurig who had children with Wigdor Kessler were the same person. Then I ran into something strange, a death certificate for Taube Traurig (relatively young) before the children were born. This thus indicated either a mistake in the records, or a second Taube Traurig. The problem was that I didn’t have another Taube Traurig in my records that could be the mother (there was another Taube Traurig, but she was the mother of the two sons in the previous example – and a first cousin of the one in this example).

This was a mystery for a long time, until I noticed a notation on the original Taube Traurig’s birth record that had the name Wigdor Kessler on it. That made no sense to me. How could the name of her husband be on her birth record? Not being able to translate the Polish annotation, I posted an image of the birth record to ViewMate, a great service from JewishGen that lets you post an image or photograph and ask for help with translating records or any general problem-solving that you think others can help you with concerning the image. The responses I got indicated that the parents of Taube Traurig had been legally married in 1906, thus making all of their children ‘legitimate’ in the eyes of the state. Wigdor Kessler had signed the records of the couple’s children in 1906 as a witness that they were now considered legitimate by the state.

The person who translated the record for me had said something which stuck with me – he said Wigdor Kessler was not listed as the husband of Taube Traurig in the record. Now I didn’t necessarily think they would require him to state he was the husband, but I also guessed the person telling me this had seen other similar records and if he made the comment, he probably had seen others indicate they were the husband. I also found another record which showed Wigdor Kessler having a child several years later with a Taube Engelberg instead of Taube Traurig. That was utterly confusing since the original Taube Traurig had a sister Sara who had married someone with the last name Engelberg.

So what’s the answer here? The Taube married to Wigdor Kessler was the niece of the Taube in the original birth record. Searching through the marriage records I was able to find a marriage record between Wigdor Schopf and Taube Engelberg after all the children who were born where Taube’s name was listed as Taube Traurig, and before the child was born where she is listed as Taube Engelberg on the birth record. Who is Wigdor Schopf you’re asking? Schopf was Wigdor Kessler’s mother’s name (as shown in the marriage record). Traurig was Taube’s mother’s name. Her father’s name was Engelberg. Thus in all the earlier birth records she had been using her mother’s surname. Wigdor had used his father’s name all along on the birth records of his children, although why he had to use his mother’s surname in the marriage record is not clear.

Thus there were four birth records from 1898, 1900, 1902 and 1904 where Wigdor used his father’s surname and Taube used her mother’s surname. A wedding record in 1905 where Wigdor used his mother’s surname and Taube used her father’s surname. Finally, a birth record in 1910 where Wigdor uses his father’s surname and Taube uses her father’s surname.

What is not clear is why Wigdor was able to use his father’s surname in his childrens’ birth records but not his own marriage record, and why Taube used her mother’s surname in the first four birth records, but then used her father’s surname in her marriage record and in the later birth record. I would surmise that this later Taube’s parents were legally married in between the birth of Taube’s fourth child in 1904 and her marriage in 1905, although I have nothing to indicate that other than her own change of recorded name.

So what lessons have we learned here? If you’re researching your Jewish family in Poland or the surrounding countries, and they were born in the 19th century, don’t assume a person took on their father’s surname. Genealogy programs tend to automatically fill in the father’s surname when adding a child record, thus it’s easy to create a record where you assign the father’s surname even if you have no evidence that the child used the father’s surname. In many cases it might be a safe assumption, but in the case of 19th century Jewish records in Europe it clearly is not a safe assumption.

Two books that discuss some of the issues involved here are Suzan Wynne’s The Galizianers: The Jews of Galicia, 1772-1928 and Alexander Beider’s A Dictionary of Jewish Surnames from Galicia. If you’re asking why I’m pointing to two books that specifically deal with Galicia (a region of the former Austro-Hungarian Empire which currently is partly in Poland and partly in the Ukraine), it’s because the issues discussed here were particularly prevalent in Galicia, and as a big chunk of my family originates in Galicia, it’s also the area I know the most about (and of which I know about relevant books).

If you’ve had similar stories of relatives taking on their mother’s surname, please add your stories in the comments.