1. Home
  2. Knowledge Base
  3. ClearView
  4. ClearView – 1.5 Rule Exclusions and 1.6 Inclusions

Extract from ClearView User Guide

Please refer to the full User Guide documentation here for further information.

1.5  Rule Exclusions – Remove False Positives

It is worth reviewing the reports to check for any potential false positives that are being captured. By doing this regularly, and adding exclusions to the pattern matching (see below), it ensures the ongoing reporting accuracy and value. It is extremely simple to exclude words or phrases by adding an exclusion to remove any potential false positive results, logic that will not trigger the Rule.  For example a student searching for the movie ‘Suicide Squad’ would trigger the Self-Harm Rule if an exclusion was not in place.

It is necessary to consider what popular expressions, language or trends may affect results and should be excluded in the Rules.  As trends change, more words can be added to the existing exclusion.

As most users will not have access to the Rules to add exclusions to remove false positives, users could add exclusions to their Queries for refining the data results for an immediate solution.  (Refer to Queries Exclusions) As there can be multiple Queries for different groups and users, it is best practice to apply exclusions to a Rule so irrelevant data is not captured and is not presented in any Query or report.

Users should advise the IT System Administrators that exclusions need to be applied to a Rule when they discover trends that are unnecessary in the results and will affect all users.  

1.5.1 Steps to Exclude

Access the relevant Rule.  In this example, to exclude ‘Suicide Squad’, it will be the Self Harm Rule.  

Click  ‘Add Criteria’ and choose the Text Search Criteria’ option.

1. Tick ‘NOT’ to search for the string.

2. Type ‘suicide squad’ in ‘Strings to search for’ text field.  More strings can be added to the text search Criteria as needed.

TIP:  add all variations that could be used.  e.g. two words or one word or blond with and without ‘e’ as shown.

3. Click ‘Update’ and apply the changes. Click on ‘Back to Rule’ to return to the Rules set and remember to ‘Apply Changes’ to implement the changes.

The Ruleset list will now show the new configuration.

NOTE: Changes to a rule only apply from the date the change is implemented.  Any data captured preceding the change, would still report ‘suicide squad’ in Queries or reports on timeframes prior to the change date.

1.5.2 Exclude pattern words  

On rare occasions, there may be a need to exclude a word that is in the predefined pattern list.  Edit the pattern list and add the word or words you do not want to capture. This field only ignores words that are in the ‘Pattern lists to use’ as selected in the field above.

1.6 Inclusions – Add Strings to Rule

While it is important to remove unwanted results, there may also be a need to capture new popular expressions or words, or words that cause concern, which do require monitoring.  Adding specific words or strings to the Pattern Matching Criteria for the relevant Rule or Rules, will ensure that important trends or concerns can be captured for reporting.

Some examples that provide welfare and support staff with evidence-based triggers are:

Fights – organised in a nearby park can be monitored easily by adding the name of the park to the Aggression Rule.

Drugs – new slang or street names can be added to the Drugs or Self Harm Rules.

Reputational Risk – school, teachers’ names or nicknames can be added to an ‘Online Reputational Risk’ Rule to capture inappropriate comments.

Select the relevant Rule and click ‘[edit]’.  

Select the pattern Criteria for the Rule and click ‘[edit]’.  

  1. Type in the word or phrases in the ‘Additional strings to search for’ field. Enter one word or phrases per line.
  2. Click ‘Update’ to add the string. Click on ‘Back to Rule’ to return to the Ruleset and remember to
    Apply Changes’ to implement the changes.

NOTE: Query searches for additional words or strings cannot be achieved as the results have not been captured in the data source until a Rule recognises the pattern matched.

Was this article helpful?