Read this first: Produce documents from DISCO
The production document format options include:
- PDF (default)
- B&W TIFF & Color JPEG
- B&W TIFF Only
- Natives with Slipsheet (Unless redacted)
By default, DISCO will produce documents in color, PDF format. TIFF images will always be in black and white. If a B&W TIFF & Color JPEG format is chosen, DISCO will scan each page for any color content, and create a JPEG image if any color is found.
Produce as native with slipsheet (unless redacted)
Here a user can specify which imageable documents should be produced as natives (with slipsheets) instead of images. CAD and Excel files, while are usually imageable in DISCO, are produced as natives by default, though these options can be changed. Other imageable file types can also be produced as natives (e.g., if you want to produce PowerPoint documents as natives instead of images). Again, natives will never be produced of documents that are redacted (unless the “Omit redactions” option is selected). By default, DISCO will produce the following five file types in their native format:
To override this default when creating a production, select Produce as Natives with Slipsheet Unless Redacted box from the document format select bar. Excel spreadsheets that were imaged in DISCO will now be produced as images for this production.
Load file format
Load file format options include:
- All standard (DAT, DII, XML)
- Custom DAT...
Click here to read more on how to customize your load file.
While DISCO performs strategic document deduplication upon ingestion (click here to read about family level deduplication used in DISCO ingest), the user has the option to split the duplicate documents out again on production (into separately Bates stamped images/files) in several ways.
These options run on a spectrum from getting the most number of documents in the production (No deduplication - meaning produce exactly in the way and number the duplicate documents were ingested into DISCO) to the fewest (One copy for the entire production - meaning produce only one copy of each set of duplicated documents, no matter how many duplicates there were).
The default option - One copy per custodian and per parent - is the most common option, guaranteeing that at least one copy of a duplicated document will be produced for each custodian, and one copy of each email attachment will be produced for each email that duplicate was attached to.
- No deduplication
- One copy per custodian and per parent (default)
- One copy per parent across custodians
- One copy per custodian
- One copy for the entire production
Here the user can choose a sorting order for the documents (and, hence, the Bates stamping) in the production. The “then” in the options means that the documents will be initially sorted by the first criteria, then the second criteria.
For example, the default option, “Custodian then Family Date”, means that the documents will first be sorted by their custodian, then by family date within that custodian group. The family date of a document is the sent date (or last modified date) of its parent, or just the sent date/last modified date of the document if it has no parent. Family date ordering helps ensure that attachments directly follow their parent emails in the production, where possible.
“Path” is simply the original file path of the document (i.e., the path of the file on the disk or email container the document came from).
Reference ID is a special custom field in DISCO that the user can set via initial loadfile or later mass update of the documents. This is rarely used, but useful when the user already has applied a control ID to the documents before they come to DISCO, and wants to preserve that ordering for the production.
- Custodian then Family Date (default)
- Custodian then Path
- Family Date then Path
- Path Only
- Reference ID
Starting Volume Label
By default, a production creates a separate volume for every 500 TIFF files per folder, 2,000 documents, or 40,000 pages, whichever is reached first (this is to make the production compatible with older document review software, and to comply with certain government standards). With this option, you can specify the name of the first volume. DISCO will automatically increment the volume label for each subsequent volume (e.g., if you supply “VOL001” as the starting volume label, the second volume will be “VOL002”, and so on). Each volume will be a separate, compartmentalized unit, with its own set of document folders and load files.
Starting Volume Break
As indicated above, the default behavior for volume creation is a separate volume for every 5,000 pages (or 40,000 documents). The user can also specify no volume breaks (i.e., the entire production will be in one single volume), or to break the production up into one volume per custodian included in the production.
- By Size (default)
- Do not apply Bates stamp to images
Do not print Bates stamps to the document images (and do not bring these Bates numbers back into DISCO for searching/sorting). A Bates prefix and starting number must still be specified for naming the actual files in the production.
- Also include natives for all images unless redacted
Include all natives for documents, regardless of production format (unless the document is redacted, of course).
- Omit redactions
Render the images without their redactions. Obviously a dangerous option as it will reveal sensitive information. Usually only used for internal or archival productions.
- Store OCR text file in same folder as images
A rarely used option to make the production more compatible with early versions of Summation.