Featuring Ben Deitch, Engineering Fellow

By Elizabeth Mays & Mek

Open Library is powered by a global community of volunteers, a small team of staff, and several extraordinary, handpicked volunteer fellows who are picked to work alongside staff to tackle ambitious, high impact projects. This week, we’re featuring the work of Engineering Fellow Ben Deitch, who has made a dramatic impact on the Open Library initiative since 2024. 

Ben’s numerous engineering contributions have strengthened Open Library’s experience for hundreds of thousands of patrons. With the mentorship of senior staff engineer Drini Cami, Ben wrote code that enables patrons to:

  • Find exact book editions from their Reading Logs
  • Search which books were read within any given year
  • Discover interesting books based on a sophisticated reddit-style trending algorithm
  • Query for books, even when the search may contain typos
  • Mark books as “Want to Read” from author pages

Prior to Ben’s work, reading logs would show works instead of editions. Ben added the ability to view editions on a reading log. This enables users to track the precise editions of books they have read. The log will also show the right cover for each edition. 

Ben also implemented a basic “fuzzy search” for the Solr Search engine, making the overall search system much more tolerant of spelling errors and bringing it closer to modern standards for search engines so that patrons don’t hit dead ends. 

In another project, Ben coded in a new, image-based preview for user created book lists, which appears on users’ My Books pages. This feature also enables patrons to see the first few books in a list at a glance. 

Ben can also be credited for enabling the “already read” books to be viewed by the year in which they were read

Historically, search results and book pages have featured a “Want to Read” button that patrons can click to keep track of books of interest. Ben extended book results so patrons can also click “Want to Read” from the author’s page.

In the past, when carousels were rendered for the homepage, facets were included – like language – that were accidentally being dropped when additional results were loaded. Ben fixed this issue so books results were relevant even when loading multiple pages.

Finally, Ben fixed an librarian issue to alter the display message after the merging author entries so merging two author records no longer show as successful when there was actually an error

Ben’s work can be found across the Open Library – from the search page, to the home page, the author’s page, and the my books page. We are grateful to Ben and couldn’t be more proud of his contributions to our Open Library.

You can send Ben kudos here on LinkedIn!

A Community-Curated Nancy Drew Collection

A team of volunteer Open Librarians have worked together to organize the many Nancy Drew book series into a beautiful collection on Open Library

If you’re excited about this collection, you can direct your thanks to Open Library volunteer Emily, who proposed the project. A few months ago, Emily put out a call in Open Library’s librarian Slack channel to see if other librarians might be interested in teaming up. Today, the collection is live and ready for the benefit of the public.

A collaborative approach was second nature for Emily, a librarian and educator who recently completed a Master of Information program. 

“Almost all of our projects were group work to help prepare us to work together and collaborate in libraries,” she said.

To organize the project, Emily built a detailed Google Document with information, ideas, questions about methodology and choices the team would need to make as a group. Participants added thoughts and notes asynchronously before the call.

An initial Zoom call then brought the team of volunteers together in real time. The call was held in a time zone that worked for the international contributors, who came from Tokyo, Pakistan and the western U.S.

“I think it was really important to do a video call to start things off, just to really just humanize everyone,” Emily said. “Like you see everyone a little bit, you hear their voices, you know that you’re working together. You know that you’re a team, and that helps everyone stay motivated.”

Maahin, located in Pakistan, worked on two series of the collection, Nancy Drew and the Clue Crew and Nancy Drew Notebooks. She had long wanted to become a librarian. “Being in a place where there’s no scope of reading and related professions, Open Library is the best chance to contribute in book-related tasks, and it motivated me finding you can contribute to it remotely,” she said.

On the kickoff call, contributors aligned on preliminary decisions, discussed how to divide the work and shared their reasons for contributing.

How best to build the collection required some sleuthing. Contributors explored various methods to build collections and tag large numbers of works. They considered using Python scripts to automate finding books and adding metadata, but determined the approach was impractical given the extensive metadata cleaning and large-scale review this project required, combined with limitations in their current technical expertise. In addition, they experimented with alternative versions of the current carousel code. However, they found that these new versions would result in a lag when users loaded the page. Contributors wanted to make sure the collection would be accessible to anyone, regardless of their Internet speed.

Because this was such a large collection with so many different series, Emily checked behind the scenes to learn how similar collections in Open Library had been built. 

