AcclaimIP HelpRecent Updates

Recent Updates

  • 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 AcclaimIP.com

    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.

  • At the document level you can view and/or modify custom data from the Document Details window.  Custom fields appear to the right in an accordion-style panel labeled "Custom Fields."

  • Just like other data fields, custom fields can be faceted filters.  Remember, a filter lets you refine your search by some data element; the facets are the actual counts within a filter.

    In this example, I created a rating system and tagged about 5000 of Google's patents with rankings.  These data were randomly generated for demonstration purposes and do not represent real opinions on the patents displayed.

    One of the ultimate goals of most patenting organizations is to build a ever-growing knowledgebase that tells users which patents are major inventions, which are incremental improvements and even which are no good at all and slated for abandonment.  The example here uses a simple 4 dimensional rating system including the following criteria.

    • Current Use – Is the invention being used in products today?
    • Detectability – Can use be economically proven in infringing devices?
    • Alternatives – Are there other methods to achieve the same result as the patented invention?
    • Prior Art Risk – What is the likelihood the patent could stand up to extensive prior art search?

    Editorial Opinion:

    This simple system is a good start for your own rating system.  While this is a fairly simple one, simple is often better.  I advise IP managers to develop the simplest possible rating system that will meet your needs.  Overly complex rating systems, while well intentioned and better in theory, virtually always fail due to their complexity.

  • Updated on: Mar 26, 2014

    Finding Empty Custom Data Fields

    You may be familiar with the FIELD field code to find empty data fields in any normal AcclaimIP patent data field.  The FIELD field code also works for custom fields.

    For example, let's say you define a custom field to categorize patents, and you name it "Technology" and give it a field code _TAX.TECH.  Remember all custom field codes begin with a leading underscore character to prevent user-defined field codes from colliding with AcclaimIP's standard field codes.

    FIELD:isEmpty_TAX.TECH  -->  Finds all patents where the _TAX.TECH custom field contains no data.

    You'll find that you'll use this query quite often when you want to track the progress of some workflow you designed for you and your group.  

    For example, let's say you want to rate and rank your entire portfolio along several dimensions.  You might create custom fields for your rating system, then query the fields for the empty state (or NotEmpty state) to see how many patents are left to rate.

    The inverse is also true:

    FIELD:isNotEmpty_TAX.TECH  -->  Finds all patents with data in the _TAX.TECH custom data field.

  • Updated on: Mar 26, 2014

    Searching Custom Fields

    If you have been given rights to view a custom field data, you can also search it.  Search custom data fields using field codes or filters and facets.  When your administrator creates the custom field, he or she will have also created a field code for the data.  The custom field code will look something like this:

    _CF:

    Custom fields codes all begin with a leading underscore character.

    To organize custom fields into logical groups, your administrator may place them into virtual folders.  For example a folder called "Ratings" may be created to contain all the rating data on your patents.  In this case, the custom field is preceded by the folder name and a period.  For example:

    _Ratings.IR:

    For this reason, Custom Field Admins are encouraged to keep their folder names and field code names as short as possible.