Nextpoint Default and Protected Fields

Follow

The following fields exist in Nextpoint without needing to explicitly add them to your database. Some are default fields to which you can map data during an import (Exhibit A), and others are protected fields to which you can not push data. While it is not necessary to map data to our default fields, it is best practice because it can reduce the number of fields you may need to search in your database

For instance, if you map "From" data in your load file to a custom "From" field instead of the default field "Email_Author," then to search your clients emails and those produced by Opposing Counsel for those authored by "John Smith," you would need to search:

email_author:"John Smith" OR from:"John Smith" 

If you map the "From" field to "Email_Author," you only need to search:

email_author:"John Smith"

to return hits in both sets of data. 

Warning

One field that is very important to most load file imports is the field "begattach." This field allows Nextpoint users to link parent emails with their attachments in produced data imports. In this field the bates_start value of the parent email appears in the attachment's "begattach" field. The "begattach" field must be an exact match to the character string "begattach" and must be created in a database before family linking is possible.

 

Default FieldsProtected Fields

Default Fields & Document Attributes

For any of the below-listed fields, you do not need to set up a new Field under SETTINGS > Coding.  Instead, if you have a header value in Row 1 of your load file, make sure that the load file value matches the below default fields exactly.

Values can be imported by load file headers to the provided values. App Name indicates what your load file header should read.  Visible vs. Hidden indicates if a field can be seen under SETTINGS    Coding    Fields (Visible), or if it isn't seen in the field list but can accept your load file information (Hidden).

App NameVisible vs. Hidden
AuthorHidden
Bates_StartHidden
Bates_EndHidden
Bates_Range_StartHidden
Bates_Range_EndHidden
BegattachVisible
EndattachVisible
BCCVisible
CCVisible
Created_Date_TimeVisible
CustodianHidden
CustodiansHidden
DateHidden
Document_AuthorVisible
Document_Last_AuthorVisible
Document_SubjectVisible
Document_TitleVisible
Document_TypeHidden
Document_DateHidden
Email_AuthorVisible
Email_ReceivedVisible
Email_SentVisible
Email_SubjectVisible
Email_Thread_IndexHidden
EncryptedVisible
File_NameVisible
File_PathVisible
Image_FileHidden
Last_Print_DateVisible
Mailbox_FileVisible
Mailbox_PathVisible
Modified_Date_TimeVisible
Native_FileHidden
RecipientsVisible
Root_FolderVisible
ShortcutHidden
TagsHidden
Text_FileHidden
TitleHidden

Important Field Notes:

  • Custodian/Custodians are visible under Settings > Import > Custodians
  • Have existing/historical Tags you want to migrate to Nextpoint's Additional Tags field?  Your column header should read Tags and the values should be semicolon delimited (e.g. Bob Randolph; hard copy document; Production 1; 10/22/2019).

 

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Articles in this section

See more