Configuring Format-Specific Settings

<< Click to Display Table of Contents >>

Navigation:  Using CloudNine LAW > Exporting Documents > Export Utility: Formats / Documents >

Configuring Format-Specific Settings

This page is currently under construction.

RightArrowFor now, refer to the Format-Specific Settings topic in the Answer Center.

 

 

RightArrow Configurable Formats:

ExportCaseLogistixSettingsWindowIcon CaseLogistix Settings

This window is used to configure CaseLogistix load file (XML) export settings.

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

Include document/OCR text as a field in load file - When available, the extracted/OCR text from each document will be included in the load file.

oField name - This input box specifies a name for the field where this text is stored within the load file.

Return to:

ExportCaseMapSettingsWindowIcon CaseMap Settings

This window is used to configure CaseMap load file (CSV) export settings.

Data Delimiters - The following drop-downs determine what characters are used to delimit (contain/separate) document data within the exported load file:

oField - This drop-down determines the delimiter used for Metadata Field data.

Other - When selecting <other> from the Field drop-down, use this input box to specify a new delimiter to use.

oText - This drop-down determines the delimiter used for extracted/OCR text data.

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

Include field names as first record - The name of each selected Metadata Field (Export Utility: Fields) is included in the first row (record) of the exported load file.

Return to:

ExportConcordanceSettingsWindowIcon Concordance Settings

 

Data Delimiters - The following drop-downs determine what characters are used to delimit (contain/separate) document data within the exported load file:

oComma -

oQuote -

oNewline -

oRestore Defaults - This button will restore all delimiters to their default character selections.

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

Allow Unicode data in load file -

Create Opticon load file only -

Enable support for Concordance Native Viewer -

Include field names as first record -

Include document/OCR text as a field in load file - When available, the extracted/OCR text from each document will be included in the load file.

oField name - This input box specifies a name for the field where this text is stored within the load file.

Link to images and native files in their current location -

Return to:

ExportConcordanceDesktopSettingsWindowIcon Concordance Desktop Settings

 

Use specific database (*.dcb) override path -

oDatabase path -

Browse... -

oField Settings... -

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

If Record Match is Found -

oSkip Record -

oUpdate Existing Record -

oAppend All Records -

Automatically load Opticon/Native base files -

Concatenate DCB's across separate partitions -

Create Concodrance 10.0 database (supports Unicode) -

Enable support for Concordance Native Viewer -

Include document/OCR text as a field in database file - When available, the extracted/OCR text from each document will be included in the database (DCB) file.

oField name - This input box specifies a name for the field where this text is stored within the database file.

Link to images and native files in their current location -

Truncate text values that exceed their field size -

Return to:

ExportConcordanceDirectSettingsWindowIcon Concordance Direct Settings

 

Use specific database (*.dcb) override path -

oDatabase path -

Browse... -

oSecurity... -

oField Settings... -

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

If Record Match is Found -

oSkip Record -

oUpdate Existing Record -

oAppend All Records -

Automatically load Opticon/Native base files -

Concatenate DCB's across separate partitions -

Create Concodrance 10.0 database (supports Unicode) -

Enable support for Concordance Native Viewer -

Include document/OCR text as a field in database file - When available, the extracted/OCR text from each document will be included in the database (DCB) file.

oField name - This input box specifies a name for the field where this text is stored within the database file.

Link to images and native files in their current location -

Truncate text values that exceed their field size -

Return to:

ExportDelimitedTextSettingsWindowIcon Delimited Text Settings

 

Data Delimiters - The following drop-downs determine what characters are used to delimit (contain/separate) document data within the exported load file:

oField - This drop-down determines the delimiter used for Metadata Field data.

oText - This drop-down determines the delimiter used for extracted/OCR text data.

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

Allow Unicode data (UCS-2 format) -

Return to:

ExportDocuMatrixSettingsWindowIcon DocuMatrix Settings

 

Case Name -

Database Name -

Include attachments by parent -

Include page offset data with OCR -

Create XML for fixing existing documents -

Renumber documents sequentially -

oStarting # -

Return to:

ExportEDRM1SettingsWindowIcon EDRM 1.0 Settings

 

Batch Name -

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

Include document/OCR text as content in load file - When available, the extracted/OCR text from each document will be included in the load file.

Link to images and native files in their current location -

Return to:

ExportEDRM2SettingsWindowIcon EDRM 2.0 Settings

 

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

Include document/OCR text as content in load file - When available, the extracted/OCR text from each document will be included in the load file.

Link to images and native files in their current location -

Return to:

ExportiCONECTSettingsWindowIcon iCONECT Settings

 

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

Date Format -

Include document/OCR text as a field in load file - When available, the extracted/OCR text from each document will be included in the load file.

oField name - This input box specifies a name for the field where this text is stored within the load file.

Return to:

ExportTrialDirectorSettingsWindowIcon TrialDirector Settings

Use this window to configure both inData's TrialDirector and Summation Blaze load file export settings.

Document ID -

Object ID -

Description (Optional) -

Return to:

ExportInmagicSettingsWindowIcon Inmagic Settings

This window is used to configure Inmagic's DB/TextWorks load file (ADD) export settings.

Path Notation - The following options determine how image file paths are written to the exported load file:

oHard Path - The full file path will be written, so that the root directory is the same regardless of load file location.

oRelative Path - Relative file paths will be written, so that the location of the load file itself becomes the root directory.

oUNC Path - UNC notation is used for the file paths, so that a mapped network drive may be used as the root directory.

Return to:

ExportIntrospectSettingsWindowIcon Introspect Settings

 

General -

oBatch Name -

oIndex ID -

oFolder ID -

oInclude all Bates numbers -

oLink to images and files in current location -

oUse IDX version 5 format -

Field IDs... -

Priority -

oLow -

oMedium -

oHigh -

Flags -

oIndex flag -

oRender flag -

oHold flag -

Return to:

ExportPDFSettingsWindowIcon PDF Settings

 

Create bookmarks for grouped documents -

oBookmark Caption -

Parent -

Attachments -

Populate PDF metadata -

oTitle -

oDubject -

oAuthor -

oKeywords -

Return to:

ExportRingtailSettingsWindowIcon Ringtail Settings

 

Allow long folder names (over 20 chars) -

Include document/OCR text as a field in load file - When available, the extracted/OCR text from each document will be included in the load file.

oField name - This input box specifies a name for the field where this text is stored within the load file.

Insert special page markers in OCR text -

oReplace existing page markers -

Include reference to native file in Pages table -

Multi-entry fields... -

Return to:

ExportSummationSettingsWindowIcon Summation Settings

 

Allow advanced (iBlaze) dii features -

eDii Tokens... -

oWrite all fields to dii file -

oInclude document/OCR text directly in dii file - When available, the extracted/OCR text from each document will be included in the dii file.

oInclude PST tokens directly in dii file -

oInclude @EDOC token for e-mail messages -

Always write index fields to separate file -

Include field names as first record of delimited text file -

Data Delimiters -

oField Separator -

oQuote Character -

o<Return> Value in Data -

oRestore Defaults -

Dii Path Notation -

oCD Volume (@V Vol:) -

oHard Path -

oImage Directory (@1) -