Sad fact: For a while Discogs had an experimental feature aptly called "Tracks". It allowed individual tracks, not just the whole release, to be viewed as separate entities along with references to all releases on which said track appeared. A database of canonical tracks.
It enabled me to see if that great track from an ultra-rare and hard to find album perhaps appeared on a compilation or any other much easier to buy release. Sure, you can achieve similar results by simply searching, but it's much more cumbersome and downright difficult when it comes to rather generic track titles leading to countless irrelevant results.
Sadly the feature was abandoned: https://www.discogs.com/track
https://developer.spotify.com/documentation/web-api/referenc...
I used to do a lot of data mining on data from various musical sources. Mostly with the goal to make the discovery process faster.
- Discogs seems to have the most complete release data.
- MusicBrainz has the best organized encyclopedic data. For example they have entities for specific instruments, relationships between artists, entries for supporting roles like recording engineer, etc.
- Wikipedia still has the best common-sense/canonical info about singles. For example, Wikipedia will tell you in the first sentence (or infobox) "song X was first released on album Y in year Z." Answering that can actually be quite challenging on other services.
- Spotify is the go-to for finding useful qualities of individual songs (due to their acquisition of Echo Nest). Things like popularity, danceability, energy, etc.
A long-term project of mine has been wrapping all these up in a more approachable API. So far that has only resulted in this big GraphQL schema project: https://github.com/exogen/graphbrainz – but the idea is to build on that and make it even simpler.