Category Archives: Conference

An experiment in collaborative genealogy

July 9, 2018Conference, Okopowa, Researchcemeteries, collaborative genealogy, Okopowa St. Cemetery, photographs, WarsawPhilip

While making my plans for the upcoming IAJGS International Conference on Jewish Genealogy in Warsaw, I came up with an experiment I’d like to try. This experiment needs dozens, if not hundreds, of volunteers to pull off successfully.

The short version is I’m organizing volunteers to photograph and geocode all the gravestones in the Okopowa St. Cemetery in Warsaw, and then upload those images to both BillionGraves as well as to special groups on Flickr when they will become available to everyone to use.

There are probably over 80,000 gravestones in the cemetery, and while I don’t expect we’ll be able to get to all of them by the time the conference ends, the simple effort to do so will be an incredible experiment in collaborative genealogy.

For full details on this experiment, and how to get involved, please go to the Okopowa St. Project page.

As of August 31, 2018, I’ve moved the original text of the Okopowa St. Project page to this post, so we can keep it for future reference. The Okopowa St. Project page itself will continue to point to all related articles, and give the status of the project as we seek to improve the collection of genealogy data in cemeteries.

Original Project Text:

An experiment in collaborative genealogy

Like many people planning to attend the upcoming IAJGS International Conference on Jewish Genealogy in Warsaw this August, I’ve been trying to figure out my schedule, see when I’ll be at the conference, and what else I can do to take advantage of the fact that I will be spending a week in Warsaw, Poland.

One place I have been planning to visit is the Okopowa St. Cemetery, which I last visited 25 years ago while visiting Poland as part of the March of the Living. Most of the photos from my popular article Jewish Gravestone Symbols come from the Okopowa St. Cemetery, and I’ve long wanted to re-visit it.

The Okopowa St. Cemetery is one of the largest Jewish cemeteries in the world, and certainly is the largest surviving cemetery in Poland. As I contemplated my visit I realized that there was an opportunity to attempt something that might not be possible again any time soon. What if large numbers of conference attendees, many of who may already be planning to visit the cemetery, could collaborate in documenting all the gravestones in the cemetery? BillionGraves only has 226 photographs for the entire cemetery. Yes, I know there’s an excellent database on the Foundation for Documentation of Jewish Cemeteries (FDJC) site for the Okopowa St. Cemetery.

It’s probably best to think about this as an experiment in collaborative genealogy.

You can also think of this as an art project.

We don’t need to complete the project during the conference, it’s enough to see how far we can get. Part of the experiment is seeing exactly how much can be done.

Other visitors and locals in Warsaw can finish the project if we make a dent in it during the conference.

In the end, if we’re lucky, we’ll have geocoded high-resolution photos of all the graves, and the photos will be available for everyone to use in whatever projects they want to use them in. If the FDJC wants to add these photos to their site, they can. If JOWBR wants to include them, it can also do so. I’ve set up a series of steps, outlined below, which will make these photographs accessible and useful to the most people. If this succeeds, I hope people will use this model for other genealogy projects.

Some of the things I’m hoping to find out include if the tools are the best ones to accomplish these tasks, if leaving the groups open to all, and the Google Sheet editable by all, works, or if people will abuse those freedoms. Is it too complicated to upload photos to two different sites? This will be a learning experience, whose lessons we will be able to apply to future projects.

Here’s how this will work. Volunteers will install two apps on their smart phones – BillionGraves and Flickr. They should also make sure they have accounts set up for both BillionGraves and Yahoo (the owner of Flickr), and configure the apps so that they are connected to their accounts. For BillionGraves, make sure to have the Save to Camera Roll option selected in your preferences if you use an iPhone. You’ll need that later to allow you to upload the photos to Flickr. For Flickr, log into your account on the web and set the default license to “Attribution-ShareAlike Creative Commons”. This is important, as it will allow these images to be used by anyone who wants, but still requires them to attribute the photograph to you.

Volunteers will choose one section to photograph (larger sections will need multiple volunteers). There is a Google Sheet to coordinate volunteers. Take a look and add your name to a section. The volunteer should join the group on Flickr for the section they’ve chosen (the links to those groups are in the Google Sheet, and below). For larger sections with many volunteers, the volunteers should use the discussion area of the group on Flickr to figure out when they will be photographing, and try to divide up the work.

