This space is made available to users of Open Patent Services (OPS) web-service and now also to users of EPO’s bulk data subscription products such as 14. EPO worldwide bibliographic database (DOCDB), 14.11 EPO worldwide legal status database (INPADOC), 14.12 EP full text data, 14.1 EP bibliographic data (EBD)and more.
Users can ask each other questions, exchange experiences and solutions, post ideas. The moderator will use this space to announce changes or other relevant information.
-
omisler
- Posts: 1
- Joined: Thu Jun 05, 2014 5:15 pm
Post
by omisler » Thu Jun 05, 2014 5:45 pm
I have tried several times to perform a 'biblio' query using the epodoc format of a priority.
In the developers area, for instance, I searched with priority "EP20110169217":
/published-data/priority/epodoc/EP20110169217/biblio
The result is a HTTP/1.1 413 Request Entity Too Large header, though below I found a list of publications related to that priority number.
<code>CLIENT.AmbiguousRequest</code>
<message>The request was ambiguous</message>
<details>
<cause>Ambiguous input: priority/epodoc/EP20110169217</cause>
<resolution>publication/docdb/AU.2012266457.A1</resolution>
<resolution>publication/docdb/CA.2837255.A1</resolution>
<resolution>publication/docdb/CN.103596567.A</resolution>
<resolution>publication/docdb/CO.6801764.A2</resolution>
<resolution>publication/docdb/EA.201391787.A1</resolution>
<resolution>publication/docdb/EP.2717873.A1</resolution>
<resolution>publication/docdb/KR.20140029517.A</resolution>
<resolution>publication/docdb/MX.2013013853.A</resolution>
<resolution>publication/docdb/SG.195156.A1</resolution>
<resolution>publication/docdb/US.2012316172.A1</resolution>
</details>
</fault>
Further, if I search by the same priority in the 'Advanced Search' for human users it does show a series of publications.
So what's the deal?
-
EPO / OPS Support
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
Post
by EPO / OPS Support » Tue Jun 10, 2014 1:26 pm
Dear user,
I don't see error Request entity too large, I only see Ambiguous Request which usually signalised that the system would like you to be more precise and add a kind code (common when using Epodoc)
In your case, there should not be either ambiguous or request too big because your query is fine as it is. We will report this issue to out technical team.
In the meantime, I would suggest that you rather use Smart Search option when you are looking for priorities:
http://ops.epo.org/3.1/rest-services/pu ... 0110169217
In this way, you will get complete list (even WO document that was missing in your list below).
Kind regards,
OPS support
