Configuring export

Configure export to allow IBM® eDiscovery Manager users to export selected content for external review or storage.

eDiscovery Manager web client configuration

The eDiscovery Manager web client is your primary export configuration tool. Before your users can export content, you must configure exports on the following panes of the Administration page of the eDiscovery Manager web client.
  • User Roles

    An eDiscovery Manager Super User must assign the Exporter user role to users to permit them to export content.

  • Export Settings

    Export settings include the absolute path or, in some circumstances, Universal Naming Convention (UNC) path of the export directory, the maximum number of simultaneous export tasks that you want eDiscovery Manager to support, and the maximum number of threads to allocate for all export tasks.

    Important: WebSphere® Application Server might not be able to locate mapped network drives in Microsoft Windows under certain circumstances. Because of how permissions are assigned to mapped network drives, not all users are able to access these drives through the drive letters. Only the services owned by the Local System Account can map network drives that can be seen by all other accounts. In this case, you must configure the path of the directory that will contain all exported content as a UNC path.
  • Export Formats

    You can configure the content export formats that eDiscovery Manager provides, or you can create and configure new content export formats. Be sure to configure the plug-in properties of the Extract and BatchComplete plug-in points for all formats to which your users will want to export.

Syntax for the export file name

When you export Content Collector files or when you export multipart documents in custom collections, the names of the export files depend on whether the collection definition includes a FILE_NAME collection field.
If a FILE_NAME collection field is included in the collection, content in that collection is exported to files that have names with the following syntax where originalFileName is the original name of the archived file:
originalFileName_itemID_or_GUID.extension
If a FILE_NAME collection field is not included in the collection, content in that collection is exported to files that have names with the following syntax:
itemID_or_GUID.extension

To verify whether a FILE_NAME collection field is included in a collection of custom or Content Collector file types, check the Search Mapping tab on the Collections pane of the Administration page. For these types of collections, mapping the relevant content server property or attribute to a collection field that is named FILE_NAME can be useful.