|
or
The OR operator is simply a space (or you can use a vertical bar). For example, alice abstract
and
alice | abstract
both search for documents containing alice
, or abstract
, or both
alice
and abstract
+
The plus sign is the REQUIRED operator, which also functions like an AND operator. For example, alice +abstract
searches for
documents containing abstract
and optionally containing alice
. To require both alice and abstract use +alice +abstract
.
Please note the lack of a space between the '+' and the required word (alice + abstract
effectively ignores the '+')
-
The NOT operator is a minus sign. For example, alice -abstract
searches for documents that contain
alice
OR do not containabstract
. Note the OR in the previous sentence. Use +alice -abstract
to search for documents that contain alice
AND do not contain abstract
.
Please note the lack of a space between the '-' and the required word (alice - abstract
effectively ignores the '-')
" "
To search for an exact phrase, enclose the phrase in double quotes. For example, "abstract idea"
searches for documents containing exactly that phrase whereas abstract idea
is treated as OR, as discussed above.
" "~N
To search for an certain words ocurring within N words of eachother use a tilde followed by the range. For example, "2019 eligibility guidance"~10
searches for documents in which 2019
, eligibility
and guidance
occur within 10 words of each other.
~
Fuzzy match is a tilde after a word (as opposed to after a quoted phrase in the case of proximity match). In this case, N is how many letters of the word
may be different. The default is 2, but you can explicitly specify 1. (1 and 2 are the only valid values).
For example, blue~1
will match blue
, blues
, and glue
( )
For example, alice +(enfish amdocs)
will search for documents containing alice
and either or
both of enfish
and amdocs
.
*
Currently, if you want to match a partial word suffix operator is an asterisk. For example, elec*
searches for words that start
elec
. If you want to match partial words, use this operator.
To restrict your search to a particular metadata field, use <field>:<search term>
. Fields currently supported are
(please note that spelling and capitalization are important): Application_Number
, Correspondent
, Docket_Number
,
Examiner
, Filer
, Filer_Authorized_By
, CFR_Cites
, Fed_Reporter_Cites
, MPEP_Cites
,
PTAB_Cites
, USC_Cites
, USPQ_Cites
.
For example, +MPEP_Cites:2106 +"electric power group"
searches for documents that contain a cite to MPEP 2106 and contain "electric power group"
Aside from the operators above, most special characters (including & / \ + -) in your search term will be ignored (basically
treated like spaces). For example, an exact phrase search for "held & malloy"
is the same as a search for "held malloy"
(both will return documents containing "held & malloy" and "held malloy").
Where this often comes up is with application numbers (e.g., a search for 13/826,701
is treated as a search for 13
OR (since / is treated as a space and a space is an OR) 826,701
).
NOTE: if you want to search for files associated with a particular application number (Rather than for application
numbers appearing in the text of documents, use just the 8 digit application number and do not include any special characters)
We're working to make the search syntax more intuitive. If have are having trouble formulating a search of getting unexpected results, shoot us an email at [email protected] and we will help you out ASAP.
*To enter multiple values, separate them by vertical bars (e.g., 11111|22222).
Corresponds to the "Document Code" column in PAIR.
The action that happened after the result document. This can be used, for example, to find documents that resulted in a notice of allowance (i.e., the next outgoing action was a notice of allowance). Possible values for this field are generally limited to restrictions and actions on the merits.
The action that happened before the result document. This can be used, for example, to find documents where the previous action was a nonfinal rejection but are not themselves responses to nonfinal rejections. Possible values for this field are generally limited to restrictions and actions on the merits.
The incoming filing/resonse that happened after the result document. Possible values for this field are generally limited to elections and responses to actions on the merits.
The incoming filing/response that happened after the result document. Possible values for this field are generally limited to elections and responses to actions on the merits.
The name of the Examiner listed on the result document.
The name of the Customer Number listed on the result document.
The name of the Correspondent listed on the result document.
The art unit listed on the result document.
The person who signed the result document. This will often be listed as [authorizer]/[actual filer]*
The person whose registration number was used for the incoming action.**
*currently only populated on outgoing actions. Do not use if searching for incoming actions.
**currently only populated on incoming actions. Do not use if searching for outgoing actions.
The "Ex Parte" knowledge base includes a random selection of office actions, responses, appeals, decisions, etc. from public PAIR.
The "Inter Partes" knowledge base includes substantive documents from inter-partes reviews, covered business method reviews, and post-grant reviews.
The "Demo Firm" knowledge base is a demonstration of a firm-specific private knowledge base (In this case, the firm's files for applications filed betwen July 2014 and Feb 2019).
No. The full text of patents and published applications is not included (except specification text is included for private knowledge bases).
To get bibliography, file history, assignments, and pdfs for a particular application, publication, or patent, go here