With that info in view, a decision was made to manually tag books’ subject fields with a collectionid: tag for each series. 

Nichole, who focused on the Nancy Drew: Girl Detective and Nancy Drew on Campus series of the collection, joined the project out of a desire to learn.

“I was new to the Open Library and wanted to learn how to create collections and hone my metadata editing skills,” she said “I also noticed that we had a Hardy Boys series but not a Nancy Drew series, which felt like a gap.”

Working on metadata taught Nichole about source verification. Most of her previous metadata assignments involved checking single documents or websites, so she assumed the task of editing metadata for a series of books would be straightforward. But this project required evaluating and aggregating information from multiple sources. 

“It was surprisingly challenging to confirm basic facts (like how many editions of a Nancy Drew book exist and how they were published) and find reliable information.”

Another volunteer, Liz, consulted portions of the book, “Girl Sleuth: Nancy Drew and the Women Who Created Her” by Melanie Rehak. The biography identified another of the major challenges for the collection–many of the Nancy Drew books in Open Library had been attributed to the wrong ghostwriter, instead of the pen name Carolyn Keene. The pen name refers to numerous ghostwriters across different works and editions of the books (such as reissues). But most of the books in the library attributed the wrong ghostwriter as the author. 

Lead Staff Librarian Lisa Seaberg helped to correct conflated author metadata, a common issue when a pseudonym is shared by multiple authors and when multiple authors have the same name.

The collection as it stands represents many hours of metadata cleanup from each of the contributors. 

For future groups collaborating on collections, Emily suggests live-demo-ing how to edit the metadata before asking people to do it. “I think we all had to go on an individual journey of reading the documentation and figuring out how to do it,” Emily said. 

Contributors each had their own reasons for helping to bring the Nancy Drew collection to life. 

“For me, there’s definitely some nostalgia,” Nichole said. “I grew up during the era of Nancy Drew PC games and remember playing Nancy Drew: The Phantom of Venice. But I also appreciate Nancy Drew as a character. Growing up, I read a lot of detective fiction and became familiar with detectives like Sherlock Holmes, Hercule Poirot, Miss Marple, S. S. Van Dine and Hajime Kindaichi. Nancy Drew feels unique — not just in age and life experience but also in personality and technique.”

Emily grew up on a small dairy farm in rural Canada, without access to many TV channels. “It was just so nice to have these stories that I could access — this huge wealth of narratives about a woman who was really curious,” Emily said. “It was just a really good role model for me growing up.”

Maahin joined for the chance to do library work. “I am excited to work on all kinds of tasks including documentation and cataloguing and every other thing that is related to books and library,” she said.

Work on the collection and cleanup of metadata in the current collection is still ongoing, with continuing opportunities to contribute. Some of these include adding series tags or special featured collections, such as the books that inspired the Nancy Drew computer game series.

Emily also aspires to make the books appear in order in the series. (Currently the order is tied to the date of the most recent edition.) “If we could find a developer who can find a solution to help us make all these books appear in order in the series, that would be wonderful,” Emily said. 

The project took months from start to finish. The work to clean metadata and get the first eight series of 500-plus books into the collection was substantial, but rewarding.

“It was work to learn how to do it, but it is so satisfying to have built something and help share the things that helped you have a love of reading with other people,” Emily said. “And it’s been really wonderful to connect with similarly minded people as well.”

If you would like to contribute to this or future collections projects at Open Library, fill out this volunteer form.

Image of a few series in the new Nancy Drew Collection on Open Library. Shows carousel selections from Nancy Drew on Campus and Nancy Drew Girl Detective.


Lessons Learned:

  • How to Build Collections: For now, manually tagging books’ subject fields with a collectionid: tag for each series, and copying the code from past multi-series collections, is the most expedient way to build a collection.
  • Human Connection Matters: Meeting fellow librarians, combined with defined asynchronous processes, can help a collaborative project go smoothly. 
  • Live Training Could Save Time: Future projects would benefit from a short live demonstration of metadata editing at the outset. This could reduce the learning curve and help volunteers feel confident contributing sooner.

Celebrating Our Community in 2025

Highlights From the 2025 Open Library Community Celebration