When volunteers go to the cemetery, they will go to the section they’ve selected, and photograph all the graves in that section, or whatever part of it they can. They will photograph the graves using the BillionGraves app, and upload all the images to the site (this can be done later at the hotel using the free WiFi. In this first step, all the photos will be accessible via BillionGraves. In addition, when you’re done, you will go to the Flickr app and upload your photos to Flickr, and when they’re on Flickr, you will then share them to the appropriate group for the section they were taken in. You should then go to the discussion area for that group, and post how many photos you’ve shared to the group, if it was all of the graves, or if there is still more work to be done (and to the best of your ability describe what areas still need to be photographed).

At this point, if you want, you can delete the photos from your phone. Make sure, however, that the photos have been uploaded to both BillionGraves and Flickr before deleting them.

Let’s go over this once more, in clear order:

Before going to the cemetery:

Join our Facebook group Okopowa St. Project to discuss the project, and share your experiences with other volunteers.

Set up BillionGraves:

Set up an account on BillionGraves. If you already have an account on BillionGraves, login through this link so they know you’re involved in this project.
Sign up for the BillionGraves Event for this project.
Download the BillionGraves app for iPhone or Android.
Connect the BillionGraves app on your phone to your account.
If you use an iPhone, go to Preferences in the BillionGraves app on your phone and turn on ‘Save to Camera Roll’.

Set up Flickr:

Set up a Flickr/Yahoo account.
Set your default license for photos to “Attribution-ShareAlike Creative Commons”.
Download the Flickr app for iPhone or Android.
Connect the Flickr app on your phone to your account.

Select a section to photograph:

Look at the map above (click to zoom in) to get an idea of where the sections are in relation to the entrance, and how big they are.
Go to the Google Sheet and see which sections already have volunteers. Select a section that has no volunteers and add your name in the left-most volunteer cell for that section.
Click on the section name in the Google Sheet, or find it below, and go to the Flickr group for that section and join it. All discussion for that specific section will take place in the Flickr group.
In the Flickr group, post an introduction in the discussion list, and explain when you plan to photograph the section.
Print out a copy of the map, and circle the section you will be photographing. Make sure to bring it with you to Warsaw.

Preparing to go to the cemetery:

Double-check that BillionGraves is properly configured.
Make sure you have enough room on your phone to fit all the photos you’re about to take. If you need to clear up your phone to make room, do so.
Charge your phone fully. If you have an external battery, make sure that it charged as well and bring it with you. You don’t want to be in the middle of a section and have your battery die.
Check the group on Flickr for your section, and see if there is any discussions you missed. Did someone already photograph that section? Is there part this is incomplete? Check before you go because you may or may not have Internet in the cemetery.
Bring paper and pen so you can take notes, sketch the layout of the section if you want, etc.
Make sure to wear pants and appropriate shoes. The cemetery is overgrown, and you don’t want to hurt yourself.

At the cemetery:

When you arrive at the cemetery, make your way to your section, and figure out an appropriate path to photograph all or as many graves as you can. Take extra photos that show the paths, the lines of gravestones, whatever. You can take these photos using your standard camera app.
Make your way to each gravestone, and take multiple photos of each. Get one that shows the whole gravestone, and another that frames just the text on the stone. If you think you need more than one photograph of the text for it to be clear, take more than one. Don’t limit yourself. Check the back of each grave in case there is more text.

After the cemetery:

Upload your photos to BillionGraves. Try to group the photos of each grave together. Skip the general photos of the area, as those are not useful for BillionGraves. Make sure all the photos fully upload to BillionGraves before leaving the app.
Upload all your photos to Flickr, and then Share them to the appropriate group for your section. If you photographed more than one section, make sure to upload the photos to their appropriate sections. Make sure everything fully uploads before leaving the app.
Post to the Flickr discussion area for your section’s group and explain how many gravestones you photographed, how many photos you uploaded, and if there is anything more for others to photograph. Do this even if you’re the only person in the group, as it will be there for future reference. You can even post immediately after taking the photos, and then follow up after you upload them (in case there’s a significant gap between those events). That will keep everyone informed as to what is going on.

The table showing the links to the Flickr groups for each section is below. I hope if you’ve made it this far, you are considering joining this collaborative effort.

Thank you.

Flickr Groups for Okopowa St. Cemetery Sections
Section 1	Section 1A	Section 1L	Section 2
Section 2A	Section 2B	Section 2C	Section 3
Section 3A	Section 4	Section 4A	Section 4B
Section 5	Section 5A	Section 6	Section 7
Section 8	Section 8A	Section 9	Section 10
Section 11	Section 12	Section 13	Section 13A
Section 14	Section 15	Section 16	Section 16A
Section 17	Section 18	Section 19	Section 20
Section 21	Section 22	Section 22A	Section 23
Section 24	Section 25	Section 26	Section 27
Section 28	Section 29	Section 30	Section 31
Section 32	Section 33	Section 34	Section 35
Section 36	Section 37	Section 38	Section 39
Section 40	Section 41	Section 42	Section 43
Section 44	Section 44A	Section 44B	Section 45
Section 46	Section 47	Section 48	Section 49
Section 50	Section 51	Section 52	Section 53
Section 54	Section 55	Section 56	Section 57
Section 58	Section 59	Section 60	Section 62
Section 63	Section 64A	Section 64B	Section 65
Section 66	Section 67	Section 68	Section 69
Section 71	Section 72	Section 73	Section 73A
Section 74	Section 75	Section 76	Section 77
Section 78	Section 79	Section 80	Section 83
Section 84	Section 85	Section 86	Section 87
Section 88	Section 89	Section 90	Section 91
Section 92	Section 93	Section 94	Section 95
Section 96	Section 97	Section 98	Section 99
Section 100	Section 101	Section 102	Section 103
Section 104	Section 105	Section 106	Section 107

For photos that are not in one of the above sections, there is a general group for this project here.

What DPI should I scan my photos, and in what format do I save them?

July 12, 2015Software, Conference, Technicalconference, insta, negatives, photographs, scanning, slidesPhilip

My lecture Preserving Photographs, Scanning, and Digital Backups at this weeks’ IAJGS International Conference on Jewish Genealogy was well attended with somewhere around 150-200 people. While I can’t post the video of the presentation on my blog, I do want to share some of the information from the lecture here.

The two most common questions I get about scanning photographs are:

1) What DPI do I need to scan my photo?
2) What file format should I save the file in?

