Skip to content

Queries on non-patent endpoints with 'match_subentities_only' = 'false' returning error #39

@sarahkelley

Description

@sarahkelley

When one uses ‘matched_subentities_only’ = ‘false’ on non-patent endpoint (particularly cpc_subsection, nber_subcategories, uspc_mainclass), the API returns a ‘500’ error. This occurs because when you use ‘matched_sub_entities_only’ = ‘false’ the endpoint is returning all data associated with the value on that endpoint associated with the patent. So, for example, if you are querying the cpc_subsection endpoint for patent ‘5116621’ it would return all the assignee/location/inventor etc information about patents associated with the same cpc_subsection id as that patent not just the assignee/location/inventors that are associated with patent ‘5116621’. Similarly, on the locations endpoint you’d be returning all the information about all the patents with the same location as patent ‘5116621’, which is also a lot of information. We have been working on exploring how we can resolve this issue, but it is not likely to be resolved in the short term. We’d recommend that you either run the query in ‘chunks’ (e.g. first with just inventor fields, then just assignee fields, etc) or that you use ‘match_subentities_only’ = ‘true’ or that you query the patent endpoint for information about a particular patent in the mean time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions