Exporting with the RDC

You can use the Relativity Desktop Client (RDC) to export production sets, saved search results, and folders. When you perform an export, the RDC automatically creates top-level folders for images, text, and natives. The RDC exports all documents included in the production set, search result, or folder.

You can also use RelativityOne Staging Explorer in RelativityOne to export files from RelativityOne workspaces that are set up with Aspera credentials. See RelativityOne Staging Explorer. This is the most common way of exporting files to and from RelativityOne.

Note: The same ports that are required for RelativityOne Staging Explorer are required to import and export using the RDC in Aspera mode.
Allow inbound/outbound connections to the server on the TCP port 33001.
Allow outbound connections to the server on the UDP ports 33001 - 33050.

Export folder options

Note: You need to install the RDC on your computer before you can perform an export.

See the following related pages:

Exporting RDC Permissions

The following permissions are required to use the exporting feature in Relativity Desktop Client:

Object Security Admin Operations
  • Document: Local Access (Download, Copy Text)

  • Allow Export

Technical considerations for .kwx files

Note the following:

  • .kwx stands for kCura Win edds eXport.
  • The .kwx file you call on when you load export settings is a SOAP-serialized file used to run the export.
  • SOAP is a protocol based on XML. It's designed specifically to transport or store procedure calls using XML. It does this by converting fields and properties of an object into the serial format of an XML stream.
  • When you run an export, the RDC collects all the inputs from the form into an object in memory. The RDC also passes the object on to the export process.
  • When you save an export settings object, Relativity passes that object in memory to a SOAP serializer. The SOAP serializer writes that object’s settings to XML.
  • When you load export settings, Relativity takes a serialized object and deserializes it to an in-memory settings object. Then it loops over all the properties and sets the actual form values to reflect those settings.