Enterprise Vault™ Discovery Accelerator Reviewer's Guide
- Introducing Discovery Accelerator
- Introducing Veritas Surveillance
- Searching for items
- Manually reviewing items
- About reviewing with Discovery Accelerator
- About the Review pane
- Filtering the items in the Review pane
- Searching within the review set
- Finding all items in the same conversation
- Assigning review marks and tags to items
- Adding comments to items
- Viewing the history of items
- Displaying printable versions of items
- Downloading the original versions of items
- Copying the item list to the Clipboard
- Deleting items from Enterprise Vault archives
- Changing how the Review pane looks
- Setting your Review pane preferences
- Working with research folders
- About research folders
- Creating research folders
- Editing the properties of research folders
- Copying items to research folders
- Reviewing the items in research folders
- Exporting items from research folders
- Giving other users access to your research folders
- Removing items from research folders
- Converting research folders into cases
- Deleting folders
- Exporting and producing items
- Creating and viewing reports
- About the Discovery Accelerator reports
- Enhanced reporting
- Creating Discovery Accelerator reports
- Available Discovery Accelerator reports
- Viewing existing reports
- Deleting reports
- Accessing reports through the OData web service
- Configuring a Power BI template for reporting
- Appendix A. Enterprise Vault properties for use in Discovery Accelerator searches
- About the Enterprise Vault search properties
- System properties
- Custom Enterprise Vault properties
- Custom Enterprise Vault properties for File System Archiving items
- Custom Enterprise Vault properties for SharePoint items
- Custom Enterprise Vault properties for Compliance Accelerator-processed items
- Custom properties for use by policy management software
- Custom properties for Enterprise Vault SMTP Archiving
Supported OData query options
The currently supported OData query options that can be used for query composition to customize responses are mentioned below.
: Use the $select query parameter to return a set of properties that are different than the default set for an individual resource or a collection of resources. With $select, you can specify a subset of the default properties.
Example: In the example below, the query returns only two properties, Department name and Department status in the result.
https://<Reporting endpoint base URL>/odata/departments?$select=DepartmentName,Status
Use the $count query parameter to retrieve the total count of matching resources.
In the example below, the query returns a total count of roles in the system irrespective of any other filters.
https://<Reporting endpoint Base URL>/odata/roles?$count=true
Use the $top query parameter to limits the number of records returned.
In the example below, the query returns the top 10 records in the result.
https://<Reporting endpoint Base URL>/odata/departments?$top=10
Use the $skip query parameter to skips a specified number of records before returning results.
In the example below, the query returns the records skipping the first 60 records in the result.
https://<Reporting endpoint Base URL>/odata/departments?$skip=60
Use the $skipToken query parameter to retrieve the next page of results from result sets that span multiple pages.
Some requests return multiple pages of data due to server-side paging to limit the page size of the response. Reporting APIs use the $skipToken query parameter to reference subsequent pages of the result. The $skipToken parameter contains an opaque token that references the next page of results and is returned in the URL provided in the @odata.nextLink property in the response.
For example, if you call the Roles API that have more than 1000 records in the result, then the response will return only 1000 records with @odata.nextLink property as shown below.
"@odata.nextLink": "https://<Reporting endpoint Base URL>/odata/roles?$skipToken=29310"
To fetch the next page of records, the value of the @odata.nextLink can be used as the endpoint URL which has a skipToken value.