Open Data

What is in it

Three record sets, each with an index, one file per record, and where useful a single bulk file. Start from data/index.json, the catalog.

• Albums 1,364
  One record per reviewed album: schema.org MusicAlbum (session date and studio, release, catalog number, label, tracks, personnel with instruments), every review with its rating, and the Discogs master id.
  One record per file at data/albums/{album_id}.json · index · everything in one file
• Players 2,171
  One record per credited musician: instrument, other spellings, counts, every reviewed record with role and leader flag, every collaborator with shared records.
  One record per file at data/players/{slug}.json · index
• Labels 185
  One record per record label: spellings, counts, artists, every reviewed record.
  One record per file at data/labels/{label_id}.json · index

Indexes and graph

• album-index.json
  Album identity: title, artist, year, label id, review URLs.
• label-index.json
  Label identity: canonical name, spellings, review URLs.
• lineage-index.json
  The Sideman Map graph: albums with credits, musicians with album refs (key legend in llms.txt).
• search-index.json
  Album search: title, artist, label and year, rating, review URL, song titles.
• profile-index.json
  Artist profile pages and the hubs they belong to.

Feeds

• feed.xml (Atom)
  Pages added to the site: artist pages, articles, profiles, Liner Notes.
• feed-reviews.xml (Atom)
  Album reviews added to the site.

How it is made

Every file is generated from the review pages at each build, and the pages stay the source of truth: a correction to a review reaches the data on the next build. Album records use schema.org MusicAlbum, identical to the structured data in that review. Coverage is the albums reviewed here, 1949 to 2025, not a catalog of recorded jazz, so a count is always a count of reviewed records. Static files with open CORS, no key, and no limit beyond the host. The field legend for the graph file is in llms.txt.