1) the tooltips weren’t necessarily displaying the most relevant information 2) the “Album year” metadata isn’t always that valuable
Choosing which fields to include in the tooltip, and then displaying their values in a nice human-readable form, was nice and straightforward, and made a huge difference. What I didn’t work out was how (if!?) I could display a list of values where the data point represents a count of items (eg saying which playlists Wham! are on, not just saying how many); that’s a work in progress…
In the original viz, year data was featured prominently; however, this data was actually album year, not track year. This is fair, as who’s to say when a track originates from without reference to the release of the album or single it came from? Either way, abstract information like that might be available from some source on the internet, but it’s certainly not something we could expect to get from Spotify.
That the date information is actually about albums rather tracks does affect us, however, in a couple of situations:
As a practical solution to try to get the most appropriate date for a given track, I updated playviz to include an extra step in its json fetching routine: before saving a track’s json, the script now does a new Spotify search query using the track name and artist name returned by the original lookup, and grabs the earliest date from the results. This combats the compilation issue nicely, and can sometimes get around the remastering issue too (if the track was on a single as well as an album, it’s possible that the single version will have retained its original date).
Below is my viz updated to use this new year attribute:←