Would you expect album metadata processors to run on the fake non-album tracks release? I agree track metadata processors should run. A caveat is that track metadata processors that make external requests (like the Last.fm plugin) won't have any way to delay a NAT from loading, like it can do with albums by increasing album._requests. This functionality can be added of course, but plugins would still have to manually detect whether it's dealing with a non-album track.

I forgot to add: track relationships being absent is an issue unrelated to this, so you should probably create a separate ticket to track that.

Hi! No, of course I don't want the album processor run over that fake album, this was just diagnostic help from me for easier bug fixing

Ok, I created PICARD-10 ... but I can't imagine they aren't somehow connected...

The cause is different because track relationships aren't requested via a plugin, so fixing this issue won't fix that one. PICARD-10 could be solved by adding the appropriate parameters to the web service request.

And it depends on another server ticket too as it appears work relationships like composer can't be requested via /ws/2/recording

Fixed in http://bazaar.launchpad.net/~musicbrainz-developers/picard/trunk/revision/1171