How to include work-level-rels in web service API for a large release?

Tags: #<Tag:0x00007f9cfdf8d170> #<Tag:0x00007f9cfdf8d0a8>

I set up a local musicbrainz-docker server, to tag classical music file using Picard & classical Extra.
If a release has many tracks or media (I’m not sure what is the constraint), the web service API doesn’t include work in the API response.
For example,

This response doesn’t have work relationship in the recording.
How can I change this to include work relationship, even if a release has a large track count?
I mean, changing my own local server setting.



You want to change this number, or change the code to not set a max:



I increased the size to 3000. I confirmed the server response includes the work relations for the previous example.


1 Like