Relationships not returned by XML webservice

webservice
Tags: #<Tag:0x00007fcb57695698>

#1

For this very large box set (40CDs) the relationships seem to be omitted, even though included as params and clearly visible when browsing. They also appear when doing a recording look-up, rather than the full release.
See:
https://musicbrainz.org/ws/2/release/60af2508-679f-32e7-a582-d01e48450113?inc=release-groups+media+recordings+artist-credits+artists+aliases+labels+isrcs+collections+artist-rels+release-rels+url-rels+recording-rels+work-rels+recording-level-rels+work-level-rels+tags
Any ideas why this is happening?


Classical Extras plugin (for Picard 1.4.x)
55-disc release split into 55 pseudo releases "for better tagging purposes"
#2

The underlying database query takes too long to complete. It should probably be chunked into smaller queries. MusicBrainz server requires code improvement to successfully handle such request.


#3

In that case, the only solution (for Picard) seems to be to split the release into smaller pseudo-releases (see 55-disc release split into 55 pseudo releases "for better tagging purposes" and Classical Extras plugin). Is there any guidance as to the maximal size for the query? I know a 15 CD box set that works, but is it safer to aim for, say, 10-CD pseudo-releases?


#4

This 21CD box set works (just tested) but guessing that the overall track count/information count matters more than the number of discs. I would say 10 CDs would be a safe target.