Report:Delphion/Search History Interface/Stacking Queries
|Report||Patent Coverage Map||Ratings||Comments|
|This search system report was created by the Intellogist Team and is available for viewing only. If you'd like to share your knowledge on Intellogist, please visit the Best Practices, Glossary, or Community Reports pages. Registered users may be notified of any substantial changes to this report by placing a "watch" on the Revisions page, which is the last page listed in the table of contents. To learn more about using the Intellogist "watchlist," see the Watchlist Help page.|| |
|DWPI on Delphion is no longer available, as of March 31, 2012. DWPI data is available on the Thomson Innovation platform.|
Combining queries using Boolean operators is a valuable feature for users that need to construct complex searches. This ability (“stacking” queries) is present in Delphion, and can be performed from the Saved Searches page. However, while most other search providers offer the use of all three major Boolean operators, Delphion allows users to combine queries using “AND” & “OR,” but does not allow searchers to “NOT” out queries.
Using the “AND” function will take two results sets and only choose references that are common to both of them for inclusion in the new, third result set. The “OR” operator will add two queries together, de-duplicating the results set in the process. Both of these operators are useful when constructing results sets for review.
Multiple queries can be combined using the merge option; in fact, an essentially unlimited number of queries may be combined at once, but they must all be combined using either AND or OR. If two different operators are needed, for example, if the user would like to see the results set represented by Query 3 AND (Query 1 or Query 2), this logic must be constructed in Delphion using two separate combination steps.
The omission of the NOT operator when combining searches is a major one. The advantage of this function is the ability to remove already-reviewed documents from another hit list. For example, suppose a searcher has just reviewed an entire hit list of references related to dog collars. The user then desires to widen the scope of the search, and runs a query related to any type of pet collar. Combining the queries to create a new results set (“Query 2 (pet collars) NOT Query 1 (dog collars)”) would allow the searcher to review only the unseen pet collar references, without having to look at the known dog-collar references.
It is a bit strange that the NOT operator may be used when combining saved results sets (work files), but not when combining queries. Because of its usefulness, the omission of the NOT operator when merging search queries is a disadvantage for the system.