International Business Machines Corporation

Mimi Phuong-Thao Vo

Robert N Summers

Basuki N Soetarman

Taejae Lee

Kehsing J Chou

Mei-Ing W Huang

Tri Quac Ha

Alan Tsu-I Yaung

Dragutin Petkovic

Gerald Johann Wilmot

Peter C Yanker

Nelson Mendonca Mattos

Douglas Michael Hembry

David Couttie Fallside

Carlton Wayne Niblack

Siyi Terry Donn

Jing-Song Jang

Frank C Tung

Jean C Ho

Matthew Paul Anderson

Peter Paval Uhrowczik

Josephine Min-Kung Cheng

Jy-Jine James Lin

Mike A Marin

Siucheong Kenny Tse

Alan F Babich

Kenneth Carlin Nelson

Tawei Hu

Alan T Yaung

Xin Feng

Yuping Wang

Mark Joseph Sugg

Cynthia Marie Roberts

Michael Eric Mancuso

Christine M Hong

Denice A DeSimone

Richard L Dempsey

Anne C Fockler

Tracee Tao

A case creation event originating from an external content repository is detected by a processor executing an inbound event handler of a distributed integration framework that integrates a case management system with the external content repository. The case creation event is configured by the distributed integration framework to cause creation of a case within the case management system. The inbound event handler instructs the case management system to create the case within the case management system. An outbound event handler of the distributed integration framework instructs the external content repository to create a proxy case to remotely represent the case created within the case management system.

Case management integration with external content repositories

Provided are techniques for synchronization. In response to an event that modifies a real object at a first content management system, another event is triggered to perform an action to modify a corresponding proxy object at a second content management system. In response to an event that modifies a real object at the second content management system, another event is triggered to perform an action to modify a corresponding proxy object at the first content management system.

Use of proxy objects for integration between a content management system and a case management system

A method of controlling access in a content management system includes defining a domain among a plurality of domains for the content management system and designating a domain administrator for the domain. This enables the domain administrator to perform administrative tasks within the domain without revealing or affecting information in other domains of the content management system. For example, a domain administrator can view user information only for users associated with that domain. The domain administrator also can associate a user with only the defined domain, thereby limiting the user's access to information in the system to information associated with the domain.

Method for delegation of administrative operations in user enrollment tasks

A persistent federated folder within a federated content management system can be used to save federated search results, to act as a container in a workflow process, or a container for a set of documents or folders with similar characteristics. The federated folder and its associated storage structure have the capability to save its instances persistently. The federated folder operations can selectively create, retrieve, update, and/or delete an instance of a federated folder in addition to adding, retrieving updating and deleting its parts and its members. Seamless integration with the federated query is provided to operate on the federated folder transparently regardless of the locality of the user or the datastores the user is searching. Access rights for federated folders are enforced according to user's general privileges.

Method for managing persistent federated folders within a federated content management system

An architecture to enable search gateways as part of a federated search supports searching for data in one or more heterogeneous data sources. The one or more heterogeneous data sources are within a computer system. Initially, a request for data is received at a federated data source. From the federated data source, data is retrieved from one or more of one or more terminal data repositories or one or more search gateway data sources.

Architecture to enable search gateways as part of federated search

An architecture and implementation of a dynamic RMI server configuration hierarchy to support federated search and update across heterogeneous datastores. The RMI server configuration hierarchy supports searching for data in one or more heterogeneous data sources within a computer system. A request for data is received at a federated data source. Then, a server is selected to process the request based on a load of the server and based on whether the server can satisfy the request for data.

Architecture and implementation of a dynamic RMI server configuration hierarchy to support federated search and update across heterogeneous datastores

An extensible, object-oriented graphical user interface (GUI) framework that provides a consistent &ldquo;look and feel&rdquo; for an application that interfaces to the GUI framework and that manages and administers a plurality of datastores. The GUI framework is extensible by means of a &ldquo;plug-in&rdquo; facility through which support for additional datastores can be added, so that a collection of heterogeneous datastores can be managed using one consistent user interface.

