Kapell
Docs / Enrichment & credits

When enrichment is empty (and how you can help)

A blank field is almost never a bug. Here's how to see what Kapell matched, why it came up short — and how you can fix it once, for everyone.

First, a reframe

Kapell shows what the open data sources actually hold. When a credit is missing, it’s usually because the data isn’t there yet — not because of a bug or shortcoming in Kapell. The good news: a lot of those gaps are fixable, and when you fix one upstream, it improves for everyone, with no app update needed.

This page helps you tell which kind of gap you’re looking at, and what to do about it.

Check what was matched

Every enrichment carries the stable identifiers Kapell matched on. Open the details for a track or album to see them:

  • TRKTracks carry an ISRC and an Apple song ID.
  • ALBAlbums carry a UPC and an Apple album ID.
  • ARTArtists carry an Apple artist ID and a Wikidata QID.
  • MBAn MBID appears when a MusicBrainz match was found. No MBID, and the result will be nearly empty — nothing resolved to join the other sources to.

There’s also a diagnostics view that lists every source Kapell consulted and what came back — a hit, a miss, a negative (it fetched, but the source had nothing), or not consulted. That’s your self-diagnosis tool: it tells you exactly why a field is blank.

Why albums are richer than tracks

This one trips people up, so it’s worth saying plainly: a rich album with thin tracks is expected.

Albums resolve well because Kapell asks Wikidata directly using the album’s MusicBrainz ID. Tracks are thinner because a track only gets a Wikipedia article if its MusicBrainz “work” carries a Wikidata link — and only about 9% of resolved tracks do. So if the album page is full and the track pages are sparse, nothing is broken. It’s just the shape of the data — and it’s fixable upstream.

The common reasons a field is empty

Working from most to least common:

01It never resolved. The song or album couldn't be matched from its Apple ID to MusicBrainz at all. Apple's catalog is far bigger than the open data, so this is common for long-tail, obscure, or "(Deluxe)"-suffixed releases.
02It resolved to the wrong entry. A plausible-looking match with credits that feel off. Worth reporting so it can be corrected.
03It resolved, but the field is missing. The right entry, but the specific relationship isn't attached — e.g. no producer credit yet. Fixable by contributing to MusicBrainz.
04The upstream has no data yet. An honest gap — nobody's added it anywhere. The most fixable case of all.
05The track-vs-album asymmetry above. The album's fine; the track just lacks a Wikidata link.

How you can help

Here’s the part we love. Most of these gaps aren’t ours to fix in code — they’re in the open data, which means anyone can fix them, and the fix lasts. An engaged listener with liner notes in hand can do real work here.

Fix it once, everyone benefits.

A credit you add to MusicBrainz or a fact you add to Wikidata flows back to every Kapell listener — and to everyone else using that data — without anyone needing to update the app.

Contribute data. MusicBrainz relationship edits are made by hand on the site — exactly the kind of thing an engaged listener can do well.

Or contribute money. If editing isn’t your thing, these projects run on donations — keeping the data free for everyone, Kapell included.

  • MBMetaBrainz (MusicBrainz, ListenBrainz, and more). donate
  • WMWikimedia (Wikidata and Wikipedia). donate

Either way — thank you. The reason Kapell can show you any of this is that people kept the liner notes alive. Adding to them is the most direct way to make the next lookup better.

Previous‹ How enrichment worksNextCrates ›