Why Basic Patent Search Syntax Details Matter
A patent search can include the right concepts, classifications, and technical terminology and still produce incomplete or unnecessarily noisy results. The problem is often not the search strategy itself, but the way the database interprets the query. Patent databases do not always treat spaces, punctuation, proximity operators, wildcards, and classification codes in the same way. A search string transferred from another platform may therefore behave differently from what the searcher intended. In PatSeer , for example, words separated by a space are treated as an exact match by default. Searching: TA:(guide rna ) looks for the phrase “guide rna .” To find records where both terms appear independently within the title or abstract, the query must use an explicit Boolean operator: TA:(guide AND rna ) Other native syntax features can also make queries cleaner and more precise. The underscore operator helps account for inconsistent drafting. A search for: zinc_finger can retrieve “zi...
.png)
.png)
