It’s not a bug, it’s made to limit the CPU and memory consumption on server side.
1 Like
Hi @outsidecontext, I think I have to do this instead of my works search, as it allows for trating all recording relationships, not only works.
I just need works for the moment, but already have another feature in mind to search for certain linked recordings too.
But could you tell me if the /ws/2/recording?release=<release-mbid>&inc= DOES NOT have the same MBS-12154 bug as the /ws/2/work?query=rid%3A<recording-mbid>+OR+rid%3A<recording-mbid>…&inc= ?
Hopefully maybe not, as you are using it in Picard and as mine is a search (query=…) but yours is a browse.
Yes, exactly. If you do a search you get weighted results from the search server, ordered by how the search servers rates the match.
Also as you said getting all recordings for a release is the only way to get all the relationships as you would get them for the release request.
2 Likes