Hi @librarydude33! Nice to meet you and thanks for the feedback. Your frustration is understandable and noted.

Some other details; the entire Open Library team of staff has been 2 engineers (now 3) -- Drini, Jim, and myself. Volunteer team leads from the community step up to ensure the aspects of the service they care about also get done.

In any given month, more than 20 volunteers may submit contributions and our staff invests in supporting, mentoring, and reviewing the changes of each of these contributors. This takes time.

The library serves nearly 5M patrons; enabling around 350,000 borrows a month. We are the team responsible for maintaining the servers. For writing and deploying new code. For monitoring the pager when the service has performance issues. For working with librarians. For coordinating with policy teams. For drafting and executing on a roadmap for the project. For moderating spam and user-generated content. For supporting a group of volunteer librarians, more than 5 volunteer team leads, and 4 interns/fellows.

Our entire roadmap is also public and the project is open source, meaning if there's something one is unsatisfied with, they have the power to change it, and our team does our best to support contributors in this pursuit with the time we have. Moreover, we host public community calls every Tuesday and developed our yearly roadmap with the inclusion and feedback of our entire community.

Finally, the past 2 years we have added a variety of librarian features. An interface for merging duplicate works. A mechanism for deleting works and their editions in bulk. Bot infrastructure to clean up records en masse.

Many processes such as adding and editing book records don't require librarian privileges. Some tasks like author merging and deleting records require privileges because these services require a certain level of trust and training -- otherwise, a mistake which takes 10 seconds to make, may cost our engineering team 30 minutes to untangle. Also, some contributors stick around for a few days and then disappear and training takes time, so we like to build rapport with teammates before granting permissions.

Lisa, who is our lead community librarian, coordinates with more than 30 people in addition to her full time job. She typically is very fast at replying to passionate contributors who want to help out as Librarians. Even if one doesn't have librarian access, she and her teammates welcome requests for merging records.

If you send me an email to mek@archive.org, I can work as quickly as possible to invite you to our librarian channel so at minimum, you may engage with other passionate librarians, raise your concerns, your wishes, and report records which need fixing.

Thank you!