Adrian Sampson

OK, cool. Marked this as a feature request for that first stage.

Hi, @dosoe—that sounds like a separate feature request. Maybe it deserves a separate GitHub thread?

Hmm… to summarize, it sounds like you're interested in how to query the MusicBrainz web service for a specific work ID? For that, you go through the [client library](https://github.com/alastair/python-musicbrainzngs) and...

Sure, a `work_info` function would be OK—but it would need to look different from the `track_info` function. The latter produces a complete `TrackInfo` object, and there would not be a...

Sure! But I'd argue that you'd probably be better of with just a plain `dict` instead.

Hmm; that's interesting! I notice that this seems to have gotten quite a bit more complicated. It seems like it would be a worthy goal to see if this can...

Yeah, making a plugin would be a great way to make the extra queries optional and encapsulate the new code! It's actually fairly straightforward: the beets plugin system has an...

Sure! Here's the place to start: http://docs.beets.io/en/v1.4.3/dev/plugins.html Feel free to post questions along the way if anything comes up.

Indeed; while knowing the details of the release that crashes would help, it looks like the plugin needs to avoid relying on the existence of that `contributors` key.

Interesting! So would you want a new field called something like $primary_artist that only includes the name of the first artist on a track? Even better would be for $artist...