MBS-12154: MB Search API is broken, no pagination possible
2022-08-07 21921, 2022
jesus2099
Unless you make a query that matches less than 100 results, it's broken.
2022-08-07 21915, 2022
jesus2099
I could make a clumsy work around for COLLECTION HIGHLIGHTER, but only for one use case.
2022-08-07 21915, 2022
jesus2099
I am now completely stuck with this bug as I want to use web services instead of web pages, in COLLECTION HIGHLIGHTER and in MASS MERGE RECORDINGS, etc.
Click page 1 and 2, you will see that recordings don't stay in the same order, so it's impossible to parse them.
2022-08-07 21921, 2022
jesus2099
I would love to stop having to look for work-arounds (none found for recordings in release group).
2022-08-07 21900, 2022
jesus2099
A possible work-around would be, as I think the web service tells us the total the total results (count), I would load reload and rereload all pages (or only page 1) until I have an amount of distinct results equals to count.
2022-08-07 21900, 2022
jesus2099
But it sounds so tedious to do.
2022-08-07 21917, 2022
jesus2099
An MBS solution I thought of is that MBS should order all /ws/2/<entity-type>/?query= results by row ID.
2022-08-07 21957, 2022
jesus2099
It's an arbitrary sort order that would re-enable the pagination system and the searches for more than 100 results.
2022-08-07 21900, 2022
jesus2099
Good night, all. Maybe I wrote this too late in the evening. :)
There was another forum thread, but I can't find it
2022-08-07 21925, 2022
aerozol
It also affects me when I'm adding relationships (e.g. 'recording of') and a bunch of recordings of the same name keep swapping places in the results... ahhh
2022-08-07 21937, 2022
aerozol
Not sure if it's hard to fix or just nobody's been interested?
