AcclaimIP HelpRecent Updates

Recent Updates

  • Updated on: May 04, 2017

    Finding Empty Fields (FIELD)

    It is often desirable to search for patents with specific fields that are empty or contain no data.   The syntax when searching for empty fields is just a little different.  Use the FIELD field code to find patents with particular empty fields.  The FIELD field code has two switches:

    • isEmpty
    • isNotEmpty

    You further specify which OTHER field code you want to identify as having the "isEmpty" or "isNotEmpty" value.  For example.

    • Field:isEmptyANO  -->  Notice the ANO field code is added immediately after the isEmpty switch.  This query finds patents with no Original Assignee names in the field.  

    The opposite is also true:

    • Field:isNotEmptyANO  -->  Just change the switch to "isNotEmpty" and all documents returned from your search will have a name in the ANO field.


  • Updated on: May 03, 2017

    Query Syntax Details

    This chapter covers all the syntax you'll need to know to become an expert patent searcher.

  • Updated on: May 03, 2017

    The Default Field Set

    When searching in AcclaimIP you can specify field codes to search only with specific fields.  For example, to search patent abstracts for the string "light emitting diode" you would type ABST:("light emitting diode") where ABST tells AcclaimIP to look in the abstract field only.

    When you do NOT specify a field code, AcclaimIP searches a set of fields called the "Default Field Set."

  • Updated on: May 03, 2017

    Field Code Cheat Sheet

    There are approximately 75 field codes which can be queried inside of AcclaimIP.  AcclaimIP provides users multiple resources for learning about Field Codes, what they are, how to use them and when they are appropriate to use.

  • Updated on: May 03, 2017

    Query Syntax Overview

    This chapter contains instructions on how to construct valid queries using AcclaimIP syntax.  For a complete list of query field codes, please view the AcclaimIP Cheat Sheet.

    You can create your own queries through the Expert Search form, the Quick Search window and the My Query form field.  You'll find that the syntax is very easy to learn and use, and as you advance in your patent searching skills, you'll rely on advanced syntax to create powerful nested queries.

    This document explains the syntax you use to interact with the Query Parser in AcclaimIP.

  • Updated on: Apr 20, 2017

    Logging out of

    To log out, go the the Start menu located on the bottom-left of the AcclaimIP desktop. The Logout option has a yellow key icon and is located in the upper right of the menu.

  • Updated on: Apr 20, 2017

    Locking Windows

    AcclaimIP conserves screen real estate by opening new documents in existing Document Details windows. However, sometimes you may want to keep a patent open.

    AcclaimIP supports a window locking option. You can lock and keep open as many windows as you need.

  • Updated on: Jun 15, 2015

    Maintenance Event Codes (EVENTCODE)

    If you want to find patents based on what has happened in their US maintenance / renewal history, use the EVENTCODE field code.

    There are over 160 EVENTCODES which you can query.  Many codes have been deprecated and will no longer be found on current patents.  To see a full list of EVENTCODES, open the Help>Cheat Sheet and hover your mouse over the EVENTCODE field code to open the dockable tooltip.

    AcclaimIP processes maintenance events weekly.

  • In this current implementation of custom data fields, a known issue is the inability to save documents to a research folder from a query with a custom field field code.

    In other words, if you run a query like _QUAL:Good where _QUAL is a custom data field field code, the documents cannot be directly saved to a research folder.

  • On the Search Result window, there is a button at the top of the Refine Search panel called "Display Query."  Display Query shows you the flattened query.  A flattened query includes the code that is actually sent to the search engine based on selections you've made in the User Interface (UI).

    Flattened Queries provide users two main benefits:

    1. Let's you review exactly what is being sent to the search engine.  In other words, Display Query shows you how the UI impacts the query.  It is helpful for advanced users to diagnose queries and analyze what the UI is doing.
    2. By extension, you can edit default behavior of the user interface by choose Display Query, flattening the query, then editing the result.

    This second option allows you to, for example, use a Boolean NOT and remove selections, and effectively page the facets in each of the filters.