Datadory notebook
Open Library Monthly Dump Data: Dataset Structure and Field Coverage
Datadory delivers open library monthly dump data covering comprehensive field definitions, entity mappings, and historical time series — structured for direct analytics and delivered on demand.
1,744 datasets. Pick your catch.
What is the Open Library monthly dump?
Each dump line holds one record - edition, work, author, redirect or list - as a JSON payload per row, which makes parsing a streaming job rather than a database restore. The catalog behind the dumps is large: a broad search query returned numFound 7,723,767 works during testing, and the homepage states more than 3M books are borrowable free.
How big is each monthly dump?
The current all-types dump weighs about 12.4 GB compressed, and the editions file alone accounts for roughly 9.2 GB of that. If you also want revision history, the 'complete' variant runs about 29.6 GB compressed and additionally includes every past revision of every record.
| Dump component | Size (compressed) | Grain | Notes |
|---|---|---|---|
| All record types (current state) | ~12.4 GB | One line per record: edition, work, author, redirect, list | Monthly full snapshot, gzipped TSV with a JSON payload per row |
| Editions file alone | ~9.2 GB | One row per edition (ISBN-bearing) | The largest single file; implies tens of millions of edition rows |
| 'Complete' dump with revision history | ~29.6 GB | Record plus every past revision | Choose this only if you need edit lineage, not just current state |
| Ratings, reading-log, lists, covers, wikidata files | Separate files | Per user interaction / per record / per image | Ships alongside the core types; no extra collection step needed |
Which files ship alongside editions, works and authors?
Beyond the core bibliographic types, the dumps page lists separate ratings, reading-log, lists, covers and wikidata files, so reader-behavior signals ride along with the metadata instead of requiring a second collection effort. Formats are TSV (one line per record), JSON payloads inside those lines, and txt.gz archives.
How do you load a monthly dump into your own database?
A working pipeline needs five steps, and none of them involve requesting credentials:
- Decompress each txt.gz streamingly (gzip -dc | python) rather than expanding to disk; every line is a self-contained JSON payload keyed by record type.
- Split by type first: load editions (~9.2 GB compressed) into an ISBN-keyed table, works into a title-level table, authors separately, then keep redirects to resolve later merges.
- Join the side files - ratings, reading-log, lists, covers, wikidata - onto your edition and work keys so engagement signals land in the same warehouse as the metadata.
- For anything newer than last month's snapshot, fall back to the keyless Search & Works/Editions API at 1 req/s anonymous (3 req/s with an identified User-Agent and email), never at bulk-harvest volumes.
What should you pair with an Open Library dump?
The dump gives you metadata; three sibling sources give it payload. Project Gutenberg publishes 79,228 public-domain ebooks whose RDF, CSV and MARC catalogs join to Open Library records on title and author. The Internet Archive Digital Library's Text & Books Collection exposes OCR text files and PDFs over 40M+ scanned items through an advancedsearch Solr API - 4,093,835 items sat in its americana collection alone on 2026-08-21. For model training, Hugging Face's Datasets Hub lists about 770 book-tagged corpora, from LoC-PD-Books (~140,000 books, ~8 billion words) downward.
| Dump component | Size (compressed) | Grain | Notes |
|---|---|---|---|
| All record types (current state) | ~12.4 GB | One line per record: edition, work, author, redirect, list | Monthly full snapshot, gzipped TSV with a JSON payload per row |
| Editions file alone | ~9.2 GB | One row per edition (ISBN-bearing) | The largest single file; implies tens of millions of edition rows |
| 'Complete' dump with revision history | ~29.6 GB | Record plus every past revision | Choose this only if you need edit lineage, not just current state |
| Ratings, reading-log, lists, covers, wikidata files | Separate files | Per user interaction / per record / per image | Ships alongside the core types; no extra collection step needed |
Pick up where this leaves off
Every one of these ships with sample rows before you commit to anything.
Open Library Monthly Data Dumps Data
type · key · revision …+2 more
Open Library General Catalog - Browsable Lending Library Data
key · title · edition_count …+11 more
Open Library Search & Works/Editions API Data
numFound · docs · key …+17 more
Google Books APIs Data
subtitle · publisher · publishedDate …+11 more
Wikidata - Publishing Knowledge Graph + SPARQL
P212 · P957 · P1476 …+7 more
Want rows instead of a pitch? Name the datasets.
API, files, or your warehouse. Daily, weekly, or hourly.
Get a sample