With the LAW Direct Export, CloudNine™ Explore can export files directly into new or existing cases in CloudNine™ LAW.
The LAW Direct Export process passes files that remain after filtering or tagging directly to new or existing cases in CloudNine™ LAW without having to import the files using ED Loader. The export process involves two steps. First, you generate an Export Set, which contains saved export settings and the list of items to be exported. Second, you send the Export Set directly to a new or existing CloudNine™ LAW case.
To export to an existing CloudNine™ LAW case, the case must be:
•SQL Server-based
•Active
•Enabled for electronic discovery
A LAW Direct Export set can only be used for one CloudNine™ LAW case. You can send a LAW Direct Export set to the same CloudNine™ LAW case multiple times, such as for rolling productions.
If you want to export files from one CloudNine™ Explore case to multiple CloudNine™ LAW cases using the LAW Direct Export, you will need to create a separate export set for each CloudNine™ LAW case. You can also export files from multiple CloudNine™ Explore cases to the same CloudNine™ LAW case using the LAW Direct Export, but it is not recommended as doing so may result in duplicate DocID field values. For more information on configuring options for CloudNine™ LAW cases, see the CloudNine™ LAW Answer Center.
Additional Information about LAW Direct Export
When files are imported into CloudNine™ LAW using LAW Direct Export, some things are handled differently during the export, and files are imported without using ED Loader.
•Indexing - Files imported into a new or existing CloudNine™ LAW case using the LAW Direct Export are not automatically indexed after the export process. During the export, the _FTIndex field in CloudNine™ LAW is automatically set to 1 (the record has text that is ready for indexing) for all documents that contain text. You will need to manually index the case if you want to run full-text searches on the exported files in CloudNine™ LAW.
•OCR text - With the LAW Direct Export, you do not need to perform OCR on files exported to CloudNine™ LAW if OCR was already performed on the files in CloudNine™ Explore. If OCR was performed in CloudNine™ Explore, the OCR text is included in the export to CloudNine™ LAW and the OCRStatus field is populated with the correct value (Y, N, C) for each file. The OCR .txt files are exported to the following directory:
▪…Cases\[CloudNine™ Explore case name]\$Text\$OCR\
•Extracted text - If the export includes files with extracted text, the associated .txt file associated is exported to the $EDD folder for the CloudNine™ LAW case, and the TextXStatus field is populated with the correct value (C, N, or E) for each file.
•NativeFile field - When native files are exported to CloudNine™ LAW using the LAW Direct Export, the NativeFile field in CloudNine™ LAW is populated with the native file path for each imported native file. By default, the native files are exported as follows:
oWhen exporting to an existing CloudNine™ LAW case not created by the LAW Direct Export: ...\Cases\[CloudNine™ LAW case name]\$EDD\$NativeFiles\
oWhen exporting to a CloudNine™ LAW case created by the LAW Direct Export: ...\Cases\[CloudNine™ Explore case name]\$EDD\$NativeFiles\
oNative files in the export are named using the following format: [LAW ID].ntv.[native file extension]. For example: 02.ntv.xls.
•EDSession field - When files are exported to CloudNine™ LAW using the LAW Direct Export, the EDSession field in CloudNine™ LAW is populated with the export name, the CloudNine™ Explore case name, and date and time of the export session using the following format: "[export name] on [CloudNine™ Explore case name] (YYYY/MM/DD HH:MM:SS)". For each file in the export, the export session time is based on the local timezone of the machine performing the export. For example: "LDE Export - 001 on CloudNine™ Explore Case Name (2015/09/30 2:30:02 PM)"
|
The EDSession name format for LAW Direct Exports is: {ExportName} on {CaseName} {ExportRunCount} For example, "LDE Export on Explore Case Name (1)" |
•Metadata - During the LAW Direct Export, the metadata from the exported CloudNine™ Explore files populates for the corresponding fields in CloudNine™ LAW. For example, the Email_Subject field in CloudNine™ LAW is populated with the email subject identified in CloudNine™ Explore. When files are exported to CloudNine™ LAW using the LAW Direct Export, the following CloudNine™ LAW fields are not populated during the export:
o_DupID o_DupMethod o_PS_ARCX o_PS_ATTX o_PS_DIGESTX o_PS_EMBEDX o_PS_MDX o_PS_OLEX oAttRange oBatchStation oBegAttach oBegDoc# oColorID (Run Update Page Data in CloudNine™ LAW to set this value in LAW.) oDateAccessed oDupCustNames oDupCustPaths oDupParentName |
oDupParentPath oDupStatus oEP* (Extended properties or extended metadata fields) oEndAttach oEndDoc# oFileAccuracy oHasRedaction oOcrAccuracy oOrigExt oPlaceholder_Name oSourceFile oSuspectExt oSuspectOLE oTemplate oTimeAccessed oUserId |
•Tags - The CloudNine™ Explore tags and tag assignments for the included files are exported. These tags can be identified by the suffix "_EDA" on the field name.
•File type management database - When using LAW Direct Export, the CloudNine™ LAW file type management database is used to populate the SourceApp field in CloudNine™ LAW, which assigns a source application to native files based on the file type and source application mappings from the file type management database. The source applications assigned to native files are used for e-printing and TIFF/PDF conversions in CloudNine™ LAW. The LAW Configuration Utility>Environment>File Type DB indicates where the file type management database is stored for a case, which can be configured through the LAW Configuration Utility. If CloudNine™ LAW has not been opened before, and you perform a LAW Direct Export, a message will open indicating that CloudNine™ Explore cannot find the file type management database. You have the option of canceling the export or continuing the export. If you continue the export, the SourceApp field will not be populated for the exported documents, and you will not be able to e-print or convert those files imported using the LAW Direct Export to TIFF of PDF files.
•Location of CloudNine™ LAW files - If any of the CloudNine™ LAW case or database files are stored in a location considered protected by Microsoft Windows, the LAW Direct Export may not function as expected because CloudNine™ Explore may not be able to find the case or database (caselist.mdb or EDLoader.ftm.mdb) files or folders. The C:\Program Files, C:\Program Files (x86), C:\Program Data, and My Documents directories are treated as protected locations and should not be used for storing case files.
•Time zones - CloudNine™ LAW and CloudNine™ Explore use different methods to determine the time zone list, so there may be differences between dates and times if the time zone lists used by each product do not match. CloudNine™ LAW uses a lookup table in a case’s SQL Server database to determine the list of time zones, while CloudNine™ Explore uses the list of time zones from the user’s operating system.
•Export errors - If there are errors during the LAW Direct Export, the errors are written to CloudNine™ Explore process logs and can be viewed by clicking the Show link next to the Errors field on the Export tab.