Native Export

<< Click to Display Table of Contents >>

Navigation:  CloudNine Explore > Using CloudNine Explore > Case Dashboard > Export >

Native Export

There are two types of native exports in CloudNine™ Explore:

Native File Export - Generates a DAT load file, along with native files and text files, for importing into CloudNine™ Concordance®, kCura® Relativity®, or other applications that support them. The native file export can also generate an EDRM XML version 1.0 load file, along with native files and text files for importing into products that support EDRM XML version 1.0. The files generated by the native file export are saved to an export output directory.

Native Subset Export - Same as Native File Export, but created for existing native exports in CloudNine™ Explore. Before a native subset export set can be created and exported, the parent native export set must exist in the case. Native subset exports can be used to speed up the file review for a case by only exporting the native files for specific CloudNine™ Explore IDs or specific export numbers.

As an example, a native export set can be created and exported, but only the file metadata and text are exported, not the native files. Then the DAT load file or EDRM XML 1.0 load file generated by the native export can be imported into another product to tag only the relevant files for the case. After the tagging is completed, the CloudNine™ Explore IDs or export numbers for the tagged files are exported to a line-delimited text file, which is then imported into CloudNine™ Explore when creating a native subset Export Set. When the native subset export is created, CloudNine™ Explore populates the native subset export with the files from the parent native Export Set that matches the CloudNine™ Explore IDs or numbers in the line-delimited text file. Once the native subset export set is created and populated with the tagged files, you can export the native files for the tagged files.

The export process passes any files remaining after filtering or tagging to the native file export directory. The export process involves two steps. First, you generate an Export Set, which saves the export settings along with the list of items to be exported. Second, you send the Export Set directly to a native file export directory.