Overview of Filtering Options
RAIDLOG provides powerful filtering capabilities to help you quickly find the data you need. Filters can be applied across different field types, allowing for precise control over your data display. Below, we’ll break down the filtering options by the type of field.
1. Text Fields
Text fields are one of the most commonly used fields. RAIDLOG allows you to filter text fields using the following options. Please note that text filters are not case sensitive.
Contains: This option filters records that contain a specific word or phrase.
Equals: Use this filter to find records where the text exactly matches your search term.
Starts With: Find all records where the text begins with a certain string of characters.
Ends With: Use this to filter records that end with a specific text string.
Is Empty: Show records where the text field is completely empty (no data entered).
Is Not Empty: Display records where the text field contains any data (not empty).
Is Any Of: Filter records that match any one of several specified values. You can enter multiple terms, and the filter will show records that match any of them.
Pattern Match: Use this filter to find records that match a specific pattern, such as a regular expression. This is useful for finding text that follows a certain format, like email addresses or specific code patterns.
Example: To find all projects with the name "PMO," you can use the "Contains" filter with the term "PMO."
2. Date Fields
Filtering by date is crucial for tracking timelines and deadlines. RAIDLOG offers several options:
Is: Use this filter to display records that match a specific date exactly. This is useful for pinpointing data from a single day.
Example: To find all Action Items due on July 1, 2024, use the "Is" filter and select that date.
After: This filter shows records with dates after a specified date. It's useful for identifying upcoming events or future deadlines.
Example: To see all issues that are due after August 15, 2024, apply the "After" filter with that date.
Since: Similar to the "After" filter, but whereas the "After" filter excludes the specified date, "Since" includes it.
Example: To review all risks identified since January 1, 2024, use the "Since" filter with that start date.
Before: Use this filter to display records with dates before a specified date. It’s ideal for looking at historical data or past events.
Example: To see all completed tasks before June 30, 2024, apply the "Before" filter with that date.
Is Empty: This filter shows records where the date field is empty or has not been set. It’s useful for identifying missing or incomplete data.
Example: To find all action items without a due date, use the "Is Empty" filter.
Is Not Empty: This filter displays records where the date field is populated with any date. It’s useful for filtering out records that have incomplete data.
Example: To see all issues that have been assigned a due date, apply the "Is Not Empty" filter.
Newest: This filter displays the most recent records based on the date field, and it allows you to specify how many records to display. This is useful for reviewing the latest entries.
Example: To see the three most recently identified risks, use the "Newest" filter and set the value to "3."
Oldest: This filter shows the earliest records based on the date field, and it also allows you to specify how many records to display. It’s helpful for assessing the oldest entries in your dataset.
Example: To view the five oldest issues logged in your project, apply the "Oldest" filter and set the value to "5."
3. Numeric Fields
Numeric fields can be filtered based on specific values or ranges, allowing you to manage and analyze quantitative data efficiently. RAIDLOG offers the following filtering options for numeric fields:
Equals: Use this filter to display records where the numeric field exactly matches a specified value. This is useful for finding data points with a specific number.
Example: To find all projects with a budget of exactly $50,000, use the "Equals" filter with the value "50000".
Does Not Equal: This filter shows records where the numeric field does not match the specified value. It’s helpful for excluding a particular number from your results.
Example: To exclude all action items with an importance of 5, apply the "Does Not Equal" filter with the value "5."
Greater Than: This filter displays records where the numeric value is greater than a specified number. It’s useful for identifying entries that exceed a certain threshold.
Example: To list all issues with an impact score greater than 7, use the "Greater Than" filter with the value "7."
Greater Than or Equal To: Similar to "Greater Than," but includes records that match the specified value as well. This is useful for broader searches.
Example: To see all risks with a probability score of 8 or higher, use the "Greater Than or Equal To" filter with the value "8."
Less Than: This filter shows records where the numeric value is less than a specified number. It’s ideal for finding data that falls below a certain threshold.
Example: To find all decisions with an importance of less than 2, use the "Less Than" filter with the value "2."
Less Than or Equal To: Similar to "Less Than," but includes records that match the specified value as well. This is useful when you want to include the boundary value.
Example: To see all issues with an impact score of 3 or lower, use the "Less Than or Equal To" filter with the value "3."
Is Empty: This filter displays records where the numeric field has no value (i.e., the field is empty). It’s useful for identifying records with missing numerical data.
Example: To find all projects without a specified budget, use the "Is Empty" filter.
Is Not Empty: This filter shows records where the numeric field contains any value. It’s useful for filtering out records that have incomplete data.
Example: To list all projects that have a budget, apply the "Is Not Empty" filter.
Highest: This filter allows you to display the records with the highest values in a numeric field. You can specify how many of the top values you want to see.
Example: To see the top 3 projects with the highest budgets, use the "Highest" filter and set the value to "3."
Lowest: This filter allows you to display the records with the lowest values in a numeric field. You can specify how many of the lowest values you want to see.
Example: To view the 5 action items with the lowest importance, apply the "Lowest" filter and set the value to "5."
4. Dropdown/Select Fields
Dropdown or select fields are pre-defined options that can be filtered by:
Is: Use this filter to display records where the dropdown field matches a specific option. This is useful when you want to see all records that correspond to a particular category or status.
Example: To find all action items with the state "Completed," use the "Is" filter and select "Completed" from the dropdown options.
Is Not: This filter shows records where the dropdown field does not match a specific option. It’s helpful for excluding a particular category or status from your results.
Example: To exclude all action items with the state as "In Work," apply the "Is Not" filter and select "In Work."
Is Any Of: This filter allows you to display records that match any one of several specified options from the dropdown field. You can select multiple values, and the filter will show records that match any of them.
Example: To find all action items that are either "In Work," "In Review," or "Completed," use the "Is Any Of" filter and select those options.
5. Tag Field
Includes Any: This filter allows you to display records that match any one of several specified options from the dropdown field. You can select multiple values, and the filter will show records that match any of them.
Example: To find all action items that are either "In Work," "In Review," or "Completed," use the "Includes Any" filter and select those options.
Includes All: This filter lets you display records matching all selected options from a dropdown field. This is useful when you want to find records that meet multiple criteria simultaneously.
Example: To find all action items tagged with the "High Priority" and "Urgent" tags, use the "Includes All" filter and select both options. Only tasks that have both tags will be displayed.
Contains: This option filters tags that contain a specific word or phrase.
Equals: Use this filter to display records where the tag list contains only the ones specified. This is useful when you want to see records that match exactly the tags you choose (no more, no less).
Not Equals: This is the inverse of the “Equals” filter. Use this filter to display records where the tag list contains not only the ones specified. This is useful when you want to see records that do not match exactly the tags you choose.
Is Empty: This filter displays records where the tag field has no value (i.e., the field is empty). It’s useful for identifying records with missing tags.
Is Not Empty: This filter shows records where the tag field contains any value. It’s useful for filtering out records that have no tags.
Pattern Match: Use this filter to find records that contain any tag that matches a specific pattern, such as a regular expression. This is useful for finding tags with wildcard-type search patterns.
Example: Searching for "dess?ert” would match both "Desert” and “Dessert”.
Greater Than: This filter displays records where any tag is lexicographically greater than a specified value. It’s useful for identifying tags within an alphabetical range.
Example: To list all RAID with a tag that starts with "Z", use the "Greater Than" filter with the value "Z".
Greater Than or Equal To: Similar to "Greater Than," but includes the specified value as well. This is useful when you want to include the boundary value.
Less Than: This filter displays records where any tag is lexicographically less than a specified value. It’s useful for identifying tags within an alphabetical range.
Example: To list all RAID with a tag that starts with "A", use the "Less Than" filter with the value "B".
Less Than or Equal To: Similar to "Less Than," but includes records that match the specified value as well. This is useful when you want to include the boundary value.
6. Note Field
Contains: This option filters notes that contain a specific word or phrase.
Is Empty: This filter displays records where the notes field has no value (i.e., the field is empty). It’s useful for identifying records that have no notes.
Is Not Empty: This filter shows records where the notes field contains any value. It’s useful for filtering out records that have no notes.
Pattern Match: Use this filter to find records that contain any note that matches a specific pattern, such as a regular expression. This is useful for finding notes with wildcard-type search patterns.
Greater Than: This filter displays records where any note is lexicographically greater than a specified value. It’s useful for identifying notes within an alphabetical range.
Example: To list all RAID with a note that starts with "Z", use the "Greater Than" filter with the value "Z".
Greater Than or Equal To: Similar to "Greater Than," but includes the specified value as well. This is useful when you want to include the boundary value.
Less Than: This filter displays records where any note is lexicographically less than a specified value. It’s useful for identifying notes within an alphabetical range.
Example: To list all RAID with a note that starts with "A", use the "Less Than" filter with the value "B".
Less Than or Equal To: Similar to "Less Than," but includes records that match the specified value as well. This is useful when you want to include the boundary value.
Created Before: Use this filter to display records with notes created before a specified date. It’s ideal for looking at historical data or past events.
Example: To see RAID items with notes that were created before December 16, 2024, apply the "Before" filter with that date.
Created Since: This filter shows records with notes created after a specified date. It's useful for identifying recent events.
Example: To see only issues to which a note has been added since August 16, 2024, apply the "Since" filter with that date.
Latest created: This filter displays the most recent records based on the date field, and it allows you to specify how many records to display. This is useful for reviewing the latest entries.
Example: To see the three most recently identified risks, use the "Newest" filter and set the value to "3."
Oldest created: This filter shows the earliest records based on the date field, and it also allows you to specify how many records to display. It’s helpful for assessing the oldest entries in your dataset.
Example: To view the five oldest issues logged in your project, apply the "Oldest" filter and set the value to "5."
Updated Before: Use this filter to display records with dates before a specified date. It’s ideal for looking at historical data or past events.
Example: To see all completed tasks before June 30, 2024, apply the "Before" filter with that date.
Updated Since: Similar to the "After" filter, but whereas the "After" filter excludes the specified date, "Since" includes it.
Example: To review all risks identified since January 1, 2024, use the "Since" filter with that start date.
Latest updated: This filter displays the most recent records based on the date field, and it allows you to specify how many records to display. This is useful for reviewing the latest entries.
Example: To see the three most recently identified risks, use the "Newest" filter and set the value to "3."
Oldest updated: This filter shows the earliest records based on the date field, and it also allows you to specify how many records to display. It’s helpful for assessing the oldest entries in your dataset.
Example: To view the five oldest issues logged in your project, apply the "Oldest" filter and set the value to "5."