The following transcript and slides were part of a lightning talk at the Museum Computer Network conference in San Diego, November 2019.
Every day when I go to work, before I check my email or start coding or talk to my supervisor — the first thing I do is dive into the chat forums, or Talk boards. I’m not slacking off — I’m the project coordinator for Scribes of the Cairo Geniza, a crowdsourcing project led by Penn Libraries and the Zooniverse.
This project seeks to identify, classify, and transcribe medieval Hebrew and Arabic fragments once located at a historical synagogue in Cairo, Egypt. These fragments are now located in libraries around the world, from St. Petersburg to Cambridge to Los Angeles, and virtually all of them have been digitized. Over two years, we’ve mobilized nearly 8,000 people in reviewing over 50,000 fragments. Our site includes Arabic, Hebrew, and English interfaces for the world to participate.
This project in itself could be an entire lightning talk, but what I want to focus in on here are the Talk boards. That’s where I spend a lot of my time. Most Talk boards for crowdsourcing projects are used for troubleshooting issues, or specific help questions. But the volunteers in this project have made use of the Talk boards to create their own classifications systems, work together to teach each other, and generate conversations about Jewish history and culture, linguistics, and the work of libraries in the preservation of materials. We have participants commenting on the Talk boards in all three languages of our project. And with all of these people talking to each other, it’s made me think about what fostering public participation in research really looks like once you have a crowdsourcing project up and running.
So I want to show you two examples of what I mean. For volunteers who don’t read Hebrew or Arabic, visual features on these fragments are often striking — like this alama, outlined in the red rectangle in the corner. This visual characteristic is important to understanding and identifying fragments, but there aren’t nearly enough of them for our research team to make it a task or question in the project.
But volunteers started noticing an alama here or there, and one volunteer contacted me, asking if they could have a list of all the fragments in the project. So we said yes, handed over our data, and in about two weeks they came back with a tag, a definition for our glossary, and a collection of fragments they identified as definitely having an alama or possibly having the feature.
And the takeaway from this moment was that it demonstrated user participation in project-level research, trusting engaged volunteers with tasks — helping them on their way to achieving researcher status. They’re asking questions like a historian, so why not help them on their way?
On the other side of things, sometimes volunteers are interested in questions our team hasn’t spent a lot of time thinking about. Volunteers generated dozens of tags related to art, doodles, decorations, or drawings. And one volunteer was so impressed by the variety of artwork, she asked others to join her in creating a collection. So I reached and supported her, sharing all of these tagged fragments — and she, in turn, developed item-level metadata describing what she saw.
And as she did this, and wanted to promote what she found, our team shared the fragments & descriptions on social media — which wound up back in the hands of our project partners, amazed by things in their collections they hadn’t known existed before.
Which takes me to the other side of the spectrum: opening your collection to answer the research questions you intended is one thing, but following user-generated research can help spark new interests that we haven’t even begun to ask as teams or institutions.
So crowdsourcing projects are certainly not new to museum professionals at this point, and they are a great space for public participation in research. But having this open dialogue space, where people feel empowered to write in their languages, ask questions, and take on responsibility in a project supports that work is what takes this unique project to another level. It’s helped our project grow into a space of learning, communication, and collective ownership of the data that’s created. It takes a lot of investment on our team’s end to be responsive, in-the-know, and OK with sharing things in-progress, but it’s also incredibly rewarding to see how volunteers can inform, develop and transform a project over time.
Exported from Medium on April 14, 2020.