Browse Prior Art Database

Cross-Service Predicate Delete Conditions

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

Publishing Venue

IBM

Related People

Salahshour, A: AUTHOR [+2]

Abstract

Often, the user needs to delete all references to a particular subject. This user may need to delete references to the subject matter which occurs within multiple components of an office application. For example, consider the case where a user needs to cancel a meeting notice from their calendar and all inbasket entries associated with the meeting notice. Current systems require the user to issue a calendar operation for cancellation and then enter their mail application to delete the item from the inbasket list. Users desire a method by which a single delete request can be generated and understood by multiple components simultaneously. A method whereby a delete request can be generated across multiple components with a predicate condition is desirable.

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

Cross-Service Predicate Delete Conditions

      Often, the user needs to delete all references to a particular
subject.  This user may need to delete references to the subject
matter which occurs within multiple components of an office
application.  For example, consider the case where a user needs to
cancel a meeting notice from their calendar and all inbasket entries
associated with the meeting notice.  Current systems require the user
to issue a calendar operation for cancellation and then enter their
mail application to delete the item from the inbasket list.  Users
desire a method by which a single delete request can be generated and
understood by multiple components simultaneously.  A method whereby a
delete request can be generated across multiple components with a
predicate condition is desirable.

      This article addresses a methodology for predicate delete
conditions for differing components within an office application.
Upon a user requesting a cross-service delete criteria, a Predicate
Delete Cross-Component Correlation Service performs boolean search
operations on the inbasket's database, calendar's database, file
cabinet's database and any other component supported by the Predicate
Delete Cross-Component Service.  The search criteria are divided into
separate commands.  The service generates and formats each command
according to the individual service's native format, i.e., calendar
requests are formatted according the calendar's search format and
inbasket request are 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 addressee information.  In
addition, a search criteria across differing services need not be
based on the same type of searches.  For example, a parametric search
can be conducted in a calendar component while a contextual search is
being conducted by the mail service.

      Upon the user specifying a cross service deletion, a query
request is constructed from the user's specification f...