Coding field, enter the name of the field, a colon, and the text.
document_date:"January 12, 2007"
A phrase, enclose the phrase in quotes.
“John Joseph Smith”
author:”John Joseph Smith”
Using + and – operators - You can require a term to be matched, or exclude items for which it matches, respectively.
smith +patent -invention
matches "patent" but not "invention", scoring matches of "smith" higher
matches "smith" unless the item was authored by "smith"
Specific combinations of terms - You can use the boolean operators AND, OR, and NOT. “and” and “or” will be automatically capitalized for you, but you must enter “NOT” in all-caps to use it as an operator instead of the word “not.” For best results, use parenthesis to group the combinations together.
author:(smith OR jones)
smith AND (patent OR invention)
(author:smith AND kind:(email OR conversation)) or (author:jones AND document_date:2007-10-12)
(author:smith AND NOT kind:email) or (author:jones AND NOT designated:defense)
Matching Terms or Certain Character Sets - You can search for terms that end in a certain way (up to 6 characters) by placing a "wildcard" in a search term. When adding the wildcard as a prefix, anything beyond 6 characters will be truncated; Suffix wildcard does not truncate the search.
The question mark (?) will match any single character (letter/number/etc.), whereas the asterisk (*) will match any sequence of zero or more characters.
matches john, johnson, johnsen, etc.
*nextpoint.com = nt.com
matches documents containing nt.com
matches "jared", "jarod", etc.
matches any date in June 2007
NOTE: Nextpoint does not support double-ended wildcard searches (E.g. searches such as *bag*)
Embedded Values - If searching in a field which contains an embedded value (e.g. mailbox_path:Emails/Inbox/John Smith Communications/2009) - you can search for the particular value surrounded by asterisks (*) and quotations (").
mailbox_path:"*John Smith Communications*"
will return all mailbox paths which include *John Smith Communications*, even if there is a different year following.
Dates - You have multiple options, including searching before/after specific dates. Prefixing a less-than ("<") or greater-than (">") operator to the date will search for dates before or after the specified one, respectively. Adding an equals-sign after the operator will match dates "on or before" or "on or after" the specified one.
matches dates before July 13, 2007
matches dates on or after July 13, 2007
matches depositions in July and August, 2007
Searchable Coding Fields - To search in a particular coding field, enter the name of the field, a colon, and the text. For your reference, we've compiled a list of all the possible fields built into Nextpoint that you can search here.
For example, in both Review and Prep, to search within a particular folder use the following syntax:
When you create a new custom field, you can use this same syntax to search that field.
Custom Field Range - we currently support numeric custom field range searches bounded in square brackets only
There are several ways you can find documents in Review using the Search bar:
Perform a simple search by entering your term(s) in the box, and clicking the eyeglass icon. This window supports full Boolean searching as well.
Click Advanced to open the Advanced Search window.
Use a Filter Search by selecting the document categories and/or coding you wish to search by, then press Filter Documents. For instance, this filter search would return all Highly Confidential emails that do not contain Production Placeholders.
If you have Standard or Advanced status, on the Analytics tab you can perform a quick search by clicking on any graph or total on the page:
Nextpoint employs Boolean logic with Advanced Search. Enter your data in the appropriate fields and press Advanced Search. Here's a breakdown.
- Search string builds as you enter terms
- Search by Review Status
- Use Boolean operators and proximity search
- More search tools are available in this dropdown, such as word exclusions and fuzzy searches
- Search within specific coding fields
- Click Advanced Search when all terms are entered, and you will be taken to a results page
Examples of syntax using the "Shortcut" field:
To search for documents that HAVE a value: shortcut:*
To search for documents that DO NOT HAVE a value: -shortcut:*
There are various searches that you can run to return all the documents in your case. Wildcard search by itself yields all documents (*).
title:* OR title:NULL
title can be replaced with other fields, such as bates or date
where 0000 is your case ID
To assist in easing your search entry, Nextpoint offers auto-populated values when searching on folders and/or issues.
To make use of this functionality for your folder or issue search, simply start typing folder:" or issue:" and a list of potential values will appear for your selection. See examples of each below:
Yes, you may group ("nest") criteria in your search using parenthesis.
(author:smith AND shorcut:(email OR conversation)) or (author:jones AND document_date:October 10, 2007)
(author:smith AND NOT shortcut:email) or (author:jones AND NOT designated:defense)
A "fuzzy search" can be used to retrieve matches that normally would have been "near misses".
A numeric value on the scale of 0-1 is used to indicate how liberal the included results should be. A value of "1.0" would mean "exact matches only, while a value of "0.0" would match everything (but would lead to significant performance issues). The recommended range for a fuzzy search is from 0.5-0.9. Examples: With a "0.8" numeric value, a search for "plaintiff" would return documents containing "plaintifh" (perhaps a misspelling).
A slash is considered an illegal character and is removed from your search string when it is submitted.
You can normally obtain the desired results by replacing your slash with a wildcard (?) character.To find "/directory/filename.doc" in a custom field called "folder_path"folder_path:"?directory?filename.doc"
Filters produce “AND” search results. For example, filtering would be useful if you were looking for all documents containing the Folder “Defense” and the Issue “Contract Performance.”
If you were looking to run an “OR” search, this can be easily performed using Boolean logic in the search field.
For the previous example, you would type folder:defense OR issue:"contract performance". To use the Filters, click the arrow next to the identifier you wish to search by and press Filter Documents.
Some sample syntax for various stamp searches:
returns all documents with a stamp
returns all documents with Defense label stamp
returns all documents that have been Bates stamped
returns all documents that have not been Bates stamped
In Prep, find a particular exhibit number use the following search syntax:
where PX is substituted with your Folder Abbreviation, and the number is that of the exhibit you are searching for
To search for documents with a particular Bates prefix use the following syntax in the Search window:
where ABC is substituted with your particular prefix
When searching for documents with a particular Bates number use the following syntax in the Search window:
inclusive of any underscores for spaces, hyphens, and/or leading zeros
For Bates numbers with spaces in them use the following syntax:
There are a few ways you can search within a Bates range:
- Enter the Bates Range in the Coding Fields section in the Filter, and click Filter Documents.
- Go to the Advanced Search, and in the bottom section, More Document Options enter the starting and ending Bates numbers.
- Use the following syntax in the Search window:
- Use the following syntax for a Bates range with spaces:
bates:["ABC ABC_000001" "ABC ABC_000002"]
Note: Only in methods 2 & 3 you can change sort criteria to sort by Bates.
To find docs with a specific tag, you can search - "tag:tagvalue"
To save a search, enter your search criteria, execute your search, then click the Save button.
A popup window will open, where you can name your search, and choose whether you want it to be Public so others can access it. Click Save this search, and it will be available.
This information exists in the background metadata, but is not displayed as part of the standard functionality. A custom script could be developed upon request, please inquire for an estimate of the charges.