Architecture and definition of an extensible, object-oriented graphical user interface framework for managing and administering heterogenous digital library datastores

A technique for delayed delivery of query results or other data from a federated server to a federated client until such information is needed. One or more commands are executed at a client computer to retrieve data from one or more datastores connected to a server computer. At the client computer, a search request is transmitted to the server computer. Then, a client collection is generated for use in retrieving physical data from the server computer. When data is requested using the client collection, physical data is retrieved from the server computer.

Delayed delivery of query results or other data from a federated server to a federated client until such information is needed

A design and implementation of a client/server framework for federated multi-search and update across heterogeneous datastores. In particular, a technique for manipulating data in one or more heterogeneous datastores at a computer is provided. An object-oriented model is provided for integrating one or more heterogeneous datastores with a federated datastore. One or more heterogeneous datastores and a federated datastore are generated based on the object-oriented model. The generated datastores are organized into a federated composition.

Design and implementation of a client/server framework for federated multi-search and update across heterogeneous datastores

A method, apparatus, article of manufacture, and a memory structure for transforming a query to reduce the need for merging the results from a number of result lists. The method comprises the steps of forming at least one subquery from the query, executing the formed subquery to generate a result list comprising a plurality of first result elements, and replacing the executed subquery with a logical combination of the first result elements to form a transformed query. The apparatus comprises a means for forming at least one subquery from the query, a means for executing the formed subquery to generate a plurality of first result elements, and a means for replacing the executed subquery with a logical combination of the first result elements to form a transformed query. In one embodiment, the invention comprises a program storage device, tangibly embodying a sequence of instructions for performing the method steps described above.

Method and apparatus for transforming queries

This invention is directed to relational extenders for a computer-based relational database. Each relational extender includes at least one column, in a first, business, table containing a user defined application database, dedicated to object handles for defining the complex data type of an object; a second, attribute, table containing at least one column defining a unique characteristic associated with the one object and one column dedicated to containing the object handle; and a third, metadata, table containing at least one column defining a common characteristic associated with all objects defined within the business table and one column dedicated to containing the object handle and at least one column dedicated to containing a reference to object data associated with the object. The relational extender further includes a fourth table containing a reference to each object handle column defined in the first table, a fifth table containing the names of the second and third tables for each object defined in the first table, a sixth table containing a reference to each object handle removed from the first table and including one column dedicated to containing a reference to the location of the object data associated with the removed object handle, and a seventh table having at least one column which describes a property of the data type of each object defined in the first table. The relational extender further includes an eighth table as a temporary holding table for the second table, and a ninth table as a temporary holding table for the third table. Both the eighth and ninth tables are used in conjunction with the extender triggers to ensure data integrity.

Computer program product for database relational extenders

This invention is directed to relational extenders for a computer-based relational database. Each relational extender includes at least one column, in a first, business table containing a user defined application database, dedicated to object handles for defining the complex data type of an object; a second, attribute, table containing at least one column defining a unique characteristic associated with the one object and one column dedicated to containing the object handle; and a third, metadata, table containing at least one column defining a common characteristic associated with all objects defined within the business table and one column dedicated to containing the object handles and at least one column dedicated to containing a reference to object data associated with the object. The relational extender further includes a fourth table containing a reference to each object handle column defined in the first table, and a fifth table containing the names of the second and third tables for each object defined in the first table.

Relational database extenders for handling complex data types

This invention is directed to relational extenders for a computer-based relational database. Each relational extender includes at least one column, in a first, business, table containing a user defined application database, dedicated to object handles for defining the complex data type of an object; a second, attribute, table containing at least one column defining a unique characteristic associated with the one object and one column dedicated to containing the object handle; and a third, metadata, table containing at least one column defining a common characteristic associated with all objects defined within the business table and one column dedicated to containing the object handle and at least one column dedicated to containing a reference to object data associated with the object. The relational extender further includes a fourth table containing a reference to each object handle column defined in the first table, and a fifth table containing the names of the second and third tables for each object defined in the first table.

Growing community of inventors

San Jose, CA, United States of America

Mimi Phuong-Thao Vo