Browse Prior Art Database

Saving Pre-Load and Post-Load Filtering as a Single Filter

IP.com Disclosure Number: IPCOM000013340D
Original Publication Date: 2000-Dec-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 2 page(s) / 39K

Publishing Venue

IBM

Abstract

A problem today is that users can reduce large data sets by filtering them before they get loaded and displayed (sometimes referred to as "pre-load filtering" or "pre filtering",

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Saving Pre-Load and Post-Load Filtering as a Single Filter

  A problem today is that users can reduce large data sets by filtering them before they get loaded and displayed (sometimes referred to as "pre-load filtering" or "pre filtering",
e.g., via a query), and they can reduce the filtered data sets after they get loaded and displayed (referred to as "post-load filtering" or "post filtering", e.g., via inline table filtering such as with the SFTable or SFSelectionTable), but they can't save their combined post-load filters and pre-load filters as a single filter for later use. So, as the user filters a large data set down to the desired results via pre and post filtering, he or she can't reuse the filter later. The purpose of this invention is to allow the user to save all the pre-load and post-load filter settings and adjustments as one single filter.

    Within vastly huge Tivoli data sets it is sometimes hard for users to find exactly what they are looking for. They might not know all of the search parameters before starting the search. Those search parameters that are known can be selected before the data set is reduced. For example, when users want to look for a single set of subscribers in a profile manager (profile managers contain both profiles and subscribers) they might use an existing pre-filter to not show the profiles. They might select this pre filter by selecting "Open As >" and "Only Subscribers" in a menu system
(e.g., context menu and cascade menu).

    Then to further reduce the data set after the initial load the user could use post-filtering mechanisms, such as those provided by Tivoli's UI Library (i.e., SFTable and SFSelectionTable), to continue the data reduction. Sometimes it's easier to know how to red...