#musicbrainz

eharris: open your picard plugins folder (you can use this from within Picard in Options > Plugins) and remove the workandmovement.zip file there or move it elsewhere. Then create a folder "workandmovement" in the plugin folder and place the __init__.py file from https://raw.githubusercontent.com/metabrainz/pi... there. Restart Picard

and the plugin should show up with version 1.1.

aerozol: either! both! everyone tags amd thne we'll see what are the top genres on guitar like (but remember that "electric guitar" and "guitar" are not the same. be as spesific about the instrument as you cna please (so rock and roll would be electric guitar, electric bass guitar, drumkit))

outsidecontext: ok, what you said didn't work, turns out it was complaining about not having roman.py, but I just reused the one from the previous version

outsidecontext: so it looks like it's working now and doing what I want with the following script:

$set(work,$if2($get(work),$get(_recording_work)))

$set(musicbrainz_workid,$if2($get(musicbrainz_workid),$get(_recording_workid)))

eharris: oh yes, forgot it has a second file :) glad it is working for you. I'll have the changes merged soon, then this will be available via plugin download in Picard as well

But you can keep it installed like you have it now. Should there be a future version an upgrade directly from Picard will still work

outsidecontext: I still think it would be worthwhile to have a standardized/well known place for the work/composition

Maybe, not sure about this. Everyone seems to have different expectations on what should be there

is there a discussion about that you can point me to? I have read ticket PICARD-1050, and that makes sense for multipart works

PICARD-1050: Only use WORK field for multilevel works https://tickets.metabrainz.org/browse/PICARD-1050

but work/composition is still a useful thing to have even when not a multipart work

That ticket mostly, yes.

the suggestion in that ticket of using $set(work,$if2($get(work),$get(_recording_work)))

oops, the suggestion in that ticket of using MUSICBRAINZ_WORK_COMPOSITION seems reasonable

although I think it would be more logical to be MUSICBRAINZ_COMPOSITION_WORK and MUSICBRAINZ_COMPOSITON_WORKID