DPI stands for dots-per-inch, and refers to how many pixels are present in each inch of the photograph. For example, if you had an 8×10 inch photograph, and you scanned it at 100dpi, you would have a photo that was 800×1000 pixels, or 800,000 pixels altogether. That’s less than a million pixels, or another to say it is it is less than a megapixel. Doubling the DPI to 200dpi, gives you 1600×2000 pixels, or 3,200,000 pixels, or 3.2 megapixels. Note that doubling the DPI effectively quadruples the number of pixels, since the dpi increases in both vertical and horizontal directions.

Here’s another way to look at, in a slide from my presentation:

Basically, if you look at scanning photographs (or negatives/slides) you can see that scanning it at 300dpi for different sizes will give you much different size images. I have a rule-of-thumb that I use to determine the correct DPI to scan at, and basically it has to do with figuring out the largest size you want to be able to print (printing is usually done at 300dpi) and then adjust your scanning dpi to insure you’ll have enough pixels to print. Here’s the summary:

For people reading this on a small screen where the image is hard to read, the basic rule is:

Minimum resolution (DPI) should be the number of inches of the largest side you want to print, divided by the largest side in inches of what you’re scanning, multiplied by 300.

So if you are scanning a 4×5 print, and want to be able to print at 8×10, you need twice the DPI you’ll print at, so 600dpi. Of course, it doesn’t hurt to scan more than you need, although there are diminishing returns. Not all photographs are high enough quality to give you a better picture when scanned at very high resolution.

