Page 1 of 1

CLIENT.InvalidQuery when X-OPS-Range > 2000

Posted: Mon Mar 11, 2019 10:57 am
by pzypher
Hi,

following query leads to a 400 BAD REQUEST (CLIENT.InvalidQuery) when I set X-OPS-Range=5000-5025 although @total-result-count of the same query with another range returns 10000.

http://ops.epo.org/rest-services/publis ... q=pa%3DIBM

Additional header: Accept: application/json

I figured out that the upper boundary for valid X-OPS-RANGE values is around 2000.

Any idea? Thanks!

Re: CLIENT.InvalidQuery when X-OPS-Range > 2000

Posted: Tue Mar 12, 2019 7:55 am
by EPO / OPS Support
Hi

As stated in user documentation of OPS, you can only get first 2000 results via OPS. You need to limit your query in such way that you stay under 2000 in order to load all documents from your query. Please remember that OPS is just an Espacenet for machines and not a downloading service. If you need larger amount of data you have to consider buying a bulk data set instead.

Regards,
Vesna for OPS support

Re: CLIENT.InvalidQuery when X-OPS-Range > 2000

Posted: Tue Mar 12, 2019 8:31 am
by pzypher
Hi,

thanks for your reply. The queries are automated by a software of course. Can you please provide a link to the statement about the 2000 results limit? Just to show it my customer.

Thanks!

Re: CLIENT.InvalidQuery when X-OPS-Range > 2000

Posted: Tue Mar 12, 2019 9:04 am
by EPO / OPS Support
This is a slide from my online seminar about OPS where you see a list of all limitations on one page (as they are at present) in OPS. We used to link entire document at some point, but it’s a while ago and I see it’s no longer available online. But this is the most informative slide anyway so I am attaching it here.

Regards,
Vesna for OPS support