DISCO supports both document- and instance-level overlays. For more information about review documents vs. instances, please see Document IDs and Deduplication within DISCO. With mixed-mode overlays, a document overlay can now also update some fields that were previously only editable via an instance overlay. Likewise, an instance overlay can now also update some document-only fields that were previously only editable via a document overlay.
The table below describes the overlayable fields and what happens when those fields are overlaid with a document or instance overlay.
The overlay-file field used to identify the documents for overlay must consist entirely of either document IDs, instance IDs, or Bates numbers, and cannot contain a combination of these identifiers.
The following fields must use the Instance ID as the DISCO identifier to be updated:
- Bates Numbers: BeginBates, EndBates
- Dates: LastAccessedDate, LastAccessedTime, LastModifiedDate, LastModifiedTime, LastPrintedDate, LastPrintedTime, CreateDate, CreateTime, ReceivedDate, ReceivedTime
- Dedupe fields: Custodian, FileName, OriginalFilepath
- Email Metadata: EmailInReplyTo, EmailMessageID, EmailPrConversationIndex, EmailRead, EmailReferences, EmailTransportHeaders
DISCO Fields |
|
|
When using document IDs in the overlay file: | When using instance IDs in the overlay file: | ||
Field |
Description |
Mapping Requirements |
When there are multiple instances, update all of them? |
If the document only has a single instance, update the single instance? | When there are multiple instances, update all instances or only the specified instance? |
Update the single specified instance? |
AttachmentBatesRange |
The beginning and last Bates number of the attachment range |
Both values in Bates range must have same length. |
NO |
YES | Update the specified instance only |
YES |
Author |
The file’s author |
None |
YES |
YES | Update all instances |
YES |
Bcc |
The email’s BCC field |
None |
YES |
YES | Update all instances |
YES |
BeginAttachmentBates |
The beginning Bates number of the attachment range |
BeginAttachmentBates should be mapped to BegAttach. There is no EndAttach field to map. |
NO, Family overlay supported only in single instance data |
YES | NO, Family overlay supported only in single instance data |
YES |
BeginBates |
The beginning Bates number |
BeginBates and EndBates must be mapped together |
NO, Fail validation |
YES | Update the specified instance only |
YES |
Cc |
The email’s CC field |
None |
YES |
YES | Update all instances |
YES |
ChatChannelName |
The name of the channel a chat message was sent in |
None. Can be multi-valued. |
|
|
||
ChatMessageType |
The message type of a chat, DISCO values include "Public channel", "Private channel", "Direct message", and "Group direct message" |
Requires matching a DISCO value from previous column. |
|
|
||
ChatRecipient |
Recipients of a chat message |
None. Can be multi-valued. |
|
|
||
ChatSendDate |
The date the chat was sent |
None. |
|
|
||
ChatSender |
Sender of a chat message |
None. Can be multi-valued. |
|
|
||
ChatSendTime |
The time the chat was sent |
None. |
|
|
||
Company |
The company associated with the file |
None |
YES |
YES | Update the specified instance only |
YES |
CreateDate |
The date the file/email was created |
If the value contains both date and time, then the date component is stored in this field and the time component is stored in the time field |
NO, Fail validation |
YES | Update the specified instance only |
YES |
CreateTime |
The time the file/email was created |
If mapping CreateTime, CreateDate must also be mapped |
NO, Fail validation |
YES | Update the specified instance only |
YES |
Custodian |
The document’s custodian |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
Custom metadata* |
Non-DISCO fields derived from the document |
None |
YES |
YES | Update the specified instance only |
YES |
EmailInReplyTo |
The address the email reply will be sent to if different from the From address |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
EmailMessageId |
Unique email message identifier |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
EmailPrConversationIndex |
Email conversation index contained in the header information |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
EmailRead |
Email read receipt request |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
EmailReferences |
The unique message identifier that was replied to |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
EmailTransportHeaders |
Email metadata header |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
EndBates |
The ending Bates number |
BeginBates and EndBates must be mapped together |
NO, Fail validation |
YES | Update the specified instance only |
YES |
FileName |
The file’s name as detected from the file system |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
From |
The email’s From field |
None |
YES |
YES | Update all instances |
YES |
ImagePath |
The file path to the document image storage location |
The image file path must be relative to the overlay file or specify another location. The image files must be kept in the same folder. |
YES |
YES | Update all instances |
YES |
LastAccessedDate |
The date the document was last accessed |
If the value contains both date and time, then the date component is stored in this field and the time component is stored in the time field |
NO, Fail validation |
YES | Update the specified instance only |
YES |
LastAccessedTime |
The time the document was last accessed |
If mapping LastModifiedTime, LastModifiedDate must also be mapped |
NO, Fail validation |
YES | Update the specified instance only |
YES |
LastModifiedDate |
The date the file was last modified |
If the value contains both date and time, then the date component is stored in this field and the time component is stored in the time field |
NO, Fail validation |
YES | Update the specified instance only |
YES |
LastModifiedTime |
The time the file was last modified |
If mapping LastModifiedTime, LastModifiedDate must also be mapped |
NO, Fail validation
|
YES | Update the specified instance only |
YES |
LastPrintedDate |
The date the document was last printed |
If the value contains both date and time, then the date component is stored in this field and the time component is stored in the time field |
NO, Fail validation |
YES | Update the specified instance only |
YES |
LastPrintedTime |
The time the document was last printed |
If mapping LastPrintedTime, LastPrintedDate must also be mapped |
NO, Fail validation |
YES | Update the specified instance only |
YES |
LoadFileTextPath |
The path to the document text storage location |
The text file path must be relative to the overlay file or specify another location. The text files must be kept in the same folder. |
YES |
YES | Update all instances |
YES |
NativePath |
The path to the native version of the document's storage location |
The native file path must be relative to the overlay file or specify another location. The native files must be kept in the same folder. |
YES |
YES | Update all instances |
YES |
OriginalFilePath |
The original file path associated with the file |
None |
NO, Fail validation |
YES | Update the specified instance only |
YES |
ParentId |
An alternative to the BegAttach field to indicate an email/attachment relationship |
ParentID cannot be mapped if BeginAttachmentBates or EndAttachmentBates is mapped |
NO, Family overlay supported only in single instance data |
YES | NO, Family overlay supported only in single instance data |
YES |
PrivilegeNote |
The reason a document is privileged |
None |
YES |
YES | Update all instances |
YES |
ProcessingException |
A custom field identifying any relevant exceptions encountered by DISCO Data Operations team members when remediating documents |
None |
YES |
YES | Update all instances |
YES |
ProcessingExceptionDetails |
A custom field describing any relevant exceptions encountered by DISCO Data Operations team members when remediating documents |
None |
YES |
YES | Update all instances |
YES |
ReceivedDate |
The date the email was received |
If the value contains both date and time, then the date component is stored in this field and the time component is stored in the time field |
NO, Fail validation |
YES | Update the specified instance only |
YES |
ReceivedTime |
The time the email was received |
If mapping ReceivedTime, ReceivedDate must also be mapped |
NO, Fail validation |
YES | Update the specified instance only |
YES |
ReferenceId |
A general purpose field that may include an external document identifier |
None |
YES |
YES | Update the specified instance only |
YES |
SendDate |
The date the email was sent |
If the value contains both date and time, then the date component is stored in this field and the time component is stored in the time field |
YES |
YES | Update all instances |
YES |
SendTime |
The time the email was sent |
If mapping SentTime, SentDate must also be mapped |
YES |
YES | Update all instances |
YES |
Subject |
The email’s subject |
None |
YES |
YES | Update all instances |
YES |
Tags* |
User work product |
None |
YES |
YES | Update all instances |
YES |
Title |
The document’s title |
None |
YES |
YES | Update the specified instance only |
YES |
To |
The email’s To field |
None |
YES |
YES | Update all instances |
YES |
User fields* |
User fields generated by the user during review |
None |
YES |
YES | Update all instances |
YES |
* Not a standard DISCO field. Name of field will be defined by user.