To read more about uploading documents on Everlaw, feel free to refer to the articles in our Uploads section.
Table of Contents
You can use the Bates or uploaded search terms to easily pull up documents from particular uploads. You can also find uploaded documents from the Document Sets column on the homepage.
Document Sets column
The Document Sets column allows you to access lists of documents that were included in a particular native or processed upload by clicking on the card that corresponds to that upload. Native upload cards have a dark orange band and say "Native" on the card, and processed upload cards have a light orange band and say "Processed" on the card.
Uploads page
You can locate upload history cards containing information about individual native or processed uploads by clicking on the Native Data or Processed Data tab on the Uploads page. Each card contains information on the date, size, and status of an upload; you can also access individual sets of uploaded documents by clicking on the three-dot menu in the top right of each card.
Native upload cards contain additional information on upload errors. For more information about managing native uploads through the upload cards, please see the "Managing native uploads" section of the native data uploading article.
Searching by Bates number
Native documents uploaded by Everlaw will be given a control number. You can find these documents by selecting the Bates search term and choosing “#” for the Bates prefix. If you know the specific number or number range you want to search across, you can input that into the second parameter.
You can search for processed documents in the same manner, though you would select one of the Bates prefixes instead of the "#."
Searching by the Uploaded search term
To search for documents by their processing status, use the Uploaded search term. You can select the name of the dataset that you wish you search for, or select “Any Dataset.”
Using the second parameter, you can find documents by their current processing state. There are three states in the uploads process: examine, text, PDF. A document can fail on any one of the three stages.
In the third parameter, you can select any additional flags (or properties) that you want to find documents by. Here is a list of the parameters, and their basic definitions:
NOTE: For documents uploaded as processed data, only certain flags are applied by default if a native is available, these are noted below with a *.
- Container Document*: The file was originally a top-level folder, and not an actual document
- Empty Text: Document does not have a text file
- Encrypted*: The document is encrypted
- Has OCR: The document has been OCRed
- Has Placeholder PDF: The document has a placeholder image
- NIST Duplicate*: The document is on the NIST National Software Reference Library list of known, traceable software files
- Opened with Password/Key: The document was in a password protected folder or was a password protected file or S/MIME encrypted email
- Unknown Document Type*: The file is not a known document type
Using these flags, you can find documents that have certain properties, or that might need troubleshooting.
Finally, you can choose to include documents that were used to deduplicate documents during a native upload by using the “Include deduplicated docs” option. If this checkbox is selected, the search results will include all documents uploaded as part of this upload, as well any documents in the project that were used to deduplicate a document in the selected upload’s original document set. This option is unselected by default.
This functionality is illustrated in the example below:
- Document 1 and Document 2 are uploaded as a part of Upload A.
- Document 1, Document 2, and Document 3 are uploaded as a part of Upload B with Global Deduplication turned on. As a result, Document 1 and Document 2 are deduplicated.
- Searching for Uploaded: Upload B will return only Document 3, as Documents 1 and 2 were deduplicated.
- Searching for Uploaded: Upload B including deduplicated docs will return Document 1, Document 2, and Document 3.
0 Comments