Veritas Alta™ Surveillance User Guide
- Introducing Veritas Alta Surveillance
- Getting started
- Working with dashboard widgets
- Managing employee groups
- Managing departments
- About departments
- Understanding the Departments page
- Searching departments
- Creating departments
- Moving existing departments under other departments
- Adding monitored employees and employee groups to departments
- Editing monitoring policies
- Editing department details and monitoring policy
- Managing exception employees
- Designating employees as exception employee
- Assigning further exception reviewers to an exception employee
- Removing exception status
- Removing exception reviewers
- Managing department users
- Managing department-level searches
- Managing department-specific hotword sets
- Managing department-specific labels
- Managing department-specific trash rules
- Managing department-specific allowlist rules
- Managing department-specific review comments
- Viewing employees associated with departments
- Managing users, roles, and permissions
- Managing application-level searches
- Managing application-specific hotword sets
- Managing application-specific labels
- Managing application-specific trash rules
- Managing application-specific allowlist rules
- Managing application-specific review comments
- Managing data requests
- Managing search schedules
- Managing export operations
- Managing reviews
- About reviewing with Alta Surveillance
- Limitations on reviewing certain types of Skype for Business content
- Understanding the Review page
- Changing the Preview pane position
- Rearranging columns in the item list pane
- Filtering the items in the Review pane
- Viewing dynamic review item counts on the calendar
- Reviewing searched items
- Adding or removing text for machine learning
- Assigning review status to items
- Viewing hotwords highlighting
- Viewing hotwords in collaboration message
- Viewing tags highlighting
- Viewing predicted labels of review items
- Viewing the full content in a new window
- Adding comments to items
- Escalating the review items
- Applying labels to items
- Viewing history of items
- Printing and downloading the items and attachments
- Viewing Intelligent Review Details
- Working with reports
- About Alta Surveillance reports
- Predefined reports
- Enhanced reporting
- Configuring a reporting endpoint
- Authentication
- Departments API
- Users API
- UserRoles API
- Roles API
- ItemMetrics API
- ReviewerMapping API
- MonitoredEmployees API
- Evidence Of Review By Dept Async API
- Report Status API
- Evidence of Review by Department API
- Supported OData query options
- Supported reporting endpoint API filters and their values
- Responses
- Managing Power BI templates for reporting APIs
- Guidelines for using Alta Surveillance templates with Microsoft Power BI Desktop
- Configuring Microsoft Power BI Templates for Reporting APIs
- TEMPLATE - Item Metrics
- TEMPLATE - Reviewer Mapping
- TEMPLATE- Evidence Of Review By Department - Submit report request
- TEMPLATE- Evidence Of Review By Department - View report data
- Saving, editing, and refreshing the Power BI reports
- Managing Audit Settings
- Working with Audit viewer
Using fuzzy searches
Searching natural language is inherently imprecise. Fuzzy search is an alternative search method that finds words that require a proscribed number of character modifications (known as edits) to match the search term. For instance, a fuzzy search for 'ax' would match the word 'axe', since only a single deletion, removing the 'e', is required to match the two words.
The fuzziness argument specifies that the results match with a maximum edit distance of 2. It should be noted that fuzziness should only be used with values of 1 and 2, meaning a maximum of 2 edits between the query and a term in a document is allowed. To create a fuzzy search, add a tilde character (~) and a numerical value of 1 or 2. For example, to use a fuzzy search to find the word testing, you could use the following arguments:
Note:
The fuzzy search only works for individual words; it does not work for phrases.
tesitng~1
etsitng~2
The following examples show how the arguments would work for the word testing, given that only 2 edits are allowed:
tesitng~1 is searchable because, 1 edit is required
etsitng~2 is searchable because, 2 edits are required
etsitgn~2 is not searchable because, 3 edits are required