Browse Prior Art Database

Method for Cross-Service Predicate Search Conditions

IP.com Disclosure Number: IPCOM000105303D
Original Publication Date: 1993-Jul-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 2 page(s) / 76K

Publishing Venue

IBM

Related People

Jackson, BK: AUTHOR [+4]

Abstract

Often, the user does not know the service that has ownership of a particular object. For example, consider the case where a user remembers receiving a meeting notice, but does not remember if it was posted to the calendar or if it is still within the inbasket which has hundreds of entries or if the meeting notice was filed to disk. Current methods require the user to access multiple applications to find the meeting notice. The user may need to enter the mail application and perform a search request, then enter the calendar service to perform a search request and finally enter the cabinet filing service to perform a search request. Users desire a method by which a single search request can be generated and understood by multiple applications simultaneously.

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

Method for Cross-Service Predicate Search Conditions

      Often, the user does not know the service that has ownership of
a particular object.  For example, consider the case where a user
remembers receiving a meeting notice, but does not remember if it was
posted to the calendar or if it is still within the inbasket which
has hundreds of entries or if the meeting notice was filed to disk.
Current methods require the user to access multiple applications to
find the meeting notice.  The user may need to enter the mail
application and perform a search request, then enter the calendar
service to perform a search request and finally enter the cabinet
filing service to perform a search request.  Users desire a method by
which a single search request can be generated and understood by
multiple applications simultaneously.  A method is desired whereby
results from a search request can be correlated and formatted
consistently even though the results originated from differing
services.

     This article describes a methodology for handling predicate
search conditions being simultaneously generated for differing
services within an office application.  Upon a user requesting a
cross-service search criteria, a Predicate Cross-Component
Correlation Service performs boolean search operations on the
inbasket's database, calendar's database, file cabinet's database and
any other service that was requested within the search criteria.  The
search criteria is divided into separate commands.  Each command is
generated and formatted according to the individual services native
format, i.e., calendar request are formatted according to the
calendar's search format and inbasket search commands formatted
according to the inbasket's search commands.  Conditions can be
specified for which an object should be excluded from the retrieval
process.  Parametric searches are derived based on information
outside the scope of the content itself.  For example, the subject,
sensitivity level or add...