Enterprise Vault™ Discovery Accelerator Administrator's Guide
- Introducing Discovery Accelerator
- Overview and latest updates
- Configuring Compliance Accelerator Desktop Client
- Importing configuration data from an XML file
- Setting Discovery Accelerator system configuration options
- Setting up and assigning roles
- Working with cases
- Setting up review marks and tags
- Using rules to mark and tag items automatically
- Using Custodian Manager
- Searching for items
- About searching with Discovery Accelerator
- Defining email targets with Address Manager
- Building Discovery Accelerator search schedules
- Manually reviewing items
- About reviewing with Discovery Accelerator
- Searching within the review set
- Deleting items from Enterprise Vault archives
- Working with research folders
- Exporting and producing items
- About exporting and producing items
- Creating and viewing reports
- Enhanced reporting
- Available Discovery Accelerator reports
- Accessing reports through the OData web service
- Appendix A. Enterprise Vault properties for use in Discovery Accelerator searches
- Appendix B. Troubleshooting
- Issues with Custodian Manager
Format of the Dataload.xml file
You can use the Dataload.xml
file with both Compliance Accelerator and Discovery Accelerator, so it contains some information that applies to both applications. However, the file is well documented and shows which sections apply to which application.
Table: Primary Discovery Accelerator sections in Dataload.xml file
Section | Defines |
---|---|
ApplicationVaultStore | Vault stores available to all cases for searching. |
Employee | Users to add to the system as administrators or reviewers, and the application administration roles to assign to them. |
ApplicationTarget | Targets and their email addresses. These are available in all cases. |
ApplicationTargetGroup | Groups of targets. These are available in all cases. |
Department | Cases. This section includes definitions of the following:
|
AttributeDefinition | Custom search attributes. |
The second part of the file describes each XML entry. The last part of the file provides sample entries for a Discovery Accelerator system.
If you use any non-ASCII characters in a dataload file, you must specify the appropriate encoding. For example, you can save a file that contains accented European characters in Unicode format or add the following at the start of the file:
<?xml version="1.0" encoding="iso-8859-1" ?>