Existing links are not detected for releases with more than 100 artists/recordings

[kellnerd]

https://harmony.pulsewidth.org.uk/release/actions?spotify=1urbmTMDCbfEBszjLqlnAg&musicbrainz=8a1f5e0f-4fec-44a1-8303-1ccfdbcc1f97&gtin=703980552094&deezer=&itunes=&tidal=&beatport=&region=GB&release_mbid=8a1f5e0f-4fec-44a1-8303-1ccfdbcc1f97

There are 44 unique artists on this compilation and the MB API only returns up to 25 artists (with their existing links) for "browse" requests: http://musicbrainz.org/ws/2/artist?release=8a1f5e0f-4fec-44a1-8303-1ccfdbcc1f97&inc=url-rels&fmt=json
I thought it was not possible to get the missing artists, but I just realized that there is an offset parameter to page through the results...

This unlikely to be an issue for labels, but also affects releases with more than 25 tracks. Pagination for recordings should probably only implemented once the "recording actions" are opt-in, I don't want to slow down the release actions page for dozens of links which many (or most?) people probably ignore.

[mwiencek]

I thought it was not possible to get the missing artists, but I just realized that there is an offset parameter to page through the results...

There's also a limit parameter which you can increase up to 100:
http://musicbrainz.org/ws/2/artist?release=8a1f5e0f-4fec-44a1-8303-1ccfdbcc1f97&inc=url-rels&fmt=json&limit=100

Of course, you'll still need pagination if there are more than 100 artists.

[kellnerd]

There's also a limit parameter which you can increase up to 100:

Great, that's even better. I really wonder whether I had looked at the API documentation at all when I initially implemented this 😅

[mwiencek]

That's okay, I've long assumed our web service documentation is write-only. 🙃

[kellnerd]

I have at least increased the limit for artists and recordings now, paging remains to be done.