I’m seeing something odd in the behavior of the search API, in particular the use of the limit and offset arguments to paginate output. Here’s a first call: https://api.next.nomics.world/search?q=BOE&limit=20&offset=0 This gives me 20 datasets OK (although, surprisingly, number 20 is Eurostat’s “f…

Let me attempt to clarify: the “not equal to either 1-10 or 11-20 of the original” part of my original posting may be irrelevant, perhaps I was assuming too much. But here’s the key point: calls to the search API with arguments (a) BOE, limit=10, offset=0 (b) BOE, limit=10, offset=10 produce the …

Hi @acottrell , Thanks for taking time to report this. I will look a that more in depth tomorrow, to confirm what you explain, and fix it. Regards

To be a little more precise, here are full examples of what I’m talking about. “general” search: offset ignored: these two searches give the same result https://api.next.nomics.world/search?q=interest%20rate&limit=10&offset=0 https://api.next.nomics.world/search?q=interest%20rate&limit=10&offset=…

Hi @acottrell I created this issue corresponding to the bug report you made, I fixed the problem and deployed the new version in production. Can you please confirm that it’s OK for you? Sorry for the delay, and thanks again for all the feedback you made on DBnomics. Regards, Christophe

Search pagination in "next" API

Data Issues

acottrell August 17, 2018, 5:29pm 6

Yes, confirmed OK now. Thanks!

Incorrect "num_found" in search results

Topic		Replies	Views
Incorrect "num_found" in search results Data Issues	3	881	August 21, 2018
OECD datasets some are not reachable	1	309	November 13, 2023
IMF WEO 2022 missing? Community imf	6	403	November 15, 2022
DBnomics API v22 released Community	10	2063	March 7, 2019
Problem with dataset.json for BIS Community	0	10	November 19, 2024

Search pagination in "next" API

Related topics