About EDRM XML Load File Content


Imports > Add Load File

Requires Imports - Add/Edit Permissions

The eDiscovery application supports import of a load file such as an EDRM XML load file or Concordance DAT load file and builds an index representation based on the information in the imported load file.

For EDRM, the currently supported EDRM version is 1.1.

To add a load file, a user with the appropriate permissions selectsImports > Add Load File. In the dialog, you identify the location of the load file and the load file itself, and set the load file type to EDRM_XML.

For more information about how to add a load file, see Import Data from a Load File. The remainder of this topic focuses on EDRM XML load file information.

Mapping of EDRM Fields to Digital Reef Fields

The Digital Reef system includes a load file mapping configuration file ( loadfilemapping.xml), which resides in the AHS/conf directory. This file maps an EDRM field to a DR metadata field. The mapping specified in the file applies to each load file that is processed.

Note: This information is provided to help you understand the mapping of EDRM fields to Digital Reef fields. Consult a Digital Reef representative if you need changes to the load file mapping configuration file.

The following shows a sample mapping configuration file for the EDRM_XML format.

<loadfilemappings> 

<loadfilemapping loadfiletype="EDRM_XML">

<mapping extname="#EndPage" drname=""/>

<mapping extname="#From drname"="from"/>

<mapping extname="#To" drname="to"/>

<mapping extname="#CC" drname="cc"/>

<mapping extname="#BCC" drname="bcc"/>

<mapping extname="#Subject" drname="subject"/>

<mapping extname="#DateSent" drname="sent"/>

<mapping extname="#DateReceived" drname="received"/>

<mapping extname="#AttachmentNames" drname="attachments"/>

<mapping extname="#FileName" drname="filename"/>

- <mapping extname="#FileExtension" drname="origdocext"/>

<mapping extname="#FileSize" drname="size"/>

<mapping extname="#DateCreated" drname="datecreated"/>

<mapping extname="#DateAccessed" drname="dateaccessed"/>

<mapping extname="#DateModified" drname="datemodified"/>

<mapping extname="#DatePrinted" drname="dateprinted"/>

<mapping extname="#Title" drname="title"/>

<mapping extname="#Subject" drname="subject"/>

<mapping extname="#Author" drname="author"/>

<mapping extname="#Company" drname="company"/>

<mapping extname="#Category" drname="category"/>

<mapping extname="#Keywords" drname="keywords"/>

<mapping extname="#Comments" drname="comment"/>

</loadfilemapping>

<loadfilemappings>

File Type Processing

The EDRM XML import process uses the native file if it is provided. If no native file type is provided, the process uses the image and text data.

The EDRM XML import process supports a multi-page TIFF document. A combined image is created using the naming convention <docid>-combined-img.tif. If the TIFF images have any corresponding text, that text is combined as well, and associated with the ocrpath metadata field of the document.

The ocrstatus metadata field for the document is marked as EXTOCR (to flag that OCR processing took place externally, outside the eDiscovery application). If the document has an ocrstatus of EXTOCR, it is not subject to OCR processing again when the load file is added.

Restrictions

  • You must use an NFS or CIFS Connector for any load file.
  • When specifying the location of a load file, you can specify one Data Area only.
  • You can browse for the Data Area, but you should be aware of the name of the load file.
  • The Data Area specified must contain the load file and the data, as specified in the load file.
  • The system will not process any relationship information provided in an EDRM XML load file.