Example: https://ops.epo.org/3.2/rest-services/published-data/publication/docdb/biblio US.9750499.B2 takes over a minute to get a response, whereas if I take an older patent such as: US.7123123.B2 the response is nearly instant. This time delay seems even worse in batch. When querying this batch of ...

Hello OPS Team, We've noticed some recent outages w/ various OPS services beyond the normal nightly maintenance window. Are these issues expected to be resolved soon? Detected outages over the past two days: 11/29/2019: 7:33PM UTC (for 1 minute) 8:05 PM UTC (for 6 minutes) 8:41 PM UTC (for 1 minute)...

In the claim text returned from OPS, chemical formulas are often referenced with img tags and a reference number. Example EP.2236541.A1: <claim-text>1. A (optionally non-dendrim eric) polyester amide macromolecule represented by Formula 1. <img class="EMIRef" id="029338117-ib0021"...

I wasn't able to reproduce in postman, and after further investigation it looks like an issue with PHP clients when the POST size is above 1024 bytes (which I suppose happens once the number of patents in a request gets above 70 or so). I was able to fix my issue and get the expected response header...

Hello, The biblio API allows input for up to 100 patents in batch during a POST request. However, I've noticed that if I run a query of ~70 - 100 patents at once (easily reproducible for me when passing in 100 patents), the headers are missing info such as the Quota usage. In this case, the response...

it's back up now. total downtime: 2 hours, 50 minutes

Unable to use any of the OPS API at this time. Is there a place for announcements of planned downtime or was this unexpected?

Thanks!
Joe

Hi, I noticed some unusual behavior with the docdb biblio endpoint. If I query the following two patents together: JP.H0678863.U JP.H088451.Y2 The response opens with a status="not found" result, followed by the correct response for each of the two patents: <?xml version="1.0" en...

EDIT: see correction below. Hello, There used to be an issue querying multiple patents at once in docdb, where if any one of the input patent numbers were not found, the entire response to the API call returns SERVER.EntityNotFound - No results found. That problem was fixed in an update back in Nov...