Many in our community are intimately familiar with and sensitive to the challenges of FRBR (e.g. serials, etc) as it pertains to maintaining a system of Works a

Many in our community are intimately familiar with and sensitive to the challenges of FRBR (e.g. serials, etc) as it pertains to maintaining a system of Works and Editions. This is an active conversation on our slack. Send me an email and I'll be happy to invite you to join the discussion. Honestly, a lot of our Librarian bottlenecks aren't engineering, they're documentation and organization related. Since Aaron Swartz started Open Library ~2007, there have been scores of trailblazing Librarians (like Karen Coyle and Jessamyn West) who have nudged us in the right direction and documented their opinions. I've done by best to organize these learnings here: https://openlibrary.org/librarians https://openlibrary.org/librarians We could really use help here if you or anyone else is interested in doing some digital archaeology and helping us better organize (so we can make good schema decisions to move forward). Thanks for bringing this up. Fun fact, by the way: Nearly every page on Open Library is a json API of itself if you add `.json` to the end. e.g. https://openlibrary.org/books/OL7353617M/Fantastic_Mr._Fox https://openlibrary.org/books/OL7353617M/Fantastic_Mr._Fox & https://openlibrary.org/books/OL7353617M.json https://openlibrary.org/books/OL7353617M.json