Hello Vesna,

thanks for your explanation!

Regards, Martien

Hello, until this evening (last try ca. 17.45h) queries like q=pn any "US20190102515 US20190102514 US20190102513 US20190102512 US20190102511" were possible with up 10 publication numbers. Now I get "413 Request Entity Too Large" if I use more than four numbers. Did the actual mai...

Hello Vesna, before the CPCI change I got e.g.(pn=NL1016861): <patent-classifications> <patent-classification sequence="1"> <classification-scheme office="" scheme="CPC"/> <section>A</section> <class>01</class> <subclass>J</subclass> <main-group>25</main-group> <subgrou...

Since the change to CPCI my Solr Database didn't load, while it missed the field "...generating-office".
Although I'm working with JSON instead of XML, it seems to me that the XML Schema changed and
the information in the roll-out docs for CPCI may be not complete.

Kind regards,

Martien

additional to QuotaHourUsed, also the situation
'overloaded (images=green:50, inpadoc=green:30, other=green:1000, retrieval=green:50, search=black:0)'
seems to be IP dependent.

While I got this on one testserver, the other was still running with the same Key/Secret.
Is this OK?

Hi all, in https://forums.epo.org/throttling-control-robots-7587 you explained a lot about throttling. Meantime I still see the following issues: 1. hourly quota is dependent on the calling server-IP and not the user (OPS Consumer). On my test servers I got this using the same key/secret: Server 1: ...

Hi Vesna,

I definitely didn't realize the table on p. 42. before.
Thanks again,

Martien

Hi Vesna, To my example #1, I didn't get a "red" condition within the last 15 days before (where my log started). After "yellow" we slowed down a bit (4 secs) and got "black" as next result, without getting "red" before. Is seems, that a (one) certain query us...

Hi Support, I have implemented the rules according the fair use policy and normally it's working quite well. However, in some situations I still get the error CLIENT.RobotDetected, although to my understanding there should not be a reason for waiting with a next call: ####### Ex 1 #### Change from y...

Hi all, to find out if documents are changed, within ops and CQL, I only can use the publication-date. However, documents may change without a publication-date change. In docdb examples there are essential fields I'm missing within OPS and, supposed OPS would provide them, could help to reduce the e...