This year, staff, fellows, and volunteers made a number of improvements to Open Library. Here are some highlights of contributors’ accomplishments in 2025, as presented in the annual Community Celebration.

  • Ray Berger, volunteer Developer Experience Lead celebrated his fifth year with Open Library, having reviewed and merged more than 100 pull requests in 2025. This year Ray launched https://docs.openlibrary.org, a new searchable portal for developer documentation. To improve website performance, Ray upgraded the Open Library Search APIs to use FastAPI, a more performant, modern web framework. He has also helped modernize the code base to make it easier for developers to contribute. 
  • GSoC Engineering Fellow Sandy Chu worked with staff members Drini Cami and Mek to enable on-the-fly translations in BookReader. Now, books in BookReader can be translated into more than 40 languages. This project also enabled read-aloud capabilities in BookReader, which helps to close the accessibility gap for international readers. 
  • Engineering volunteers David Ragipi and Krishna Gowsami redesigned book lists to add a “follow” button next to usernames. The feature increased the number of patrons following each other from 182 to more than 3K followers in 2025.
  • Under Mek’s mentorship, GSoc Engineering Fellow Roni Bhakta developed a prototype of Lenny, a self-hostable digital library for storing and lending EPUBs. Lenny gives libraries and individuals a lightweight way to host and securely lend the EPUBs they own.
  • Engineering Fellow Ben Deitch worked with Drini to develop a new trending algorithm built on Solr that uses hour-by-hour statistics to give patrons fresh, timely books that are getting high interest at any given moment on Open Library. This feature replaced trending views that changed infrequently and also gives insight into what’s trending in a given subject.
  • Engineering Fellow Stef Kischak worked with Drini to develop a script that scrapes Wikimedia APIs for Wikisource ebooks to import. Stef also made efforts to improve the import pipeline and identify orphaned editions to edit.
  • Librarian Fellow Jordan Frederick imported reading levels metadata that improved the K-12 reading collection. Jordan also fixed metadata, split wrongly merged records, and created tutorials for Open Library patrons. 
  • New librarian volunteer Catherine Gosztonyi created the still-growing Canada Reads Awards collection on Open Library. 
  • Internet Archive Staff Member Lisa Seaberg celebrated the 684 volunteer librarians in the Open Library community Slack channel. Volunteer librarians improve the catalog by adding metadata, author info, images, and collections. Lisa also recognized multiple superlibrarians who reviewed hundreds of thousands of merge requests, curated special collections, and mentored librarians in training.
  • Volunteer communications lead Elizabeth Mays, with team Nick Norman, Ella Cuskelly, and Jordan Frederick, doubled the number of blog posts published in 2025 and streamlined a process for writing and approving blog posts. The group also defined standard starter tasks for future volunteers toward projects that will enable more frequent social content. 
  • Staff member Drini Cami highlighted the work of the developer community on a unified read button, language-aware autocomplete and carousels, full-text list search, new librarian features, Wikipedia links on author pages, and Wikidata integration. Drini presented staff improvements such as a data-quality tool that lets librarians see which popular books are missing metadata, streamlined special access for patrons with qualifying print disabilities, grid view, and security improvements to prevent cyberattacks. 

Watch the replay of our 2025 Community Celebration or these slides to learn more about these upgrades. 

Previous Community Celebrations

This is Open Library’s sixth Community Celebration to recognize contributors, who come from more than 20 countries. Catch up on past years’ events at these links:

2024, 2023, 2022, 2021, 2020

Get Involved

If you’d like to get involved, indicate your interest in volunteering with Open Library in this interest form. We’ll be in touch to connect you to the community Slack and weekly call. 

The result of implementing a change which lowered the quantity but increased the quality of sign-ups.

Achieving More with Less

Setbacks: 2025 has been a challenging year for the Open Library community and the library world. We began the year by upgrading our systems in response to cybersecurity incidents and fortifying our web services to withstand relentless DDOS (distributed denial of service) attacks from bots. We developed revised plans to achieve More with Less to meet the needs of patrons who lost access to 500,000 books due to late-2024 takedowns. The year continued to bring setbacks, including a Brussels Court order, which resulted in additional removals, and contesting thousands of spammy automated takedown requests from an AI company. Just last month, we responded to a power outage affecting one of our data centers and then a cut that was identified in one of our internet service provider’s fiberoptic cables, resulting in reduced access.

Given all these setbacks, why weren’t we seeing a decline in sign-ups?

