Ambiguous response when querying published data for Japan with a wild card kind code

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.
Post Reply

ofipify
Posts: 3
Joined: Wed Oct 04, 2023 2:24 pm

Ambiguous response when querying published data for Japan with a wild card kind code

Post by ofipify » Tue Jan 16, 2024 11:45 am

Hi,

We are using a request like the one below to grab all published documents for a publication number, using a wild card in lieu of the kind code.

Code: Select all

http://ops.epo.org/3.2/rest-services/published-data/publication/docdb/EP.1234567.%/biblio
This does not seem to work for Japanese patents. A request to:

Code: Select all

http://ops.epo.org/3.2/rest-services/published-data/publication/docdb/JP.3232777.%/biblio
results in 413 Request Entity Too Large:

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault xmlns="http://ops.epo.org">
    <code>CLIENT.AmbiguousRequest</code>
    <message>The request was ambiguous</message>
    <details>
        <cause>Ambiguous input: publication/docdb/JP.3232777.*</cause>
        <resolution>publication/docdb/JP.3232777.B2</resolution>
        <resolution>publication/docdb/JP.3232777.U</resolution>
    </details>
</fault>
The difference in behaviour is a bit confusing. I would also suggest that 300 Multiple Choices would be a better HTTP status code in this instance.

Thank you.


EPO / OPS Support
Posts: 1298
Joined: Thu Feb 22, 2007 5:32 pm

Re: Ambiguous response when querying published data for Japan with a wild card kind code

Post by EPO / OPS Support » Thu Jan 18, 2024 10:44 am

Hi,

In fact, that is a feature of OPS and not a mistake in response. The ambiguous seed informs you that your query has to be amended because there are two (or more) documents found that correspond to your number query. You have to choose one of the proposed options in order to display it.

Regards
Vesna
OPS support


consentmainmast
Posts: 1
Joined: Fri Jan 26, 2024 2:38 am

Re: Ambiguous response when querying published data for Japan with a wild card kind code

Post by consentmainmast » Fri Jan 26, 2024 2:42 am

I think this is a characteristic of OPS


Post Reply