Arctera Enterprise Vault™ eDiscovery Administrator's Guide
- Configuring eDiscovery: Desktop Client
- Importing configuration data from an XML file
- Setting eDiscovery 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 eDiscovery
- Defining email targets with Address Manager
- Building eDiscovery search schedules
- Manually reviewing items
- About reviewing with eDiscovery
- 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 eDiscovery reports
- Accessing reports through the OData web service
- Appendix A. Enterprise Vault properties for use in eDiscovery searches
- Appendix B. Troubleshooting
- Issues with Insight eDiscovery Custodian Manager
About eDiscovery cases
Everything that is related to a discovery action, including user permissions, item reviewers, the marking scheme, the tagging scheme, searches, analyses, and the set of items to be reviewed, is grouped in a case. Within a single eDiscovery system, reviewers can work on multiple cases at the same time.
eDiscovery provides an additional option with which you can enable analytics on a case or a research folder. This option provides additional analyses of the metadata and content of items that are collected in the case.
Any new cases that you create with eDiscovery 10.0.1 or later comply with the U.S. government's Federal Information Processing Standards (FIPS) for encoding and encrypting data. This is also true of any cases that you created with older and non-FIPS-compliant versions of eDiscovery, provided that you did not enable analytics in these cases. If you have enabled analytics in these old cases then, after you upgrade to eDiscovery 10.0.1 or later, you can make the cases FIPS-compliant by disabling analytics and then reenabling it.