A Kodachrome slide supposedly has enough resolution to output about 20 megapixels. That means you can basically max out a 4000dpi slide scanner and get a good result. That said, a small old print with lots of grain probably wouldn’t benefit by going beyond my rule of thumb, and some likely could be safely scanned at a lower resolution.

Storage is cheap though, so I say scan as high a resolution as you want, and use my rule of thumb as the minimum guideline.

So once you’ve figured out what resolution to scan in, what format should you save it in?

The short answer is TIFF. TIFF was actually designed early on for the purpose of scanning photographs. TIFF also, for the most part, does not lose any data in the file format, unlike formats like JPEG which always compress data in a lossy fashion (I say for the most part because it’s technically possible to use JPEG compression in a TIFF file, but it’s rare, and I doubt any scanner software you would use is going to do that). You can scan to TIFF format using LZW compression that is lossless (i.e. does not degrade the photo quality). TIFF is also good because it is so widely supported, and is used by archives and libraries for their own scanning, and is unlikely to become unsupported by future software.

PNG is also a good format for scanning. It’s a more modern format, and offers built-in lossless compression. It’s not as widely supported, but if space is at a premium, it might save you a bit over TIFF.

JPEG is not a good format for scanning, because it a lossy compression format, and you will always lose some data when saving to a JPEG, even if you save it at 100% quality. I sometimes scan to both TIFF and JPEG, as JPEG can be easier to share sometimes, but I am sure to have the TIFF file as well.

PDF is not a good format to scan photographs with, as you have no control over how images are compressed, and editing them is much more difficult than TIFF or PNG. In general, PDF files will actually use JPEG compression anyways, without being able to even set the quality. If you’re scanning a multi-page printed document, you can use PDF as a convenient way of sharing it, but if there are photos and other important content in the document, I would suggest scanning it as a TIFF as well. It’s not well known, but TIFF also supports multi-page documents, just like PDF.

If you have additional questions about scanning photographs, please post them in the comments below.

Some thoughts on day one of #IAJGS2015

July 7, 2015Conferenceconference, IAJGS, Mogador, Morocco, prenumerantenPhilip

Yesterday was day one of the IAJGS International Conference on Jewish Genealogy in Jerusalem. The last time the annual conference was in Jerusalem was 11 year ago, and that was the first genealogy conference I attended. Back then I was less involved in genealogy, although I did volunteer to put together the Souvenir Journal given out to attendees (still available online).

It’s interesting to look back at that journal and notice that there are two letters of approbation at the beginning of the journal, written by then Israeli President Moshe Katsav and then Jerusalem Mayor Uri Lupolianski. Lupolianski was, if I recall correctly, the keynote speaker that year as well. What’s interesting about those two Israeli leaders is that both currently sit in jail – Katsav on rape and sexual harassment charges, and Lupolianski on corruption charges. I suppose that should be disheartening, although on the plus side I guess we can be confident that no one is above the law here in Israel.

This year the keynote speaker was Rabbi Yisrael Meir Lau, the former Chief Rabbi of Israel (and father of the current Chief Rabbi). I think he’s above reproach, perhaps the conference organizers wanted someone they could be sure wouldn’t be in jail by the next conference here (although interestingly enough, the rabbi that served for 10 years in between Rabbi Lau and his son is currently in jail, on corruption charges).

Rabbi Lau’s story is quite amazing (I highly recommend his autobiography Out of the Depths), being one of the youngest survivors of the Buchenwald concentration camp (I believe he was 8) and ending up in Israel where he rose to be Chief Rabbi. He is a charismatic speaker, and I think well received by everyone there.

Earlier in the day I spoke on the topic of Jewish Names, Red Herrings and Name Changes. I was happily surprised to be talking to a packed room.

Speaking at IAJGS 2015 — (Thanks to my friend Jay Solomont for taking this photo)

I hope to publish a summary of my lecture sometime in the future. I made one mistake in my lecture, but I’m glad no one picked up on it…

I also attended several lectures which were excellent. One lecture which I almost missed, but was happy to find at the last minute, was a lecture titled Who Were The European Jewish Refugees in Casablanca During World War II and How Did They Get There? given by Michal Ben Ya’akov. The lecture centered around the work done by Helene Cazes Benatar, a lawyer working in Morocco during WWII, who helped Jewish refugees who flowed into the country from Europe.

