DISCO searchQuickReference
DISCO searchQuickReference
Search basics
DISCO uses Westlaw- and Lexis-style search syntax with boolean search operators. Here are the basic search bar commands and
operators.
1 Word operators (and, or, and not) can be searched if placed in quotation marks, e.g., “contract and payment”
2 Fuzzy searching allows for the addition, deletion, or substitution of up to two letters in a word.
Search Quick Reference 2
Order of operations
1. Exact phrases: “ ”
2. Groupings: ( )
3. Proximity: /n, +n
5. [space], or
User-created information
Command Description Example
documentNote Document note field (edited manually documentNote(hot)
by DISCO users) Documents with the word hot in the document note field
field Custom metadata field added by field(important)
admin-level users that is used to Documents with important in any field
capture additional information
folder Folder created in DISCO by a user folder(“Hot Documents”)
Documents in the Hot Documents DISCO folder
folder(“Hot Documents/Experts”)
Documents in the Experts subfolder
folder(“Hot Documents/!”)
Documents in the Hot Documents folder and all subfolders
privilegeNote A text field that will appear on privi- privilegeNote(“Legal Advice”)
lege logs Documents using the phrase Legal Advice inside the privilege note
redactionReason Optional user-created text than can redactionReason(“Trade Secret”)
overlay redactions Documents with Trade Secret applied as a redaction reason
stage A set of documents created by users stage(“First Pass Review”)
for linear review Documents in the First Pass Review stage
stageBatched Documents in stages that have been stageBatched(“First Pass Review”)
pulled into batches Documents in the First Pass Review stage that have been placed
in batches (whether or not yet reviewed)
stageComplete Documents that have been marked stageComplete(“Privilege Review”)
“reviewed” in a stage Documents in the Privilege Review stage that have been marked
reviewed (i.e., complete)
tag Fields appended to documents by tag(responsive)
users Documents with the responsive tag
Search Quick Reference 4
3 Metadata is data about a document that is not part of the document’s content. Metadata can include things like the creation date, author, sending and receiving information, file name,
and file path.
Search Quick Reference 5
Document attributes
Command Description Example
billingSize Returns all documents with the billingSize(>1000000)
indicated size in bytes relative to the Documents with a billing size greater than 1,000,000 bytes
review database’s billing statement
childCount Returns all parent documents that childCount(2)
have the specified number of chil- Emails or other documents that have two children (such as attach-
dren4 ments or embedded files)
childCount(1 to 1000)
Emails or other documents that have between 1 and 1000 chil-
dren
comment Returns all documents with the comment(!)
indicted text left inline in the original All documents with comments in the original files
file
company Returns all documents created by the company(Enron)
same company Documents created by Enron
conversationCount Returns all emails belonging to conversationCount(3)
conversations5 that contain the Emails that contain three emails within the conversations
number or range of emails specified
conversationCount(3 to 15)
All emails that contain between three and fifteen emails within the
conversations
extension Returns all documents with the speci- extension(.doc)
fied file extension All documents with the .doc file extension
4 A child is typically either an attachment to an email or an embedded file in a document. A parent is the email containing the attachment or the document containing the file.
5 Conversations include the various responses, replies, and forwards of an email chain.
Search Quick Reference 6
6 Choices include revisions, hidden sheets, very hidden sheets, comments, and notes.
Search Quick Reference 7
Numeric searches
For the following, you can search for an exact document, a range of documents, or documents greater than or less than the indi-
cated value (for example, id(1234), id(1 to 1234), and id(<1234), respectively).
textLength
Tag fields
Tagging decisions can also be searched by dates applied and users applying them, using the following syntaxes.
Syntax Description
tag(by [email protected]) Documents tagged by [email protected]
tag(responsive & by [email protected]) Documents tagged responsive by [email protected]
tag(non-responsive % by [email protected]) Documents tagged non-responsive by someone other than
[email protected]
sample(10, tag(by [email protected])) Ten random documents tagged by [email protected]
tag(by [email protected] & on 10/16/2015) Documents tagged by [email protected] on 10/16/2015
tag(responsive & by [email protected] Documents tagged responsive by [email protected]
& before 10/16/2015) before 10/16/2015
removedTag(responsive) Documents from which the responsive tag was removed (by
anyone)
removedTag(by [email protected]) Documents from which any tags were removed by reviewer@
lawfirm.com
* % tag(!) Documents that have zero tags associated
Tag prediction
Tag prediction uses AI to predict a tag or tags that should be applied to a document. Tag prediction search syntax is displayed
below. Search syntax can accommodate multiple tags, e.g., prediction(“tag name1” & “tag name2”, >20).
Syntax Description
prediction(“tag name”, Likeliness value) prediction(Attorney-Client, Highly likely)
Documents that are highly likely to be tagged Attorney-Client
prediction(Attorney-Client, Likely)
Documents that are likely to be tagged Attorney-Client
prediction(Attorney-Client, Neutral)
Documents that are neither likely nor unlikely to be tagged
Attorney-Client
prediction(Attorney-Client, Unlikely)
Documents that are unlikely to be tagged Attorney-Client
prediction(Attorney-Client, Highly unlikely)
Documents that are highly unlikely to be tagged Attorney-Client
prediction(“tag name”, score range) prediction(Attorney-Client, -20 to 20)
Documents that have a likelihood score in the range of -20 to
20 to be tagged Attorney-Client
prediction(Attorney-Client, >20)
Documents that have a likelihood score over 20 to be tagged
Attorney-Client
prediction(“tag name”, exact score) prediction(Attorney-Client, 20)
Documents that have a likelihood score of 20 to be tagged
Attorney-Client
Date fields
Dates can be searched by exact date, a range of dates, and before or after a date (for example, createDate(5/4/09), create-
Date(5/4/09 to 5/10/09), and createDate(before 5/10/09), respectively).
Dates can be formatted as date certain (12/10/2015), month and year (9/2016), or year (2012).
7 For all documents in an email conversation, the conversation date is the send date of the first email in the conversation. Emails have a sent date, but other document types do not.
8 date( ) refers to the sent date for emails, or the last modified date for other files.
9 For all documents in a family, the family date is the send date of the head of the family.
Yes/no fields
Syntax Description
has”Contract Date”(yes|no) yes if document has a contract date
hasDetectedSlipsheet(yes|no) yes if a slipsheet was produced in conjunction with a native
file for load file ingest
hasDocumentNote(yes|no) yes if document has a note
hasFields(yes|no) yes if document has contents in any custom fields
hasHiddenType(yes|no) yes if document has a hidden file type
hasImage(yes|no) yes if document was processed as an image
hasLanguage(yes|no) yes if document has an identified language
hasNative(yes|no) yes if document was processed with a native file
hasOCR(yes|no) yes if the extracted text was derived via OCR
hasPrivilege(yes|no) yes if document has at least one privilege tag
hasRedaction(yes|no|onDocument|onMetadata) yes if document is marked for redaction in DISCO
hasRedactionReason(yes|no|onDocument|onMetadata) yes if document has a reason for redaction
hasRedactionWithoutReason(yes|no|onDocument|onMetadata) yes if document is redacted without a stated reason
hasSearchText(yes|no) yes if document contains searchable text
hasWorkProduct(yes|no) yes if document has work product applied
hasWrongExtension(yes|no) yes if document was processed with a different extension
than the one indicated
isDetectedEmail(yes|no) yes if document was identified as an email
isInclusive(yes|no) yes if document is an email that is duplicated within an
inclusive email
isProcessedAsNative(yes|no) yes if document was processed unsuccessfully
unfoldered(yes|no) yes if document is not in a DISCO folder
Search Quick Reference 12
Redactions
Command Description Example
hasRedaction Searches for documents that have hasRedaction(onDocument) % hasRedaction(onMetadata)
redactions, do not have redactions, Documents with a redaction in the document but not in the
or have redactions in a specific metadata
location. Value options are yes, no,
hasRedaction(to)
onDocument, onMetadata, and any
Emails with redaction in the to metadata field
metadata fields.
hasRedactionReason Searches for documents that have hasRedactionReason(author)
redaction reasons, do not have Documents with a redaction reason for the author metadata field
redaction reasons, or have redaction
hasRedactionReason(yes)
reasons in a specific location
Documents that have a redaction reason
hasRedactionWith- Searches for documents that have hasRedactionWithoutReason(yes)
outReason a redaction, but no corresponding Documents with a redaction that does not have a corresponding
redaction reason. Value options redaction reason
are yes, no, onDocument, onMeta-
hasRedactionWithoutReason(onMetadata)
data, and any metadata field.
Documents with metadata redactions that do not have a corre-
sponding redaction reason
Custom fields
DISCO also allows administrators to define their own fields that can then be used in DISCO searches. Fields also support wildcards
and true/false syntax.
Example Description
deposition(important) Documents with the word important in the Deposition field
“My thoughts”(“very important”) Documents with very important in the My Thoughts field
or My_thoughts(“very important”)
hasDeposition(!) Documents with any contents in the Deposition field
or hasDeposition(true)
has”PSL Notes”(!) Documents with any contents in the PSL Notes field
or has”psl notes”(true)