Less is More: Putting patrons’ experience first. As the year progressed and we reviewed our quarterly numbers, one metric that circumstantially held high was sign-ups. The Open Library is historically a significant source of registrations for the Internet Archive, contributing to approximately 30% of all registrations. Some websites may have found it reassuring that, despite all the challenges presented in 2024 and 2025, adoption seemed to keep its pace. At the Open Library, we measure success in value delivered to readers — not registrations — and this trend seemed to indicated something may have become out of balance:

What reason(s) might explain why registrations remain steady when significant sources of value are no longer accessible?

We hypothesized some class of patrons are signing up with an expectation and then not getting the value they are expecting.

Testing the hypothesis: The first step of our investigation was to take inventory of the possible reasons one might register an account. Each of the following actions require accounts:

  • Borrowing a book
  • Using the Reading Log
  • Adding books to Lists
  • Community review tags
  • Following other readers
  • Reading Goals

Supporting Evidence: We started by reviewing the Reading Log because it’s the platform’s largest source of engagement, with 5M unique patrons logging 11.5M books. We discovered that millions of patrons had only logged a single book. There’s nothing inherently bad about this statistic, in fact many websites may be happy about this engagement. However, unlike many book catalog websites, the Open Library is unique in that it links to millions of books that may be accessed through trusted book providers. It is thus reasonable that many patrons come to the Open Library website with the intent of accessing a specific title. This data amplified occasional reports from patrons who expressed disappointed when clicking “Want to Read” did not result in access to the book.

Refined hypothesis: Based on these learnings, we felt confident the “Want to Read” button may be confusing new patrons who thought clicking the button would get them access to the book. Under this lens, each of these registrations represents adoption for the wrong reason: i.e. a patron is compelled by the offering to register, but they bounce because what they get is a broken promise.

Trying a solution: Data gave us confidence the “Want to Read” button may be confusing new visitors to the site, but it also revealed that hundreds of thousands of patrons are actively using the Reading Log to keep track of books and we didn’t want to confuse the experience for them. We decided to change the website so that non-logged-in patrons, would see the “Want to Read” button as “Add to List” instead, whereas logged-in returning visitors would continue to see the “Want to Read” button they were used to.

The original button presented to patrons, which shows a potentially misleading: "Want to Read"
Before: The original button presented to patrons, which shows a potentially misleading: “Want to Read”
The button presented to logged out patrons after the change, reading "Add to List" instead of "Want to Read"
After: The button presented to logged out patrons after the change, reading “Add to List” instead of “Want to Read”

Results: When our team launched this week’s deploy, we noticed a few performance hiccups: our latest deploy increased memory demands and our servers began using too much memory, causing swapping. After some fire-fighting, we were able to make adjustments to our workers that normalized performance, though we remained alert.

A chart from Open Library's grafana system indicating that the website was facing a large number of 503's (i.e. it failed to respond to patron requests)

Later that night, we noticed a significant drop in registrations and started frantically testing the website:

A chart from Open Library's grafana system indicating that registrations-per-minute had fallen in the latest deploy.

We were thrilled to realize that our services are working correctly and the chart accurately reflected — what we hope to be — a decrease in bad experiences for our patrons.

Conclusion: Sometimes, less is more. We anticipate this will be the first small change in a long series of marginal improvements we hope to bring us closer into alignment with the core needs of our patrons. As we move towards 2026, we will continue to respond to the new normal shaped by recent events with the mantra: back to basics.

Save the Date: 2025 Open Library Community Celebration 

Each year since 2020, we’ve hosted a virtual celebration to honor the many global contributors who make the Open Library project possible and continuously improve the experience for our patrons. 

This year’s Open Library Community Celebration will be held virtually on Tuesday, Nov. 4, at 9 a.m. PDT. 

Volunteers, staff, patrons and friends of the library are invited to RSVP here to get the link.

Last year was marked by more than 500,000 books being removed from the library, cyber security attacks, and power outages. Our response has been to focus on doing more with less: making the books we have more useful, making our contributors more effective, and targeting our efforts to the underserved communities who rely on our services most.

Celebrate with us as we present:  

  • Personal success stories
  • New improvements for our library patrons
  • A sneak peek at our 2026 roadmap
  • Open Library’s strategic path forward

Also, check out previous years’ community celebrations to learn more about other recent victories: 2024, 2023, 2022, 2021, 2020.

Looking forward to inviting you to this year’s celebration!