Among the thousands of refugees in Morocco during the war was my grandmother, and six other female relatives who fled from France on a banana boat, ending up in Mogador, as the current city of Essaouira, Morocco was known at the time, when it was still a French protectorate. The story of my family’s stay in Morocco has always been something I’ve wanted to investigate further, and I hope to be able to find information on my family in the records Ben Ya’akov discussed in her lecture.

Another interesting lecture was on the topic of prenumeranten. The lecture was given by Yehuda Aharon Horovitz, and he discussed the topic in great detail. In the past, I’ve described prenumeranten as the Kickstarter of the 19th century publishing business. While writers today can crowdfund their books in advance online, the model is actually quite old, although it was much more labor intensive. Back then, a writer might travel from town to town and take advance payments on books, to enable him to have funds to do the work and to print and mail the books out. This was a very popular method for writers of Jewish religious books. In some cases, the author himself wouldn’t travel to collect money, but rather he would hire someone as a middle-man to travel from town to town, collect money, and then bring him the list and the money (after taking a cut obviously). This isn’t so different than what happened in the secular world, where salesmen might travel from town to town selling encyclopedias. Dictionaries were sold in advance and volumes mailed out as they were completed. In the case of the Jewish books, however, the list of pre-purchasers would be printed in the first edition of the book, usually sorted by town. These name lists might sometimes be the only lists of names that exist for a given town at a specific time, and thus can be very useful.

A fellow researcher, whose shares cousins with me, exposed me to prenumeranten a couple of years ago. RYT, as I’ll call him, since I’m not sure he’d want his name online, did some amazing work finding relatives of ours in these prenumeranten. I’ve intended to write an article just about his work at some point, and now seeing this lecture has given me the encouragement to get back into that research. I learned about new resources that I wasn’t aware of, and am hopeful that Horovitz’s goal of getting all prenumeranten lists scanned and indexed, and made searchable online, will come to fruition.

I’m looking forward to the rest of the conference.

Typical name distribution? A preview of my lecture on Monday.

July 5, 2015Conference, Namesconference, Engelberg, Kessler, names, Schopf, surnames, TraurigPhilip

The following is a slide from my lecture on Monday in Jerusalem at the 35th annual IAJGS International Conference on Jewish Genealogy. My lecture is titled “Jewish Names, Red Herrings and Name Changes” and is taking place at 10am. This slide is about mid-way through my lecture, and takes a look at a family with confusing naming patterns (and is subject to change by Monday).

It’s a little hard to follow without some introduction in the previous slides, but in short there are two Taube Traurigs, including one who married a Schopf but was never named Taube Schopf.

There’s an actually Taube Schopf, whose father was a Wigdor Schopf. Her married name was Taube Engleberg, which is what the other Taube’s name should have been at birth (but wasn’t).

There are actually two Wigdor Schopfs, one married to a Taube, and one the father of a Taube.

The son of Taube Traurig and Wigdor Kessler was named Ephraim Engelberg. It all makes sense really.

Have your own confusing name stories? Share them in the comments.

Want to hear more and are in Israel? Come to my lecture on Monday. Details on the Facebook event page for the lecture. If you’re going to attend and use Facebook, please sign up on the event page.

Attending and have a question about Jewish names? Send me a message before Monday and I’ll try to include the answer in my lecture.

Attending the Int’l Conf. on Jewish Genealogy in Jerusalem this summer?

May 4, 2015ConferencePhilip

Will you be attending the International Association of Jewish Genealogical Societies (IAJGS) International Conference on Jewish Genealogy (seriously, they need a shorter name) this summer in Jerusalem? I will be giving two lectures at the conference:

Jewish names, red herrings, and name changes
Monday July 6, 10:15am

Preserving Photographs, Scanning, and Digital Backups
Thursday, July 9, 2:00pm

The links for each lecture above go to Facebook events I’ve set up for each lecture. If you are going to be at the conference and plan to attend a lecture, you can join the event now if you’d like. Even if you cannot attend, please feel free to go to the event on Facebook and ask questions on the topic of the lecture, and I will try to respond.