Search and Analyze
- Nextpoint Search Guide
- Locked Metadata Fields
- Search Hit Highlights
- Search Upgrades, Spring 2020
- How to Report the Page Count of a Folder
- Global Account Search
- Early Data Assessment Details
- Discovery Analytics
- Advanced Search
Our comprehensive Search Guide is outlined below, but if you prefer a PDF version, you can download by clicking on this button:
Download Nextpoint Search Guide
Search Topics Below
- Where to Search in Nextpoint
- Search Syntax Operators - Search_Text, Search_Fields, AND, OR, NOT, Proximity, Exact Phrase, Wildcard
- General Metadata - Author, Date, Document Type, File Extension, File Name, File Path, Title, Root Folder, App Name, Encrypted, Page Count
- Email Metadata - Email Author, Recipients, CC, BCC, Domain, Sender Domain, Receiver Domain, Email Subject, Email Sent, Email Received, Mailbox File, Mailbox Path, Email Message ID
- Document Metadata - Document Title, Document Subject, Document Author, Document Last Author, Created Date Time, Modified Date Time, Last Print Date
- Document Identifiers - Nextpoint ID, Bates, Bates Prefix, Bates Range
- Work Product - Folder, Category, Issue, Responsive Status, Privilege Status, Highlighted, Highlight Notes, Page Notes, Treatments, Exhibit Stamped, Custom Fields, Tags
- True/False Fields - Privileged, Confidentiality, Redacted, Email Thread, Bates Stamped, Native Placeholder, Non-Imaged Placeholder
If you are still having difficulty building your search syntax after viewing the search guide, please contact our Product Support team at support@nextpoint.com.
Where to Search in Nextpoint
Users can log into any Nextpoint Discovery database to view the ANALYTICS tab.
ANALYTICS presents powerful, interactive visualization of your data in graphical form.
Simply click on any of the graphs to view a complete list of the documents in that specific category. The overall progress of your review project is also quickly viewable in the interactive 'doughnut chart’ near the bottom of the page.
To refine the data in your visualizations, just add terms to the SEARCH TO REFINE box on the upper right, and hit return on your keyboard. All data visualizations will redraw correspondingly.
View further details on the Analytics page here >>
The Search bar is available in both Discovery and Litigation databases, and when working in Litigation, can be utilized for searching documents and transcripts. Simply enter your search syntax (additional details on building searches below) and click the eyeglass icon.
Below, we illustrate how you can begin with a simple keyword in the search bar and continually add criteria in order to further refine your results.
If you are learning the nuances of building more complex searches and/or just want some help building your search syntax, there is an Advanced Search functionality to assist.
Building an Advanced Search
To build and run an Advanced Search, start by selecting ADVANCED next to any search bar (as shown above). Here's a breakdown of some of the basics:
- Search syntax builds as you enter terms or make coding selections
- Search by Discovery, Privileged and/or Confidentiality statuses
- Use Boolean operators (AND, OR), look for exact phrases, and enter proximity searches
- More search tools are available via the "More Tools" dropdown, such as word exclusions and fuzzy searches
- Search within specific Bates or Date Ranges
- Search within specific metadata or (custom) coding fields
- Click Advanced Search when all terms are entered, and you will be taken to a results page
Filters are available in any Nextpoint database to the right of the search bar and are extremely useful when looking to return documents which match a particular set of coding or metadata.
It is important to note:
- 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".
- Additionally, Filters CAN NOT be used in conjunction with the search bar. For example, you can not run a search in the search bar and then use the Filters to further narrow. If you do such, the secondary user of Filters will override any search you have input in the search bar.
To use the Filters, click the arrow next to the identifier you wish to search by and press Filter Documents.
If you were looking to run an “OR” search, this can be easily performed using Boolean logic in the search field. For the aforementioned example, you would type folder:defense OR issue:"contract performance".
While the aforementioned search functionalities can be employed to search, analyze, and cull documents across your database, please note there is also search functionality within each individual document.
For databases created on or after December 6, 2021: to search within an individual document, click the PDF search in document viewer, input your search at the top right, and hit return on your keyboard. This will prompt the PDF Search Toolbar and search hit highlights shown on the word(s).
For databases created prior to December 6, 2021: to search within an individual document, once you are in the document viewer, input your search at the top right, and hit return on your keyboard or click search immediately below your input.
Want your keyword searches persistently highlighted when they hit on a document? Read more about setting up and utilizing Key Terms here >>
Search Syntax Operators
| Operators | Description |
|---|---|
| Term(s) / Words |
For any keyword search, simply input the term in your search bar and click return/enter to execute the search. Doing so will query the database for any search text or metadata which hits on your keyword and return resulting documents to your grid view. EXAMPLE: patent will return all documents containing the term patent anywhere on the document or in the metadata. |
| Search_Text: |
Will return all documents containing the term in the search text of the documents, only. If an input search hits on only a metadata field (e.g. Document_title), but not in the search text, that document will not be returned in your results. EXAMPLE: search_text:patent will return all documents containing the term patent in the search text of the document, only. |
| Search_Fields: |
Will return all documents containing the term(s) in the coding and metadata of the documents, only. EXAMPLE: search_fields:patent will return all documents containing the term patent in the coding/metadata of the document, only. USE CASE: Depending on the quality of any scanned documents and/or handwritten notes, your document search text may not always be comprehensive or extremely useful. Instead, many users will annotate or code documents using fields. As coding takes place over the years, the coding can become inconsistent and users have a difficult time knowing which field to search. In the above example, search_fields:patent will allow the users to search across fields without knowing the exact field(s) the term patent could appear (e.g. attorney_notes:patent OR reviewer_notes:patent OR title:patent). FORMATTING NOTE:
|
| Operator Hierarchy |
General hierarchy is NOT > AND > OR Without parentheses present in your search syntax, any NOT search will be performed before any AND search, and any AND search will be performed before an OR search. If you would like to segment your search syntax so a particular group of criteria are considered together (e.g. this OR that OR that), then make sure to enclose that portion of your syntax in parentheses. EXAMPLE: (batch:2 OR batch:3) AND confidentiality:CONFIDENTIAL will look for any documents in batch 2 or batch 3 that are marked confidential. The OR search component will be performed before the AND search because the parentheses were input as a directive to consider that section as a segment. |
| AND, + |
Connecting two (or more) terms/fields with AND will return results with both terms - this AND that. You can also replace the AND with a plus sign (+). If doing so, ensure there are spaces on each side of the + as shown in below example. EXAMPLE: patent AND invention (or patent + invention) will return documents which contain both terms. If a document does not contain both of those terms, it will not be returned for this search. |
| OR, ( ) |
Connecting two (or more) terms/fields with OR will return results with either terms or fields - this OR that. EXAMPLES: patent OR invention will return all documents which contain patent or invention. So long as a document contains one of those terms, it will be returned for this search. custodian:"smith, john" OR custodian:"miller, barbara" will return all documents from either of the two custodians. TIP: You can also enclose two or more terms (not applicable to fields) in parentheses to imply an OR search, so the aforementioned would be (patent invention). |
| NOT, - |
Excludes term or field from results - this NOT that. You can also replace NOT with a minus sign (-). If doing so, make sure the - is immediately preceding the second term as shown in the below example. EXAMPLE: patent NOT invention; patent -invention - Documents with the term patent but without the term invention |
| ~ |
Proximity search, searching within n words EXAMPLE: “patent invention”~5 - Documents containing the term patent within five words of invention |
| “ ” |
Surrounding any sequence of terms in quotation marks will imply an exact phrase when searching. EXAMPLE: "prior art" - Documents which contain the exact phrase "prior art" |
| * |
You can input an asterisk(*) before and/or after a word to account for variations (e.g. report* will return reporting, reported, reporter, etc..). While there is no limit on characters when a wildcard is placed at the suffix of a word, any wildcard placed as a prefix (before the term) will truncate to the last 6 characters. EXAMPLES:
IMPORTANT FORMATTING NOTES:
|
General Metadata
General Rule of thumb for searching within any coding/metadata field is field_name:value
| Command | Description |
|---|---|
| Author |
Combined field identifying the author of an email or document. EXAMPLE: Author:smith@nextpoint.com |
|
Document_Date or Date |
Combined date field with the following priorities — Emails: Sent date then received date. Efiles and non-email attachments: modified date, then created date. EXAMPLES: Specified Date >> Document_date:01/10/2020 - can also use Document_Date:01/10/2020 Date Range, Years >> Date:[2001 2019] - returns results for all documents within that range of years. Can also use exact dates to narrow your date range. Date Range, Specified >> Document_Date:["January 10, 2020" "January 20, 2020"] - returns results for all documents within the specified date range. Date Range, Greater/Less than >> Date:>2001-09 - returns results for all documents after September 2001; can also use Date:>09/2001 |
| Document_Type |
Category of document based on its origins:
These values can be overwritten via otherwise provided values in a loadfile. EXAMPLE: document_type:email AND Date:["January 10, 2020" "January 20, 2020"] - all emails dated between 1/10/2020 - 1/20/2020 |
| File_Extension |
File extension of the processed document EXAMPLE: File_extension:xl* - all versions of Microsoft Excel documents (i.e. xls, xlsx, etc.) |
| File_Name |
Original file name of native file — contains subject of email message for email records EXAMPLE: file_name:mountain* - all documents containing "mountain and anything thereafter" in the File Name. |
| File_Path |
Location from which the file was collected EXAMPLE: When a document has a File Path field with the value: \John.Smith@ClientFirm.com.pst\Top of Outlook data file\John.Smith@ClientFirm.com (Primary)\Recoverable Items\Purges\woof.pdf This list of searches is not exhaustive, but is indicative of the searches that return this document:
|
| Title |
Combined field that pulls the email subject from emails and the title field from e-files and attachments. EXAMPLE: title:report - all emails containing report in the Email Subject line, and all documents containing report in the document title |
| Root_Folder |
Root folder location in your database's File Room at time of processing. This encompasses any loose files imported from File Room without a load file. EXAMPLE: root_folder:EDRM_Data* - all documents stemming from a File Room folder beginning with "EDRM_Data" and ending with anything thereafter (e.g. EDRM_Data_001, EDRM_Data_002, etc...) |
| App_Name |
Application Name field value pulled from metadata of native file. EXAMPLE: app_name:"Microsoft Excel" - all documents containing Microsoft Excel within the App Name Field. Note: If looking for something like "All excel files", we recommend relying on the file_extension:xl* search as the App Name may not always be populated and/or consistently named when populated. |
| Page Count |
Count of processed image pages for a document. EXAMPLES: page_count:0 - all documents which have zero imaged pages in Nextpoint (can assist in identifying identifying documents which didn't image) page_count:>8 - all documents which have more than eight (8) imaged pages in Nextpoint (can assist in identifying documents which are "more or less than X number of pages") page_count:[11 24] - all documents which between 11 to 24 imaged pages in Nextpoint |
Email Metadata
General Rule of thumb for searching within any coding/metadata field is field_name:value
| Command | Description |
|---|---|
| Email_Author |
Author of an email. EXAMPLE: Email_Author:smith@nextpoint.com |
| Recipients |
Recipient(s) of an email; Plural regardless of singular or multiple recipients EXAMPLE: Recipients:smith@nextpoint.com |
| CC |
Recipient(s) carbon copied on an email. EXAMPLE: cc:smith@nextpoint.com |
| BCC |
Recipient(s) "blind copied" on an email EXAMPLE: bcc:smith@nextpoint.com |
|
Above searches are dependent on what format your data is brought into Nextpoint. Often inboxes are set where an individual’s actual name appears in the To/From/CC/BCC fields, in lieu of their email handle. For example, cc:smith@nextpoint.com could also be formatted as cc:"John Smith" or cc:smith. Before performing your email search, we suggest reviewing a couple sample emails or the Analytics "widget" section for further, quick insight. |
|
|
Email Searching: Nextpoint stores email addresses as a whole and split up for ease of searching. EXAMPLE: When a document has text with the email address ‘russel.wilson@nextpoint.com’ this list of searches is not exhaustive, but is indicative of the searches that return this document:
The term `badger2` will also return documents with the email address bucky.badger2@uwbadgers.com |
|
| Domain |
Returns all emails to or from a particular domain. This includes the author, recipients, cc, and bcc fields. EXAMPLE: Domain:nextpoint.com - all emails containing @nextpoint.com in the author, recipients, cc, or bcc fields. Note: We recommend against using an @ in your search. This character is treated like a space, and thus, you may return unexpected results. |
| Sender_Domain |
Returns all emails from a particular domain. This includes the author field. EXAMPLE: Sender_Domain:nextpoint.com - all emails containing @nextpoint.com in the author field. Note: We recommend against using an @ in your search. This character is treated like a space, and thus, you may return unexpected results. |
| Receiver_Domain |
Returns all emails to a particular domain. This includes the recipients, cc, and bcc fields. EXAMPLE: Receiver_Domain:nextpoint.com - all emails containing @nextpoint.com in the recipients, cc, and bcc fields. Note: We recommend against using an @ in your search. This character is treated like a space, and thus, you may return unexpected results. |
| Email_Subject |
Subject line of an email. EXAMPLE: email_subject:lunch - all emails containing lunch in the subject line |
|
Email_Sent + Email_Received |
Date-time of a sent email, or date-time of an email that was received. EXAMPLES: Specified Date >> email_sent:01/10/2020 - can also use Document_Date:01/10/2020 Date Range, Years >> email_sent:[2001 2019] - returns results for all documents within that range of years. Can also use exact dates to narrow your date range. Date Range, Specified >> email_received:["March 13, 2019" "April 6, 2019"] - returns results for all documents within the specified date range. Date Range, Greater/Less than >> email_received:>2015-09 - returns results for all documents after September 2015; can also use Date:>09/2015 |
| Mailbox_File |
If present, filename of mailbox archive email was extracted from. EXAMPLE: mailbox_file:john.smith444_gmail.com.mbox - all emails and attachments which stemmed from the compressed mailbox file of "john.smith444_gmail.com.mbox" TIP: Want to find only the emails from a particular mailbox_file? Try searching mailbox_file:john.smith444_gmail.com.mbox AND document_type:email |
| Mailbox_Path |
Mailbox path represents the full sequence of mailboxes and sub-mailboxes that specifies the location of a certain, named mailbox. EXAMPLE: mailbox_path:inbox - all emails + attachments which stemmed from a particular location within a mailbox_file. TIP: Commonly, we see structures like "top level mailbox/Inbox", "top level mailbox/calendar files", "top level mailbox/contacts", but it is dependent upon how emails were organized and collected from the source. If there are no mailbox subdirectories contained within the source Mailbox_file, then this field will not be populated. |
| Email_Message_ID |
Email message ID field value extracted from the metadata of the native file. EXAMPLE: email_message_id:"<ABC1deF23gHHIJk445LM@mail.gmail.com>" - all documents with a particular Email Message Id TIP: A direct link to a particular message ID search syntax is always available at the bottom right in your document viewer under the section titled "Extracted Metadata" |
| Email_thread:true | True if email conversation starter |
| Is_attachment:true | True if file is attached to an email |
| Has_attachment:true | True if email has an attachment |
Document Metadata
General Rule of thumb for searching within any coding/metadata field is field_name:value
| Command | Description |
|---|---|
| Document_Title |
Title field value extracted from the metadata of the native file. EXAMPLES: document_title:"calendar wizard" - all documents which have the exact phrase "calendar wizard" in the Document Title. document_title:expert* - all documents which have the keyword expert* (the asterisk accounts for "anything after" expert, like expert, experts, expertise..) |
| Document_Date |
EXAMPLES: Specified Date >> Date:01/10/2020 - can also use Document_Date:01/10/2020 Date Range, Years >> Date:[2001 2019] - returns results for all documents within that range of years. Can also use exact dates to narrow your date range. Date Range, Specified >> Date:["January 10, 2020" "January 20, 2020"] - returns results for all documents within the specified date range. Date Range, Greater/Less than >> Date:>2001-09 - returns results for all documents after September 2001; can also use Date:>09/2001 |
| Document_Author |
Author field value pulled from metadata of the native file. EXAMPLES: document_author:(robert david) - all documents containing Robert OR David in the Document Author Field document_author:(robert AND putnam) - all documents containing Robert AND Putnam in the Document Author field document_author:* - all documents containing any value in the Document Author field (is not blank) |
| Document_Last_Author |
Last ‘Saved By’ field value pulled from metadata of the native file. EXAMPLES: document_last_author:(robert david) - all documents containing Robert OR David in the Document Last Author Field document_last_author:(robert AND putnam) - all documents containing Robert AND Putnam in the Document Last Author field document_last_author:* - all documents containing any value in the Document Last Author field (is not blank) |
| For any date searches
Context Aware: Any date_time search will take into consideration any context you do or don't provide.
Flexible Formatting: You can search for a date (or range of dates) in a variety of common formats.
|
|
|
Created_Date_Time |
Creation date and time of the native file when imported without produced images. EXAMPLES: created_date_time:2003-01-22 - all documents with a created_date_time of 2003-01-22. created_date_time:>1-17-09 - all documents with a created_date_time greater than (after) 1/17/2009 created_date_time:[3/19/09 2015-04-01]- all documents with a created_date_time between 3/19/2009 - 04/01/2015. |
| Modified_Date_Time |
Date and time the native file was last modified EXAMPLES: modified_date_time:2003-01-22 - all documents with a modified_date_time of 2003-01-22. modified_date_time:>1-17-09 - all documents with a modified_date_time greater than (after) 1/17/2009 modified_date_time:[3-19-09 04-01-2015] - all documents with a modified_date_time between 3/19/2009 - 04/01/2015. |
| Last_Print_Date |
Date the native file was last printed (MS Office documents) EXAMPLES: last_print_date:2003-01-22 - all documents with a last_print_date of 2003-01-22. last_print_date:>1-17-09 - all documents with a last_print_date greater than (after) 1/17/2009 last_print_date:[3-19-09 04-01-2015] - all documents with a last_print_date between 3/19/2009 - 04/01/2015. |
Document Identifiers
General Rule of thumb for searching within any coding/metadata field is field_name:value
| Command | Description |
|---|---|
| Nextpoint ID |
Unique number assigned to every document upon creation in your Nextpoint database. EXAMPLES: ID:1234 ID:(1234 5678 9101) - Becomes an OR search, and pulls all three documents |
| Bates |
Bates number assigned to a document, whether it was stamped through Nextpoint, or elsewhere. EXAMPLES: ABC000001 - Returns the document that contains this exact stamp on a page of said document Bates:* - Returns all Bates assigned documents within your database Bates:(ABC000001 ABC000015 ABC000027) - Returns each document that hits on that particular Bates number. Essentially this becomes an OR search instead of a range search TIP: Bates numbers with spaces need to be in quotes. Bates:"ABC 000001" |
| Bates Prefix |
The alphabetical portion of the Bates stamp. EXAMPLES: Bates_prefix:ABC - Returns all documents with Bates Prefix ABC. TIP: If your Bates prefix has any separating characters like underscores _ , hypens - , spaces, periods, etc.. you do not need include those characters in your search. |
| Bates Range |
Documents with Bates numbers within an identified range EXAMPLE: Bates:[ABC000001 ABC000015] Bates numbers with spaces need to be in quotes. Bates:[“ABC 000001” “ABC 000015”] |
Work Product
General Rule of thumb for searching within any coding/metadata field is field_name:value
| Command | Description |
|---|---|
| Folder |
Will return all documents contained within a particular folder in Nextpoint. EXAMPLE: Folder:”John Smith Inbox” - Will return all documents within the John Smith Inbox" folder in Nextpoint FAQ: How do I search for a certain range of documents in a folder (e.g. the first 1,000 documents in the folder)? folder:"folder name":[1 1000] |
| Category |
Will return all documents associated with a particular category via their folder assignment. Searching for a particular category will translate on the back-end as an OR search across all folders within that category. EXAMPLE: Category:”Productions” - Will return all documents within the folders associated with the Productions category. The back-end syntax for Category:"Productions" translates as (folder:"prod1" OR folder:"prod2" OR folder:"prod3") |
| Responsive_Status |
Will return all documents tagged as “Responsive” EXAMPLE: Review_status:responsive - Will return all documents tagged as “Responsive” |
| Issue |
Will return all documents tagged with a particular responsive issue EXAMPLE: Issue:damages - all documents tagged with issue damages |
| Privilege_Status |
Will return all documents tagged with a particular privilege reason EXAMPLE: Privileged:Work-Product - all documents tagged as privileged, work-product |
| Tags |
Manually added work product tags applied via Bulk Actions or at the document-level EXAMPLE: Tags:AJEML - all documents which have been tagged by an end user with the specific tag AJEML. TIP: If your tag is specific enough (e.g. AJTAG), you can simply enter the tag text in your search bar and click enter/return |
| Highlighted |
Will return all documents with highlight image markups AND any associated highlight issue. EXAMPLE: Highlighted:true TIP: If you would like to find all documents with highlights, regardless if an issue has been assigned, it is recommended you use the FILTERS. Open your Filters > navigate to the Work Product section > Document Annotations subsection > select Documents with Highlights > Filter Documents. |
| Highlight_Issues |
Will return all documents with highlight image markups AND a particular highlight issue. EXAMPLE: Highlight_Issues:"Fraud Claim" will return all documents highlighted and associated with Fraud Claim issue. |
| Highlight_Notes |
Documents with highlight image markups associated with a particular note. EXAMPLE: Highlight_Notes:collusion will return all documents with the term collusion in the highlight notes. |
| Page_Notes |
Documents with page notes associated with your specific criteria. EXAMPLES: page_notes:"for redaction" - Returns all documents with the exact phrase "for redaction" on a page note. page_notes:* - Returns all documents with a page note(s) TIP: You can also find documents with Page Notes by using your Filters. Open Filters > Work Product > Select “Documents With Notes Only” |
| Redaction_Notes |
Documents with redaction notes associated with your specific criteria. EXAMPLES: redaction_notes:SSN - Returns all documents with SSN in the redaction note(s) redaction_notes:* - Returns all documents with a redaction note |
| Designation_Notes | Transcripts with designation notes associated with your specific criteria.
EXAMPLES: designation_notes:"present at scene of accident" - Returns all transcripts with the exact phrase "present at scene of accident" associated with a page/line designation note. designation_notes:* - Returns all transcripts with a designation note(s) |
| Treatments |
Utilize the filter to narrow to all documents with treatments applied in theater mode Open Filters > Work Product > Select “Has Treatments” |
|
Stamped |
Will return all documents with a specified exhibit name (folder) and number. The search syntax for a particular exhibit is Folder:'folder abbreviation':stamp number EXAMPLES: folder:PX:5 - Returns Plaintiff Exhibit 5 Stamped:* - Will return all documents that contain an exhibit stamp applied within Nextpoint folder:px:[1 10] - Will return Plaintiff Exhibits 1-10 (the brackets [ ] indicate a range of exhibits) |
| Fields (Documents and Transcripts) |
General rule of thumb for searching is field_name:value DOCUMENT EXAMPLE: Attorney_notes:important - Search for a term or phrase from a note that you may want to locate Request_for_Production:5 - Search a value from a picklist. Use case: If you had all of your request for production numbers listed in a custom picklist field, and coded documents to each request, you could pull up all documents that pertained to a particular request through the above search. TRANSCRIPT EXAMPLE: Volume:2 - Search for a specific transcript volume Deposing_Attorney:Smith - Returns and transcript(s) containing "Smith" in the Deposing Attorney transcript field. |
True/False Fields
General Rule of thumb for searching within any coding/metadata field is field_name:value
| Command | Description |
|---|---|
| privileged:true | True if document has at least one privilege tag |
| confidentiality:true | True if one document is marked with Confidentiality in Nextpoint |
| redacted:true | True if one document is marked with redactions within Nextpoint |
| Email_thread:true | True if email conversation starter |
| Is_attachment:true | True if file is attached to an email |
| Has_attachment:true | True if email has an attachment |
| Bates_Stamped:true | True if Bates stamped within Nextpoint |
| Has_native_placeholder:true | True if native placeholder was inserted and Bates stamped, as it was a file type that needed to be produced in its native/original form, even though it does have an image in Nextpoint (i.e. excels) |
| Non_imaged_placeholder:true | True if a non-imaged placeholder was inserted and Bates stamped, because it was a file type that does not image through traditional software (I.e. audio/video files) |
| Encrypted | True if native document was encrypted on import. Helpful to search for encrypted:true to locate all files which need a password |
Nextpoint Search Guide
To assist our users in protecting the integrity of both native and user-generated metadata, Nextpoint has released the ability to prevent certain metadata fields from being edited.
Beginning on April 18, 2022, all of the pre-created metadata fields in new and existing databases will be locked by default, preventing users from changing any of the data in any of these fields. Advanced users have the ability to lock and unlock any fields in a database including custom coding fields. Once locked, fields cannot be edited at the document level or via bulk action unless they are first unlocked by an advanced user. The information will remain viewable, but at the document level, locked fields will be greyed out, preventing users from editing them. Nextpoint will maintain a "Field Modification History," so users can gain insight on who locked/unlocked specific fields.
Locking/Unlocking Fields
To unlock individual fields in your Nextpoint discovery database, navigate to "Settings" > "Coding" > "Fields." In a Nextpoint litigation database you need to navigate to "More" > "Settings" > "Documents" > "Fields." From there you can:
1. Unlock individual locked fields.
2. Unlock all fields at once.
Similarly, for the same location you can:
1. Lock individual unlocked fields.
2. Lock all unlocked fields at once. Note: the "Unlock all" button becomes a "Lock all" button when a majority of the fields are unlocked.
Field Modification History
To access the "Field Modification History," select the clock icon at the top of the "Fields" section.
From here you can Search (1) on the list of field modifications, sort (2) the list, and export (3) the list as a PDF. The "Field Modification History" will also record when fields are added or deleted.
Editing Document Fields
At the document level, unlocked fields (1) will remain white and editable. While you will still be able to read information in locked fields (2), they will appear greyed out and will not editable.
When attempting bulk actions on a set of documents, unlocked fields (1) will appear in black text and can be selected. Locked fields (2) will appear in grey text and can not be selected for bulk actions.
Locked Metadata Fields
*Search hit highlights are available in all databases created on, or after, December 6. Read more at the end of this article as to how you will be able to retroactively fit your legacy databases with search hit highlights in the future.
Navigating Search Hit Highlights
Now, when you run a search in a database with search hit highlights, Nextpoint will remove any field:value combinations, and carry any keywords through to the document-level.
For example, the below search reads folder:"BZ and BA Emails" AND (takeout test counting).
Upon clicking into any of the resulting documents and entering the document viewer, folder:"BZ and BA Emails" has been removed, but the terms takeout test counting remain in the search bar at the top center of the document viewer.
You will also notice the search terms are highlighted within the document.
The terms from the search bar will also be presented in a toolbar at the top left of the document. We refer to this as the PDF Search toolbar because PDF images are what facilitate the search hit highlights you see.
These PDF images are a new component of the document viewer and immediately upon release, will only be available in databases created on, or after, December 6. Read more at the end of this article as to how you will be able to retroactively fit your legacy databases with search hit highlights in the future.
Don't see the PDF Search toolbar? Make sure to toggle to the PDF Search Viewer Mode at the top left of your document.
A Closer Look at PDF Search Toolbar
Once in the document, you can navigate a series of tools for your document review in the PDF Search Toolbar.
- Thumbnail View, provides thumbnail image for all pages in document
- Toggle pages
- Highlight all, Match Case, Whole Words
• Highlight all: When enabled, all occurrences of the searched term(s) will be highlighted. Use the up/down arrows to toggle through the different term hits. Current term will be highlighted in green.
• Match case: When enabled, considers capitalization of searched terms.
• Whole words: When enabled, only exact matches of searched term(s) will be highlighted. - Zoom is set to Automatic Zoom by default; adjust as needed
- Drop-down menu
• Rotate: This option is not a permanent rotation, but a great temporary rotate option
• Text Selection Tool: Copy/paste of text directly from the document.
• Odd and Even Spreads: Side-by-side page view of document pages.
Search Hit Highlights in Legacy Databases
As it relates to search hit highlights, a legacy database is any Nextpoint database created before December 6, 2021. We have outlined below, several FAQ's on search hit highlights for legacy databases, but if you have more particular questions, please contact your firm's Client Success Director.
- Why doesn't my database have search hit highlights?
Search hit highlights will be available in all Nextpoint databases created on, or after, December 6th. We expect to introduce a tool next month that will allow us to implement this feature in legacy databases for an additional fee. -
How do I navigate search hits if my database does not yet have search hit highlights?If you are currently working in a legacy database, you will navigate search hits similar to before the release. When searching via the search bar at the document-level, you will be presented with hyperlinked page numbers for the result(s) and provided associated search hit context. Notably, all other updates in this release are available to you.
-
How do I implement search hit highlights on my legacy database(s)?
We will release a tool in the coming weeks that allows us to implement search hit highlights in legacy databases for an additional fee. Once the tool is released, all legacy databases will have a new icon next to document-level search bar. Advanced database users will be able to click this icon to initiate a request that their database be upgraded with search hit highlights.
Questions? Feedback? Please contact our team at support@nextpoint.com.
Search Hit Highlights
Have you noticed recently that Nextpoint search is SUPER fast? 
Nextpoint upgraded our search technology in March 2020, and with this upgrade came increased indexing and searching speeds, more stability, and the opportunity to continue to scale our search functionality as we move forward.
In addition to making finding your documents faster than ever, we also added several functionality updates which will make finding your documents easier than ever. We've outlined the updates below and included several examples in hopes of acquainting you with ways you can leverage these new functionalities in your daily practice.
Questions?
Please contact your Client Success Director, and we will be happy to further discuss these recent updates.
Bates Prefix
The Bates prefix field is derived from the Bates start of a document. Currently, this is a search-only field, but has also been provided as a field on the Analytics page as a custom widget.
Prior to this update, you could only locate all documents with a particular Bates prefix using a search formatted like Bates:ABC*, but now, you can also search Bates_prefix:ABC.
Important to Remember
- If your Bates prefix has any separating characters like underscores _ , hypens - , spaces, periods, etc.. you do not need include those characters in your search.
- For example, for Bates prefix "ABC_00001", the search is Bates_prefix:ABC
- You can also search using the format Bates_prefix:ABC*.
- The wildcard following the prefix accounts for the prefix and "anything after". So, in this case, it could be documents with the Bates prefixes ABC_#### or ABC_Priv_####.
Additional Note Types
You can now search on these a additional notes fields:
- redaction_notes
- page_notes
- designation_notes (transcripts in Prep)
While these fields all previously existed, they were not indexed for searching and had to be located via a Filter. Now, you can search these fields like any other text field in Nextpoint.
Keep in mind the general rule of thumb when searching these fields is field_name:value.
So, for example, if you want to search for all documents with page notes reading "for redaction", the search syntax will be page_notes:"for redaction" (see above example).
1 | More flexible formats for date/time searches
You can now search for a date (or range of dates) in a variety of common formats as opposed to the specific format previously required.
These more flexible search formats apply to all default date fields in Nextpoint: Date, Email_Sent, Email_Received, Date_Time_Created, Modified_Date_Time, and Last_Print_Date.
This also applies to any (custom) Date input type fields you create in your database.
EXAMPLE - Singular Date
Any of the below searches will return results with a date of January 20, 2020:
EXAMPLES - Date Range
Any of the below searches will return results with a date range January 10, 2020 - January 20, 2020:
Please note these abnormal values which won’t work in range searches: Early 1900s; 2020-02-00
2 | Context aware date/time searches
Date searches will now take into consideration any context you do or don't provide.
EXAMPLE - Without Context
A search with no time value like email_sent:2020-01-01 will return all documents with an email_sent value of that date, no matter the time of the day.
EXAMPLE - With Context
A search with a time value like email_sent:”2020-01-01 18:51:32“ will return results only for that time.
This upgrade also introduced improved email tokenization, which means more flexibility for our users when searching email addresses.
When a document has text with the email address ‘russel.wilson@nextpoint.com’ this list of searches is not exhaustive, but is indicative of the searches that return this document:
- russel.wilson@nextpoint.com
- nextpoint.com
- russel.wilson
- russel
- Wilson
- russ*
- wil*
The term `badger2` will also return documents with the email address bucky.badger2@uwbadgers.com
By now, you may have noticed a trend in having more flexibility in your search syntaxes, and that continues to ring true when it comes to File Path and Mailbox Path searches. If you want to use any part of your File or Mailbox Path(s) to recreate a portion of the original file structure, this update will be incredibly helpful in doing so.
The example below illustrates just how many ways you can split up a path to locate a particular grouping of emails and/or documents.
EXAMPLE
When a document has a File Path or Mailbox Path Field with the value:
\John.Smith@ClientFirm.com.pst\Top of Outlook data file\John.Smith@ClientFirm.com (Primary)\Recoverable Items\Purges\woof.pdf
This list of searches is not exhaustive, but is indicative of the searches that return this document:
- file_path:"John.Smith@ClientFirm.com.pst"
- file_path:"recoverable items"
- file_path:purges
- file_path: * purges * (no spaces in NXP)
- file_path:*purges
- file_path:"outlook data"
- file_path:outlook
- file_path:John.Smith@ClientFirm.com
Keep in mind, if you need to be more specific, you can build a more robust sytax using and AND to connect your two paths (e.g. file_path:John.Smith@ClientFirm.com AND file_path:"recoverable items" may help eliminate recoverable items from another custodian's mailbox).
Letters with accents will now fold into letters without accents. This converts alphabetic, numeric, and symbolic characters that are not in the Basic Latin Unicode block (first 127 ASCII characters) to their ASCII equivalent, if one exists.
EXAMPLES
- Searches for acai will return results with acai and açaí.
- The filter changes André to Andre for more comprehensive searching.
You can now use wildcards at the beginning and end of your search to account for variations.
EXAMPLE
If you are looking for variations/tenses of the word "enact", you can search for *enact*
Nextpoint will return documents which hit on enact, reenact, enacted, reenacted, etc...
With this upgrade, we also increased the maximum number of results we can display in your grid view from 10,000 to 1,000,000.
This is applicable when viewing a set of search results in your Grid View like you see in the image below. The limit has been increased, thus letting you click through to more pages of results and/or manually input the page number of results and click "Skip to Page".
Maintaining a maximum number of results we can display will ensure we continue to optimize performance of your databases. Questions on how to handle "more than 1,000,000 results? Read more here >>>
Search Upgrades, Spring 2020
In your Nextpoint database, there are several ways to obtain the page count of a particular folder of documents.
Get Page Count
*The below action is only available in Nextpoint Discovery.
- Click on the three-dot menu next to any folder title, and click "Get Page Count" from the drop-down list.
- A report will be generated and emailed to you, detailing page counts for each relevancy status within the folder.
Page Count on Export
*The below action is available in Nextpoint Discovery and Litigation.
- Click on the three-dot menu next to any folder title, and click "Export" from the drop-down list.
- A report will be generated and displayed in the blue box detailing the page count total for all documents in the folder.
How to Report the Page Count of a Folder
While often it is logical and beneficial to break up databases for performance, access, and/or organization reasons, we know it may also sometimes be helpful or necessary to be able to search across multiple databases with one search.
Global Account Searh provides users the ability to search across databases (to which they already have access) and share those results with other users in the account.
Who can access Global Account Search?
Accounts on our All-Access plan have access to Global Account Search. To add Global Account Search to your Nextpoint account, please contact your Account Director.
If and when added, all users in the account can access the Global Account Search interface, but each user will only be able to search on and view results for databases to which they have access.
How to Use Global Account Search
Outlined below are instructions for locating and using Global Account Search. Whether you need to locate related documents across relevant litigation, pull testimony from a particular expert witness across different matters, research documents and testimony from previous litigations, or more, Global Account Search can assist in providing insight and transparency across all your matters in Nextpoint.
Global Account Search can be found via the top-left database drop-down when you are logged in to your Nextpoint account.
To get started, simply click the drop-down > select "Global Account Search"
When you first make your way to Global Account Search, the interface will display “No Results” and ask you to select databases to search. Click the underlined “Select Databases” OR the Green Select Databases button.
Important Note on Database Access
Users are only permitted to search databases to which they already have access.
A “Select Database” slider will pop up, and you will see a list of databases to which you have access. If you do not have access to a particular database, it will not be available for selection in the list.
If you would like to refine the databases displayed in your list, enter criteria in the search bar provided at the top. This is helpful if you want to select and search all databases for a particular project, practice area, client, etc...
Once you are ready to select your databases to search, either click the top selection box to “Select All” from your list, OR click the down arrow beside the box to make one of the four following selections:
- All account databases: Selects all databases in the account. Reminder, you will only see (and be selecting) databases to which you have access. If you later share these results with another account user, they will be able to view results from all databases in the account to which they have access.
- My ## databases: Selects all databases to which you have access. If you later share these results with another account user, they will only be able to view results from the databases in your selection to which they have access.
- ## matching databases: If you refine the list of databases as mentioned above, “My # databases” will change to → “## matching databases”. This option selects all databases which matched your search entered in the “Refine Database List” box at the top. If you later share these results with another account user, they will only be able to view results within those matching databases to which they have access.
- None: Removes any existing selections, likely allowing you to “start over”
Once you have selected your databases, click “Set Databases”.
You are now ready to run your search. Insert the search criteria desired, keeping the below parameters in mind:
- Searching is limited to keywords, phrases, boolean, and proximity search syntaxes. These said searches will look in both document search text AND metadata.
- Date restrictions are currently not available in Global Account Search, but searches can be further refined in individual databases.
- Search results are provided in real time, broken out by database, and include the counts of documents, deposition transcripts, and proceeding transcripts hits.
Your results return below the search bar and hyperlink any associated documents, transcripts, or proceedings hits. Click any of the hyperlinked numbers to navigate to the respective database (it will open in a new tab).
To share your results with another user in the Account, click the “Share Results” button from the main Global Account Search page.
A pop-up modal will appear from which you can select the user you would like to share your results with, insert a search title, and enter a corresponding message for the recipient.
If another user shares Global Account Search results, the recipient will receive an email similar to the following:
The receiving party can then click on the orange “View the Results” button and they will subsequently be redirected to the Global Account Search page to review the shared results.
Want to learn more about Global Account Search and how you can add to your firm's Nextpoint account? Contact your Account Director or our Client Support Team at support@nextpoint.com.
Global Account Search
Control cost and gain insight with early data assessment.
You’ve got millions of files that may be vital to your case. Or they may be digital deadweight.
Nextpoint’s early data assessment (EDA) service eliminates unnecessary files and gives you customizable metrics, analysis, and business intelligence to manage your case.
Using tactics like advanced deduplication, analytics, reporting, filtering, and culling, we can cut down any size eDiscovery challenge. Advanced reporting and analytics give you and your clients more insight into your data to make informed decisions. While you can take advantage of EDA for eDiscovery projects of all sizes, it is particularly relevant when confronted with BIG data problems.
Nextpoint’s expert Data Strategy team can analyze and categorize mountains of data, eliminate the unnecessary stuff, and then organize it into a usable archive.
Data can be sent to Nextpoint either on usb hard drives, or transferred to a case-specific file room (NOTE: Data sets requiring downloading to the Nextpoint office will require additional time before processing can begin).
During processing, date and time fields are pulled from the intrinsic properties of a given document. If date and time from the original operating system is needed, a forensic copy must be collected and sent to Nextpoint.
Nextpoint is not responsible for forces beyond our control such as data/drives lost in transit or drive mechanical failures. Data sent to Nextpoint must therefore be a copy, no single copy data will be accepted. As such no copies or backups will be made to prevent data loss.
The following reports will be provided upon completion of processing:
Archive Extraction Errors– File listing of the archive error files within the report scope which includes details about the error messages received and general descriptive information regarding the error file.
ESI Filter Report – This shows how a data set was reduced via the filtering and culling settings within the system. If the number of archives in the Report Header of this report is subtracted from the Post Duplicate Removal Total Files count, this is the number you would receive when running any of the other reports using the Project Level Deduplication setting.
File Type Frequency – This report groups the files within the report scope by application type. Within the report the pie chart shows the top X% of the file types within the report scope and the table below gives a listing of every file type identified, the number of these files, and the associated size.
Document Timeline Report – Shows the files contained within the report scope on a timeline. Date Sent is used for emails and Last Modified Date is used for efiles. Attachment counts are added into the overall emails counts within the report. The visual shows a line charts by month or year with a different color line per Custodian and the table provides a workable listing broken down by Custodian, month/year, efile, emails, size, and percentage of files within the scope. This report is helpful for understanding trends within the data related to collection and work product details.
Sender Domains Report – A listing of the sender domains as well as the associated email addresses per domain contained within the report scope. the chart details the top 10 domains within the report scope and the table details all domains available within the scope as well as the associated email addresses and items sent by the domain/sender.
Recipient Domains Report – A listing of the recipient (To, CC, BCC) domains as well as the associated email addresses per domain contained within the report scope. The chart details the top 10 domains within the report scope and the table details all domains available within the scope as well as the associated email addresses and items received by the domain/recipient.
If search terms are provided, an additional search keyword report will also be provided.
Keyword Term Hits – Contains all project search terms the files in the data set are responsive to. When using a Keyword Group or Search Term scoping setting users have the ability to isolate terms to only report back on the terms or terms within the Keyword Group selected as the report scope. The search counts included are based upon the scope of the report.
Nextpoint will assign custodians upon request. Please note that the custodian of a piece of data is not intrinsic to that data, rather it is an employee or other person or group with ownership, custody, or control over potentially relevant information. For example, an individual custodian’s electronically stored information (ESI) usually includes their mail file, whereas a group custodian’s ESI may include a shared network folder.
Due to this, custodians cannot be assigned without direction as to how the data was collected. Email archives collected and combined into a single PST file with multiple folders can be split among multiple custodians after processing has been completed. Assignment of more than 10 custodians in a single import may be billed as an additional hourly charge.
Master date of the document is the date used for filtering and date restrictions. Master date will be generated from the date sent of parent email for emails and their attachments and the last modified date for efiles.
When applying date restrictions, the kept documents are inclusive of the chosen date (master date as described above).
By default, Nextpoint will process all date ranges and file types received. It is possible, though not recommended, to filter by date or file type upon import. These filters would preclude those specified files from being entered into the database and full reprocessing would be necessary to go back and add them at a later time.
Nextpoint’s default setting is to suppress inline email attachment images from becoming separate stand alone documents. The inline attachments will be added to the Filtered columns in the Project and Import Snapshots. Please note, inline attachments are embedded in the body of an email. Examples of inline attachments are images within a signature line of an email, or any other item that is not properly attached to the email like a screenshot. If getting text for embedded screenshots through OCR is desired, this setting should not be selected.
For most matters, Nextpoint does not enable filtering of NIST documents. If it is found that the data is collected from client’s computers, this option can be turned on to removed non-user generated files.
Nextpoint dedupes email families and loose files globally across all custodians. To do so a MD5 hash value is generated, for emails, from Date Sent, Sender Name, Sender Email Address, Recipient Email Addresses, Display To, Display CC, Display BCC, Subject, Body, Attachment Names, Attachment Size and for loose files the bit stream of that file.
Upon import into the review platform, more custom deduplication is available based on message id of emails (while checking for differences in attachment count and BCC fields) at an additional hourly charge.
Imaging of documents imported after the EDA process are done by the Nextpoint Review application and generally follow the guideline of printing the document in its last saved state. If specific, by document type, imaging settings are needed, this can be done for an additional hourly charge.
Regardless of the timezone chosen at the time of processing, Nextpoint will image the date sent of the email with its original time and offset.
Upon processing each document will have its text indexed for searching.
If keywords searching is desired, syntax should be supplied in dtSearch syntax. Consultation on terms and syntax is available for an additional hourly charge.
Please note that the words below are considered stop words by default. This is to ensure proper functionality of the index. If you require one of these words to be included in a search, the default settings can be modified to accommodate the term.
Search Stop Words:
| a | came | him | much | still | very |
| about | can | himself | must | such | was |
| after | come | how | my | take | way |
| all | could | however | never | than | we |
| also | did | i | not | that | well |
| an | do | if | now | the | were |
| and | each | in | of | their | what |
| another | even | indeed | on | them | when |
| any | for | into | only | then | where |
| are | from | is | or | there | which |
| as | further | it | other | therefore | while |
| at | furthermore | its | our | these | who |
| be | get | just | out | they | will |
| been | got | like | over | this | with |
| before | has | made | said | those | would |
| being | have | me | see | thus | your |
| between | he | might | she | to | |
| both | her | more | should | too | |
| but | here | moreover | since | under | |
| by | hi | most | some | up |
Have Questions?
Contact your Account Director at hello@nextpoint.com or the Nextpoint Data Strategy team at support@nextpoint.com
Early Data Assessment Details
*This functionality is available for Standard and Advanced users only.
Users can log into any Nextpoint Discovery database to view the ANALYTICS tab.
ANALYTICS presents powerful, interactive visualization of your data in graphical form. Simply click on any of the graphs to view a complete list of the documents in that specific category. The overall progress of your review project is also quickly viewable in the interactive ‘doughnut chart’ near the bottom of the page.
To refine the data in your visualizations, just add terms to the SEARCH TO REFINE box on the upper right, and hit return on your keyboard. All data visualizations will redraw correspondingly.
Here is a breakdown of each section of ANALYTICS:
Your Data - Totals
Database totals for the following categories: All Documents, Emails, Attachments, and Email Threads. Click on any box to return all corresponding documents in that category.
Please note: These totals correspond to the master "document type" field in your imported data set.
Your Data - Documents by Date Range
Database totals based on customizable date range. Update the date range by using the tool at the top. Hover over each bar in the chart to view the date and document count. Click on any bar to return those specific results.
Choose “View documents without a date” link at right to view all corresponding documents (and add dates if warranted).
Your Data - Custom Data Widgets
Choose which data is most important to you in this customizable widget section. Add or delete widgets to suit your needs. Click on totals to return those specific results.
Choose “View non-imaged documents” to view all corresponding documents.
Your Review
View the up-to-date progress of your Review regarding relevancy and privilege status. Click on the doughnut chart or any of the totals in the legend to return those specific results.
Want to see more, or different database analytics?
Press on the field you would like to replace and then click the empty box to choose which metadata field you would like displayed instead.
Please note: only the first 100 results will display when you click "show all". If you would like a full list of the results, reach out to us and we can compile a csv with the full list.
Need detailed reviewer metrics?
Choose "Request detailed metrics" located under the Privilege Status chart, fill out the form, and a member of the Nextpoint team will be in touch.
Discovery Analytics
When importing your data into Nextpoint, OCR 1 is employed on your documents imported to extract any associated search text. After the import is complete, users have the flexibility to construct their own search syntaxes with the assistance of Boolean logic 2. You can find the search bar below in Nextpoint Discovery and Litigation (for both Documents and Transcripts).
If you are learning the nuances of building more complicated searches and/or just want some help building your search syntax, there is the Advanced Search functionality to assist. This can be found to the right of any search bar under ADVANCED.
Check out some Search Tips, Tricks, and FAQ's here.
Building an Advanced Search
To build and run an Advanced Search, start by selecting Advanced next to any search bar (as shown above). Here's a breakdown of some of the basics:
- Search syntax builds as you enter terms or make coding selections
- Search by Discovery, Privileged and/or Confidentiality statuses
- Use Boolean operators (AND, OR), look for exact phrases, and enter proximity searches
- More search tools are available via the "More Tools" dropdown, such as word exclusions and fuzzy searches
- Search within specific Bates or Date Ranges
- Search within specific metadata or (custom) coding fields
- Click Advanced Search when all terms are entered, and you will be taken to a results page
Return to Discovery Workflow
Notes:
- EDRM (edrm.net), Glossaries, http://www.edrm.net/glossary/ocr/
- EDRM (edrm.net), Glossaries, http://www.edrm.net/glossary/boolean-search/