US5446883A - Method and system for distributed information management and document retrieval - Google Patents

Method and system for distributed information management and document retrieval Download PDF

Info

Publication number
US5446883A
US5446883A US07/965,165 US96516592A US5446883A US 5446883 A US5446883 A US 5446883A US 96516592 A US96516592 A US 96516592A US 5446883 A US5446883 A US 5446883A
Authority
US
United States
Prior art keywords
computer
document
inquiry
solution
data base
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US07/965,165
Inventor
Louise Kirkbride
Todd Eisemann
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CA Inc
Original Assignee
Answer Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US07/965,165 priority Critical patent/US5446883A/en
Application filed by Answer Systems Inc filed Critical Answer Systems Inc
Assigned to ANSWER COMPUTER, INC. reassignment ANSWER COMPUTER, INC. ASSIGNMENT OF ASSIGNORS INTEREST. Assignors: EISEMANN, TODD, KIRKBRIDE, LOUISE
Assigned to ANSWER SYSTEMS, INC. reassignment ANSWER SYSTEMS, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: ANSWER COMPUTER, INC.
Publication of US5446883A publication Critical patent/US5446883A/en
Application granted granted Critical
Assigned to PLATINUM TECHNOLOGY IP, INC. reassignment PLATINUM TECHNOLOGY IP, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FREEDMAN, LARRY S.
Assigned to COMPUTER ASSOCIATES THINK, INC. reassignment COMPUTER ASSOCIATES THINK, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PLATINUM TECHNOLOGY IP, INC.
Assigned to PLATINUM TECHNOLOGY, INC. reassignment PLATINUM TECHNOLOGY, INC. MERGER (SEE DOCUMENT FOR DETAILS). Assignors: ANSWER SYSTEMS, INC.
Assigned to PLATINUM TECHNOLOGY IP, INC. reassignment PLATINUM TECHNOLOGY IP, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PLATINUM TECHNOLOGY, INC.
Anticipated expiration legal-status Critical
Assigned to CA, INC. reassignment CA, INC. MERGER (SEE DOCUMENT FOR DETAILS). Assignors: COMPUTER ASSOCIATES THINK, INC.
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/93Document management systems

Definitions

  • This invention relates to heuristic learning application programs and more particularly to a method for entering user-specific problems and for heuristically retrieving documented solutions among multiple distributed computer management systems.
  • a recurring problem among users of expert systems arises when multiple systems are employed in solving a common set of problems.
  • expert systems are used to solve recurring problems by applying a set of either known or learned rules to a common set of problem characteristics. As new problems develop, responses to these problems are designed and installed on the system.
  • Use of a single expert system is often cumbersome, particularly when users are located in remote sites. For example, a set of users in the United States would have difficulty sharing an expert system with users in Japan. This difficulty would be particularly acute if the two groups commonly faced diverging sets of problems and if the expert systems were programmed to respond in languages native to only one of the two groups.
  • the telecommunications costs associated with the use by the Japanese of the U.S. installation might be greater than the costs of installing a similar expert system in Japan.
  • This sharing of information would occur when one data base receives a problem for which it does not have a solution, and for which an associated data base is positioned to more efficiently solve.
  • the first data base might then escalate the problem to the second data base which would solve the problem and then return a solution to the first.
  • Such a system would be capable of selectively transferring problems, solutions, and useful information efficiently between data bases.
  • the system (9) includes multiple expert or inquiry computers (10) connected using a networking scheme such as a modem or other communication link.
  • Each inquiry computer (10) contains a processor (11), a plurality of specially configured registers, and a memory array comprising an acyclic graph data base (27).
  • the computers (10) transfer problems to each other using a selective protocol which imports problems, identifies or creates document solutions and exports the solutions to the originating computer (10).
  • a problem is logged into the inquiry computer (10) and a search for a solution document is undertaken. If no solution document is found, a problem report is then created and posted into a document.
  • the document may be escalated to a remote inquiry computer by placing it in an export index (42), wherein the problem may be solved and a solution automatically sent electronically to the original user.
  • FIG. 1 is a block diagram showing distributed information system 9 in a preferred configuration having a primary inquiry computer 41 connected to a plurality of secondary and lower order computers;
  • FIG. 2 is a schematic diagram showing the preferred embodiment of inquiry computer 10 of the present invention.
  • FIG. 3 is a schematic diagram showing various document levels within acyclic graph data base 27 of the present invention.
  • FIG. 4 is a block diagram showing the contents of local area network 19 of the present invention.
  • FIG. 5 is a block diagram showing the steps implemented in secondary inquiry computer 43 of the present invention.
  • FIG. 6 is a block diagram showing the steps implemented in primary inquiry computer 41 of the present invention.
  • FIG. 1 A preferred block diagram of the distributed information management and document retrieval system 9 of the present invention is shown in FIG. 1.
  • Primary inquiry computer 41 is shown connected to a pair of secondary computer systems 43, which are in turn shown further connected to a plurality of tertiary inquiry computers 45.
  • tertiary inquiry computers 45 could further contain additional subsidiary inquiry computers.
  • An alternative embodiment might contain networking schemes in which each of the inquiry computers 10 are connected to other inquiry computers. This connection to other computers may be in a ring network configuration, a star network configuration, or a combined network embodying both ring and star Characteristics, rather than in the modified tree structure of FIG. 1.
  • inquiry computer 10 is shown.
  • the preferred embodiment of inquiry computer 10 of the present invention is implemented on a general purpose, microprocessor based, computer such as a Sun Microsystems, IBM, or Hewlett-Packard computer.
  • Inquiry computer 10 is maintained and operated by a system administrator who is at least somewhat knowledgeable about the subject matter being supported, as well as the computer hardware and associated software. The system administrator is able to change the structure and model of system 9 as needed.
  • system manager there is at least one data owner who is knowledgeable about various solution documents, but who is not charged with operation or maintenance of inquiry computer 10 and its hardware components.
  • support engineers who may enter incidents, but do not enter solutions or maintain the system.
  • Inquiry computer 10 of the present invention is shown having processor 11 which is connected to keyboard 15 and display 13. Keyboard 15 and display 13 enable a user to interact with processor 11 by entering data and viewing the displayed contents of various memories. Also connected to processor 11 are printer 17, mass storage 21, and Local Area Network (LAN) 19. Printer 17 enables the user to make a permanent record of the various memory contents. Mass storage 21 is useful for long term storage and for maintaining large quantities of data. Local area network 19 enables the user to exchange data files and to interact with the memories and processors of other computer systems, as described in more detail below. Connection to an alternative Wide Area Network (WAN), is also possible, for serving a geographic area larger than that served on a traditional LAN 19.
  • WAN Wide Area Network
  • Acyclic graph data base 27 contains a collection of documents designed to 5provide assistance to users who log inquiries into the system. As in a traditional expert system, the user logs onto computer 10 and presents a problem or incident to be solved by a document resident in the system. Rather than stating the problem as a series of answers to questions posed by the machine, as in the classical expert environment, the user searches a sequence of indices at various nodes in an acyclic graph. This acyclic graph data base 27 structure can be more clearly understood by referring to FIG. 3.
  • Data base 27 has a first or top level 34 which contains a list of documents which might be useful in solving common user problems.
  • Acyclic graph data base 27 may contain links connecting lower levels to higher levels, as well as vice versa, so long as the overall structure precludes an endless loop. Thus, as in FIG. 3, node 39 may be connected to node 38, allowing a search to proceed from the fourth level back up to the second level.
  • Acyclic graph data base 27 contains two indices in top level node 34, specifically for communicating with other inquiry computers 10. These two indices are import index 40 and export index 42. These indices will be discussed in further detail below.
  • incident table register 23 includes an array of memory elements containing records of all user inquiries. Each time a user accesses inquiry computer 10 to enter a problem, the system logs and stores, in problem report register 29, the incident and the search steps performed by the user in search of the documented solution.
  • User table register 25 includes a list of all authorized users of inquiry computer 10. This user table register 25 contains such information as the user's name, company affiliation, address, phone number and other personal information related to the user's history or circumstances.
  • Inquiry link register 24 stores the mapping or link between the incident table register 23 and user table register 25.
  • inquiry link register 24 records the location in user table register 25 pointing to the user's identification and attaches to that pointer an address relating to the location in incident table register 23 corresponding to the incident.
  • This inquiry link provides important correspondence between the user and the user inquiry. Using this correspondence link, the system administrator is able to track the ongoing problems of each user and is able to use this information to organize solution documents to assist users with problems. This information also enables the user to be notified when new solution documents to a given incident are generated.
  • Solution link register 26 is similar in structure to inquiry link register 24, except that each record in incident table register 23 relating to the present inquiry is mapped to a document solution in acyclic graph data base 27. More than one inquiry may be mapped to a given document solution. This linkage or mapping between incident and solution allows the administrator to monitor the effectiveness of acyclic graph data base 27 and to perform updates and maintenance on specific documents based on usage.
  • Notify link register 28 records the mapping between user table register 25 and the incident solution in acyclic graph data base 27. This linkage maintains a list of all users who have an interest in a specific document, enabling notification of users when a change or update to the document is created.
  • Problem link register 29 connects the contents of incident table register 23 to corresponding solution documents in acyclic graph data base 27. This linkage is useful to the system administrator for showing which solution documents were retrieved for various incidents or problems posed to inquiry computer 10. One example of the use of this linkage would be if a non-optimal solution document was continually being retrieved for a recurring problem or incident. Recognizing this pattern from the data stored in problem link register 29, the data owner could take action to either improve the solution document or restructure acyclic graph paths 36 so that a more useful solution to the given problem is found.
  • the system administrator may choose to escalate or transfer these problem documents to an alternate location for solution.
  • this escalation would typically occur between secondary computer 43 (or lower order computer), which would create the originating problem document and primary system 41 (or other higher order computer).
  • Physical transfer of this unsolved problem document occurs by linking the problem document to export index 42.
  • processor 11 checks all of the documents linked to export index 42 and batch dumps these export documents to a transfer file which is reformatted and sent to the primary system 41 through local area network 19, or alternatively a WAN.
  • Modem 16 is a standard telephone modem which connects the processor to a T-1 phone line or other communications line.
  • the block connecting distributed users block 18 represents the connection of multiple users to processor 11 through a local network system such as EtherNet.
  • FIG. 5 a block diagram shows the steps of a method employing the secondary inquiry computer 43 of the present invention.
  • This method begins with the user making an inquiry of computer 43 in step 51.
  • the user is the purchaser of a new toaster who has a problem with burned toast and that computer 43 is being administered by a local representative of the toaster manufacturer.
  • the user makes inquiry into computer 43, either directly or more likely through the representative.
  • the incident (burned toast complaint) is logged into inquiry computer 43 through keyboard 15.
  • Information relating to the burned toast complaint is stored in incident table register 23 by processor 11.
  • processor 11 creates an inquiry record link and stores this link into inquiry link register 24.
  • step 55 the user (or support representative) begins the search of acyclic graph data base 27 for a document relating to the subject of burned toast.
  • the top level node 34 is first searched for subjects related to the problem, e.g., making toast.
  • the user will then follow path 36 to a second level node 38, where a document related to the incident might be found and read.
  • a document related to the incident might be found and read.
  • Such a document might be titled "What to Do When the Toaster Burns the Toast,” which suggests moving the toasting time indicator to a lighter setting.
  • the user can optionally print the document on printer 17.
  • the support representative is operating computer 43 on behalf of the user, the support representative will then notify the user of the solution in step 71.
  • step 56 a problem report is then generated and submitted to a local toaster expert (also employed by the toaster manufacturer) to review in step 59.
  • the toaster expert will attempt to locate a solution document within acyclic graph data base 27, and if a document is found, the structure of acyclic graph data base 27 may be modified to make the document more detectable. If no solution document is located, the toaster expert will use the problem report to try to generate a local solution to the incident in step 58. If a local solution is generated in step 58, the user is notified of the solution in step 71.
  • step 59 a decision may be made to escalate the problem document in step 57, and thereby create a new problem report on primary system 41, which is maintained by the toaster manufacturer.
  • the unsolved document on secondary system 43 is linked to export index 42 in step 63.
  • the accumulation of documents are batch-shipped to the primary system using standard electronic techniques in step 65. They are then converted into problem reports in primary system 41 and linked to that system's import index.
  • step 60 primary inquiry computer 41 receives a batch file of inquiry documents electronically. In step 61, it generates problem reports from these documents, and, in step 62, it stores these problem reports in import index 40. The receipt of these problem reports within index 40 of primary computer 41 is the equivalent of the inquiry step to secondary computer 43 which occurred in step 53. Within primary computer 41, a search is conducted for the solution document in step 66, in a manner similar to that which occurred in steps 55 and 56 of the secondary computer 43 flow chart shown in FIG. 5. The generation of the problem report within primary inquiry computer 41 is an important step in the overall process, since this problem report represents a linkage between the primary and secondary inquiry computers 41, 43.
  • the problem report records the nature of the original user inquiry, the steps traced in secondary inquiry computer 43 to resolve the inquiry prior to receipt by primary inquiry computer 41, and the identity of secondary inquiry computer 43, to which a solution document must be returned.
  • the data owner at primary inquiry computer 41 will either find or create a solution document which solves the problem report generated from the document created on secondary inquiry computer 43.
  • the solution document is shipped back to secondary inquiry computer via E-mail in step 70.
  • step 71 If no solution is found, it is possible for primary inquiry computer 41 to further escalate the problem report, assuming higher-order computers are available, in a manner similar to the escalation of the inquiry from secondary inquiry computer 43 in step 65. Once the solution document is received by secondary inquiry computer 43 in step 69, the solution can be communicated to the user in step 71.

Abstract

A distributed computer system and method for integrating call management to the retrieval of documents in response to user inquiries includes distributed computers, a processor connected to an incident table register, a user table register and an acyclic graph data base. The incident table register records and stores information related to the user inquiry, the user table stores information related to the user's identity and the acyclic graph data base stores a plurality of documents useful in addressing user inquiries. Within a top level of the acyclic graph data base are indices for importing and exporting documents to remote inquiry systems for the purpose of escalating inquiry problems to other systems having more specialized knowledge.

Description

BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention relates to heuristic learning application programs and more particularly to a method for entering user-specific problems and for heuristically retrieving documented solutions among multiple distributed computer management systems.
2. Description of the Background Art
A recurring problem among users of expert systems arises when multiple systems are employed in solving a common set of problems. Traditionally, expert systems are used to solve recurring problems by applying a set of either known or learned rules to a common set of problem characteristics. As new problems develop, responses to these problems are designed and installed on the system. Use of a single expert system is often cumbersome, particularly when users are located in remote sites. For example, a set of users in the United States would have difficulty sharing an expert system with users in Japan. This difficulty would be particularly acute if the two groups commonly faced diverging sets of problems and if the expert systems were programmed to respond in languages native to only one of the two groups. Furthermore, the telecommunications costs associated with the use by the Japanese of the U.S. installation (or vice versa) might be greater than the costs of installing a similar expert system in Japan.
The use of two separate systems, however, presents its own set of challenges. If the separate groups are organizationally related, it may be useful or important for the two expert systems to be able to cooperate and share selected information. One approach to the sharing of information is to synchronize the two data bases so that any solution developed in the Japanese data base, for instance, would correspondingly appear in the U.S. data base. However, due to the administrative costs of synchronizing data bases, and the fact that some solutions common to Japanese problems may not be required in the U.S. expert system data base, total synchronization is generally impractical. What is needed, then, is a way to selectively share information on an as-needed basis. This sharing of information would occur when one data base receives a problem for which it does not have a solution, and for which an associated data base is positioned to more efficiently solve. The first data base might then escalate the problem to the second data base which would solve the problem and then return a solution to the first. Such a system would be capable of selectively transferring problems, solutions, and useful information efficiently between data bases.
SUMMARY OF THE INVENTION
In accordance with the present invention, a system (9) and method for distributed call management and document retrieval is shown. The system (9) includes multiple expert or inquiry computers (10) connected using a networking scheme such as a modem or other communication link. Each inquiry computer (10) contains a processor (11), a plurality of specially configured registers, and a memory array comprising an acyclic graph data base (27). The computers (10) transfer problems to each other using a selective protocol which imports problems, identifies or creates document solutions and exports the solutions to the originating computer (10). According to the method of the present invention, a problem is logged into the inquiry computer (10) and a search for a solution document is undertaken. If no solution document is found, a problem report is then created and posted into a document. The document may be escalated to a remote inquiry computer by placing it in an export index (42), wherein the problem may be solved and a solution automatically sent electronically to the original user.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram showing distributed information system 9 in a preferred configuration having a primary inquiry computer 41 connected to a plurality of secondary and lower order computers;
FIG. 2 is a schematic diagram showing the preferred embodiment of inquiry computer 10 of the present invention;
FIG. 3 is a schematic diagram showing various document levels within acyclic graph data base 27 of the present invention;
FIG. 4 is a block diagram showing the contents of local area network 19 of the present invention;
FIG. 5 is a block diagram showing the steps implemented in secondary inquiry computer 43 of the present invention; and
FIG. 6 is a block diagram showing the steps implemented in primary inquiry computer 41 of the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENT
A preferred block diagram of the distributed information management and document retrieval system 9 of the present invention is shown in FIG. 1. Primary inquiry computer 41 is shown connected to a pair of secondary computer systems 43, which are in turn shown further connected to a plurality of tertiary inquiry computers 45. Under the structure of the present invention, tertiary inquiry computers 45 could further contain additional subsidiary inquiry computers. An alternative embodiment might contain networking schemes in which each of the inquiry computers 10 are connected to other inquiry computers. This connection to other computers may be in a ring network configuration, a star network configuration, or a combined network embodying both ring and star Characteristics, rather than in the modified tree structure of FIG. 1.
Referring now to FIG. 2, the preferred embodiment of inquiry computer 10 is shown. The preferred embodiment of inquiry computer 10 of the present invention is implemented on a general purpose, microprocessor based, computer such as a Sun Microsystems, IBM, or Hewlett-Packard computer. Inquiry computer 10 is maintained and operated by a system administrator who is at least somewhat knowledgeable about the subject matter being supported, as well as the computer hardware and associated software. The system administrator is able to change the structure and model of system 9 as needed. In addition to the system manager, there is at least one data owner who is knowledgeable about various solution documents, but who is not charged with operation or maintenance of inquiry computer 10 and its hardware components. Finally, there may also be support engineers, who may enter incidents, but do not enter solutions or maintain the system.
Inquiry computer 10 of the present invention is shown having processor 11 which is connected to keyboard 15 and display 13. Keyboard 15 and display 13 enable a user to interact with processor 11 by entering data and viewing the displayed contents of various memories. Also connected to processor 11 are printer 17, mass storage 21, and Local Area Network (LAN) 19. Printer 17 enables the user to make a permanent record of the various memory contents. Mass storage 21 is useful for long term storage and for maintaining large quantities of data. Local area network 19 enables the user to exchange data files and to interact with the memories and processors of other computer systems, as described in more detail below. Connection to an alternative Wide Area Network (WAN), is also possible, for serving a geographic area larger than that served on a traditional LAN 19.
Connected to inquiry computer 10 by data bus 20 are a plurality of special purpose memories and registers which are utilized by processor 11 in executing programming steps which are resident in program memory 22. Acyclic graph data base 27 contains a collection of documents designed to 5provide assistance to users who log inquiries into the system. As in a traditional expert system, the user logs onto computer 10 and presents a problem or incident to be solved by a document resident in the system. Rather than stating the problem as a series of answers to questions posed by the machine, as in the classical expert environment, the user searches a sequence of indices at various nodes in an acyclic graph. This acyclic graph data base 27 structure can be more clearly understood by referring to FIG. 3. Data base 27 has a first or top level 34 which contains a list of documents which might be useful in solving common user problems. In addition to the list of documents is a menu of sub-indices from which the user can choose to search an additional, more narrowly focused list of documents. If a sub-index from the menu is chosen, the user will move along path 36 to a second level node 38 containing a new list of documents and a new list of sub-indices. The search can be continued in this manner, descending through N levels until the desired document is found. Acyclic graph data base 27 may contain links connecting lower levels to higher levels, as well as vice versa, so long as the overall structure precludes an endless loop. Thus, as in FIG. 3, node 39 may be connected to node 38, allowing a search to proceed from the fourth level back up to the second level.
Acyclic graph data base 27 contains two indices in top level node 34, specifically for communicating with other inquiry computers 10. These two indices are import index 40 and export index 42. These indices will be discussed in further detail below.
Referring now to FIG. 2, incident table register 23, user table register 25, inquiry link register 24, solution link register 26, acyclic graph data base 27, notify link :register 28 and problem link register 29 are also connected to data bus 20. Incident table register 23 includes an array of memory elements containing records of all user inquiries. Each time a user accesses inquiry computer 10 to enter a problem, the system logs and stores, in problem report register 29, the incident and the search steps performed by the user in search of the documented solution. User table register 25 includes a list of all authorized users of inquiry computer 10. This user table register 25 contains such information as the user's name, company affiliation, address, phone number and other personal information related to the user's history or circumstances.
Inquiry link register 24 stores the mapping or link between the incident table register 23 and user table register 25. When the user logs onto computer 10, inquiry link register 24 records the location in user table register 25 pointing to the user's identification and attaches to that pointer an address relating to the location in incident table register 23 corresponding to the incident. This inquiry link provides important correspondence between the user and the user inquiry. Using this correspondence link, the system administrator is able to track the ongoing problems of each user and is able to use this information to organize solution documents to assist users with problems. This information also enables the user to be notified when new solution documents to a given incident are generated.
Solution link register 26 is similar in structure to inquiry link register 24, except that each record in incident table register 23 relating to the present inquiry is mapped to a document solution in acyclic graph data base 27. More than one inquiry may be mapped to a given document solution. This linkage or mapping between incident and solution allows the administrator to monitor the effectiveness of acyclic graph data base 27 and to perform updates and maintenance on specific documents based on usage.
Notify link register 28 records the mapping between user table register 25 and the incident solution in acyclic graph data base 27. This linkage maintains a list of all users who have an interest in a specific document, enabling notification of users when a change or update to the document is created. Problem link register 29 connects the contents of incident table register 23 to corresponding solution documents in acyclic graph data base 27. This linkage is useful to the system administrator for showing which solution documents were retrieved for various incidents or problems posed to inquiry computer 10. One example of the use of this linkage would be if a non-optimal solution document was continually being retrieved for a recurring problem or incident. Recognizing this pattern from the data stored in problem link register 29, the data owner could take action to either improve the solution document or restructure acyclic graph paths 36 so that a more useful solution to the given problem is found.
As problems arise that cannot be solved within the administrative structures of local inquiry computer 10, the system administrator may choose to escalate or transfer these problem documents to an alternate location for solution. In the preferred embodiment, this escalation would typically occur between secondary computer 43 (or lower order computer), which would create the originating problem document and primary system 41 (or other higher order computer). Physical transfer of this unsolved problem document occurs by linking the problem document to export index 42. Periodically, processor 11 checks all of the documents linked to export index 42 and batch dumps these export documents to a transfer file which is reformatted and sent to the primary system 41 through local area network 19, or alternatively a WAN.
Referring now to FIG. 4, a block diagram of local area network 19 is shown comprising modem 16 and other distributed users 18. Modem 16 is a standard telephone modem which connects the processor to a T-1 phone line or other communications line. The block connecting distributed users block 18 represents the connection of multiple users to processor 11 through a local network system such as EtherNet.
Referring now to FIG. 5, a block diagram shows the steps of a method employing the secondary inquiry computer 43 of the present invention. This method begins with the user making an inquiry of computer 43 in step 51. To illustrate the method, assume that the user is the purchaser of a new toaster who has a problem with burned toast and that computer 43 is being administered by a local representative of the toaster manufacturer. The user makes inquiry into computer 43, either directly or more likely through the representative. In step 53, the incident (burned toast complaint) is logged into inquiry computer 43 through keyboard 15. Information relating to the burned toast complaint is stored in incident table register 23 by processor 11. At the time of the initial inquiry, processor 11 creates an inquiry record link and stores this link into inquiry link register 24.
In step 55, the user (or support representative) begins the search of acyclic graph data base 27 for a document relating to the subject of burned toast. The top level node 34 is first searched for subjects related to the problem, e.g., making toast. The user will then follow path 36 to a second level node 38, where a document related to the incident might be found and read. Such a document might be titled "What to Do When the Toaster Burns the Toast," which suggests moving the toasting time indicator to a lighter setting. If this document solves the incident (step 56), the user can optionally print the document on printer 17. If the support representative is operating computer 43 on behalf of the user, the support representative will then notify the user of the solution in step 71. If in step 56, no solution document is found, a problem report is then generated and submitted to a local toaster expert (also employed by the toaster manufacturer) to review in step 59. The toaster expert will attempt to locate a solution document within acyclic graph data base 27, and if a document is found, the structure of acyclic graph data base 27 may be modified to make the document more detectable. If no solution document is located, the toaster expert will use the problem report to try to generate a local solution to the incident in step 58. If a local solution is generated in step 58, the user is notified of the solution in step 71. If no solution is reached in step 59, a decision may be made to escalate the problem document in step 57, and thereby create a new problem report on primary system 41, which is maintained by the toaster manufacturer. In order to create the problem report, the unsolved document on secondary system 43 is linked to export index 42 in step 63. The accumulation of documents are batch-shipped to the primary system using standard electronic techniques in step 65. They are then converted into problem reports in primary system 41 and linked to that system's import index.
Referring now to FIG. 6, the flow chart of steps is shown which are processed within primary inquiry computer 41. In step 60, primary inquiry computer 41 receives a batch file of inquiry documents electronically. In step 61, it generates problem reports from these documents, and, in step 62, it stores these problem reports in import index 40. The receipt of these problem reports within index 40 of primary computer 41 is the equivalent of the inquiry step to secondary computer 43 which occurred in step 53. Within primary computer 41, a search is conducted for the solution document in step 66, in a manner similar to that which occurred in steps 55 and 56 of the secondary computer 43 flow chart shown in FIG. 5. The generation of the problem report within primary inquiry computer 41 is an important step in the overall process, since this problem report represents a linkage between the primary and secondary inquiry computers 41, 43. The problem report records the nature of the original user inquiry, the steps traced in secondary inquiry computer 43 to resolve the inquiry prior to receipt by primary inquiry computer 41, and the identity of secondary inquiry computer 43, to which a solution document must be returned. In step 68 of FIG. 6, the data owner at primary inquiry computer 41 will either find or create a solution document which solves the problem report generated from the document created on secondary inquiry computer 43. The solution document is shipped back to secondary inquiry computer via E-mail in step 70.
If no solution is found, it is possible for primary inquiry computer 41 to further escalate the problem report, assuming higher-order computers are available, in a manner similar to the escalation of the inquiry from secondary inquiry computer 43 in step 65. Once the solution document is received by secondary inquiry computer 43 in step 69, the solution can be communicated to the user in step 71.

Claims (13)

We claim:
1. A method for retrieving a solution document in response to an inquiry from among a system of distributed data bases, the system having at least a first and a second computer, each computer having a data base of solution documents, the method comprising the steps of:
receiving at least one inquiry into the first computer, the inquiry having a subject;
searching the data base of the first computer for a solution document related to the subject of the inquiry;
responsive to finding at least one solution document in the data base of the first computer related to the subject of the inquiry, retrieving the solution document from the first computer;
responsive to finding no solution document in the data base of the first computer related to the subject of the inquiry, performing the steps of:
generating in the first computer, a document from at least one inquiry in the first computer for which no solution document was found, the document containing for each such inquiry the subject of the inquiry, and an identity of the computer in which the inquiry originated;
transmitting the document to the second computer;
extracting in the second computer any inquiries from the document;
for each extracted inquiry, searching the data base of the second computer for a solution document related to the subject of the inquiry;
responsive to finding at least one solution document in the data base of the second computer, retrieving the solution document from the second computer and exporting the solution document to the computer in which the inquiry originated; and,
responsive to finding no solution document in the data base of the second computer, notifying the computer in which the inquiry originated that no solution document has been found.
2. The method of claim 1 wherein the data base of the first computer comprises top, second and lower levels of nodes, each node containing at least one subject index and at least one document index, each subject index connected by a path to at least one lower level node, each document index containing a list of documents, and wherein the step of searching the data base of the first computer for a solution document further comprises the steps of:
identifying in the top node of the data base at least one document or subject index related to the subject of the inquiry;
following the path of a subject index related to the subject of the inquiry to a second level node;
identifying in the second level node at least one document or subject index related to the subject of the inquiry; and
following the paths of subject indices to other nodes until a document related to the subject of the inquiry is identified.
3. The method of claim 1, wherein the first computer has an export index as a data base node and the second computer has an import index as a data base node, wherein the step of transmitting the document to the second computer further comprises the steps of:
linking the document to the export node of the first computer; and
transmitting the document to the second computer;
and wherein the step of extracting any inquiries from the document further comprises the steps of:
storing the document in the import node of the second computer; and
generating a problem report for each inquiry in the document in the import node of the second computer, each problem reporting containing an extracted inquiry.
4. The method of claim 1, wherein the step of exporting the solution document from the second to the first computer further comprises the step of:
generating a new solution document in the second computer related to the subject of the inquiry.
5. The method of claim 1, further comprising the steps of:
responsive to finding no solution document in the data base of the second computer related to the subject of the inquiry, performing the steps of:
generating a document from at least one inquiry in the second computer for which no solution document was found, the document containing for each such inquiry the subject of the inquiry, and further containing an identity of the computer in which the inquiry originated;
transmitting the document to at least one additional computer containing a data base of solution documents;
extracting in the additional computer any inquiries from the document;
for each extracted inquiry, searching the data base of the additional computer for a solution document related to the subject of the inquiry;
responsive to finding at least one solution document in the data base of the additional computer, retrieving the solution document from the additional computer and exporting the solution document to the computer in which the inquiry originated; and,
responsive to finding no solution document in the data base of the additional computer, notifying the computer in which the inquiry originated that no solution document has been found.
6. The method of claim 1, wherein in each computer the data base of solution documents is organized in an acyclic graph.
7. The method of claim 1, wherein the computers are coupled by an electronic communications network, and where the steps of transmitting the document, and exporting the solution document further comprise the step of:
transmitting the document between the computers using the electronic communications network.
8. The method of claim 1, wherein the document generated in the first computer further contains for each inquiry at least one search step performed in searching the data base of the first computer for a solution document.
9. The method of claim 1, further comprising, responsive to finding no solution document in the data base of the first computer related to the subject of the inquiry, the step of:
generating a problem report describing the inquiry and at least one search step performed in searching the data base of the first computer for a solution document, wherein the document generated in the first computer is generated from the problem report.
10. A computer system for retrieving solution documents responsive to inquires from among a system of distributed computers, the system comprising:
a communications network coupled between the distributed computers;
a plurality of computers, each computer comprising:
a processor for receiving an inquiry;
an incident table coupled to the processor, the incident table storing the inquiry;
a document data base coupled to the processor and storing a plurality of solution documents, each solution document providing a solution to at least one inquiry in incident table;
an export index for storing at least one inquiry for communication to a second computer;
an import index for storing at least one inquiry received from another computer;
a search device coupled to the processor, and directed by the user for searching the document data base to retrieve a solution document providing a solution to an inquiry;
an escalation device, coupled to the search device, and placing an inquiry, for which no solution document is retrieved from the document data base by the search device, in the export index;
a communications device coupling the computer to the communications network, and coupled to the import and export indices, the communications device for transmitting at least one inquiry in the export index to another computer, and for receiving at least one inquiry from another computer and storing a received inquiry in the import index, wherein the search device searches the document data base for solutions to inquiries in the import index.
11. The system of claim 10, each computer further comprising:
a problem report table for storing a problem report including an inquiry received in the import index from a first computer, at least one search step used during a search of the document data base the first computer, and an identity of the first computer.
12. The system of claim 10, each computer further comprising:
a solution response device coupled to the communications device and the search device, to provide to the communications device a solution document retrieved by the search device in response to an inquiry in the import index, the inquiry received from a first computer, the communications device transmitting the solution document to the first computer.
13. The system of claim 10, wherein the database of each computer comprises a plurality of nodes, including a top node, at least one second level node, and a plurality of leaf nodes, each node including at least one solution document, the top and second level nodes each further including at least one subject index.
US07/965,165 1992-10-23 1992-10-23 Method and system for distributed information management and document retrieval Expired - Lifetime US5446883A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US07/965,165 US5446883A (en) 1992-10-23 1992-10-23 Method and system for distributed information management and document retrieval

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US07/965,165 US5446883A (en) 1992-10-23 1992-10-23 Method and system for distributed information management and document retrieval

Publications (1)

Publication Number Publication Date
US5446883A true US5446883A (en) 1995-08-29

Family

ID=25509552

Family Applications (1)

Application Number Title Priority Date Filing Date
US07/965,165 Expired - Lifetime US5446883A (en) 1992-10-23 1992-10-23 Method and system for distributed information management and document retrieval

Country Status (1)

Country Link
US (1) US5446883A (en)

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997019415A2 (en) * 1995-11-07 1997-05-29 Cadis, Inc. Search engine for remote object oriented database management system
US5729751A (en) * 1995-03-15 1998-03-17 Automated Legal Systems, Inc. Document assembly system with assembly logic
US5794237A (en) * 1995-11-13 1998-08-11 International Business Machines Corporation System and method for improving problem source identification in computer systems employing relevance feedback and statistical source ranking
US5802511A (en) * 1996-01-02 1998-09-01 Timeline, Inc. Data retrieval method and apparatus with multiple source capability
US5862322A (en) * 1994-03-14 1999-01-19 Dun & Bradstreet Software Services, Inc. Method and apparatus for facilitating customer service communications in a computing environment
US6023694A (en) * 1996-01-02 2000-02-08 Timeline, Inc. Data retrieval method and apparatus with multiple source capability
GB2343764A (en) * 1998-11-10 2000-05-17 Int Computers Ltd Data processing system for integrated business solution
US6105035A (en) * 1998-02-17 2000-08-15 Lucent Technologies, Inc. Method by which notions and constructs of an object oriented programming language can be implemented using a structured query language (SQL)
US20010029602A1 (en) * 2000-04-05 2001-10-11 Nec Corporation System development method, development-support system and storage medium storing program of same
US6336029B1 (en) 1996-12-02 2002-01-01 Chi Fai Ho Method and system for providing information in response to questions
US6393490B1 (en) * 1997-12-18 2002-05-21 Ian James Stiles Method and system for a programmatic feedback process for end-user support
US6411936B1 (en) 1999-02-05 2002-06-25 Nval Solutions, Inc. Enterprise value enhancement system and method
US6449355B1 (en) * 1997-12-19 2002-09-10 Mediaone Group, Inc. Method and system for providing assistance to users of a service
US20020138315A1 (en) * 2001-03-20 2002-09-26 Mineo Nozaki Technical support system
US6463437B1 (en) 1999-12-16 2002-10-08 General Electric Company Method and system for processing customer issues
US20020165701A1 (en) * 2000-12-08 2002-11-07 Jakob Lichtenberg Method of configuring a product
US6498921B1 (en) 1999-09-01 2002-12-24 Chi Fai Ho Method and system to answer a natural-language question
US6546380B1 (en) * 1997-09-24 2003-04-08 Unisys Corporation Method and apparatus for detecting an endless loop in a rules-based expert system
US20030088330A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha Method, system and computer program product for coping with the changes in hardware
US20030088451A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha Technical support system
US20030088641A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha Technical support system
US20030088454A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha System, method and computer program product for complaint report issue
US20030088590A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha Method, system and computer program product for providing backup data for use in studying claims
US20030088453A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha System, method and computer program product for rank assignment
US20030091025A1 (en) * 2001-11-15 2003-05-15 International Business Machines Corporation Scalable call management system
US6571240B1 (en) 2000-02-02 2003-05-27 Chi Fai Ho Information processing for searching categorizing information in a document based on a categorization hierarchy and extracted phrases
US20030115169A1 (en) * 2001-12-17 2003-06-19 Hongzhuan Ye System and method for management of transcribed documents
US20030115087A1 (en) * 2001-11-02 2003-06-19 Toshiba Tec Kabushiki Kaisha Technical support system
US20030135817A1 (en) * 2002-01-11 2003-07-17 G.E. Information Services, Inc. Automated method, system and software for storing data in a general format in a global network
US6625617B2 (en) 1996-01-02 2003-09-23 Timeline, Inc. Modularized data retrieval method and apparatus with multiple source capability
US6631382B1 (en) 1996-01-02 2003-10-07 Timeline, Inc. Data retrieval method and apparatus with multiple source capability
US20040083213A1 (en) * 2002-10-25 2004-04-29 Yuh-Cherng Wu Solution search
US20070136342A1 (en) * 2005-12-13 2007-06-14 Sap Ag Processing a user inquiry
US20140114645A1 (en) * 2012-10-23 2014-04-24 Ilan Kleinberger Information management systems and methods

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4714992A (en) * 1985-11-26 1987-12-22 International Business Machines Corporation Communication for version management in a distributed information service
US4876643A (en) * 1987-06-24 1989-10-24 Kabushiki Kaisha Toshiba Parallel searching system having a master processor for controlling plural slave processors for independently processing respective search requests
US5109486A (en) * 1989-01-06 1992-04-28 Motorola, Inc. Distributed computer system with network and resource status monitoring
US5179660A (en) * 1989-05-15 1993-01-12 International Business Machines Incorporated System for reducing communications overhead in distributed database transactions by serializing in order related requests into single transmission message and receiving transmission response
US5253361A (en) * 1989-09-15 1993-10-12 Emtek Health Care Systems, Inc. System for accessing a row of time-dependent data by referring to a composite index table indicating page locations of linked row labels
US5287537A (en) * 1985-11-15 1994-02-15 Data General Corporation Distributed processing system having plural computers each using identical retaining information to identify another computer for executing a received command
US5287505A (en) * 1988-03-17 1994-02-15 International Business Machines Corporation On-line problem management of remote data processing systems, using local problem determination procedures and a centralized database
US5293250A (en) * 1991-03-14 1994-03-08 Hitachi, Ltd. A system for notifying a destination terminal that electronic mail has reached a host computer
US5301314A (en) * 1991-08-05 1994-04-05 Answer Computer, Inc. Computer-aided customer support system with bubble-up
US5333317A (en) * 1989-12-22 1994-07-26 Bull Hn Information Systems Inc. Name resolution in a directory database

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5287537A (en) * 1985-11-15 1994-02-15 Data General Corporation Distributed processing system having plural computers each using identical retaining information to identify another computer for executing a received command
US4714992A (en) * 1985-11-26 1987-12-22 International Business Machines Corporation Communication for version management in a distributed information service
US4876643A (en) * 1987-06-24 1989-10-24 Kabushiki Kaisha Toshiba Parallel searching system having a master processor for controlling plural slave processors for independently processing respective search requests
US5287505A (en) * 1988-03-17 1994-02-15 International Business Machines Corporation On-line problem management of remote data processing systems, using local problem determination procedures and a centralized database
US5109486A (en) * 1989-01-06 1992-04-28 Motorola, Inc. Distributed computer system with network and resource status monitoring
US5179660A (en) * 1989-05-15 1993-01-12 International Business Machines Incorporated System for reducing communications overhead in distributed database transactions by serializing in order related requests into single transmission message and receiving transmission response
US5253361A (en) * 1989-09-15 1993-10-12 Emtek Health Care Systems, Inc. System for accessing a row of time-dependent data by referring to a composite index table indicating page locations of linked row labels
US5333317A (en) * 1989-12-22 1994-07-26 Bull Hn Information Systems Inc. Name resolution in a directory database
US5293250A (en) * 1991-03-14 1994-03-08 Hitachi, Ltd. A system for notifying a destination terminal that electronic mail has reached a host computer
US5301314A (en) * 1991-08-05 1994-04-05 Answer Computer, Inc. Computer-aided customer support system with bubble-up

Cited By (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5862322A (en) * 1994-03-14 1999-01-19 Dun & Bradstreet Software Services, Inc. Method and apparatus for facilitating customer service communications in a computing environment
US5729751A (en) * 1995-03-15 1998-03-17 Automated Legal Systems, Inc. Document assembly system with assembly logic
US6169992B1 (en) 1995-11-07 2001-01-02 Cadis Inc. Search engine for remote access to database management systems
WO1997019415A3 (en) * 1995-11-07 1997-07-31 Cadis Inc Search engine for remote object oriented database management system
WO1997019415A2 (en) * 1995-11-07 1997-05-29 Cadis, Inc. Search engine for remote object oriented database management system
US5794237A (en) * 1995-11-13 1998-08-11 International Business Machines Corporation System and method for improving problem source identification in computer systems employing relevance feedback and statistical source ranking
US6631382B1 (en) 1996-01-02 2003-10-07 Timeline, Inc. Data retrieval method and apparatus with multiple source capability
US5802511A (en) * 1996-01-02 1998-09-01 Timeline, Inc. Data retrieval method and apparatus with multiple source capability
US6625617B2 (en) 1996-01-02 2003-09-23 Timeline, Inc. Modularized data retrieval method and apparatus with multiple source capability
US6026392A (en) * 1996-01-02 2000-02-15 Timeline, Inc. Data retrieval method and apparatus with multiple source capability
US6023694A (en) * 1996-01-02 2000-02-08 Timeline, Inc. Data retrieval method and apparatus with multiple source capability
US6480698B2 (en) 1996-12-02 2002-11-12 Chi Fai Ho Learning method and system based on questioning
US6336029B1 (en) 1996-12-02 2002-01-01 Chi Fai Ho Method and system for providing information in response to questions
US6865370B2 (en) 1996-12-02 2005-03-08 Mindfabric, Inc. Learning method and system based on questioning
US6501937B1 (en) 1996-12-02 2002-12-31 Chi Fai Ho Learning method and system based on questioning
US6546380B1 (en) * 1997-09-24 2003-04-08 Unisys Corporation Method and apparatus for detecting an endless loop in a rules-based expert system
US6393490B1 (en) * 1997-12-18 2002-05-21 Ian James Stiles Method and system for a programmatic feedback process for end-user support
US6449355B1 (en) * 1997-12-19 2002-09-10 Mediaone Group, Inc. Method and system for providing assistance to users of a service
US6105035A (en) * 1998-02-17 2000-08-15 Lucent Technologies, Inc. Method by which notions and constructs of an object oriented programming language can be implemented using a structured query language (SQL)
GB2343764A (en) * 1998-11-10 2000-05-17 Int Computers Ltd Data processing system for integrated business solution
US6411936B1 (en) 1999-02-05 2002-06-25 Nval Solutions, Inc. Enterprise value enhancement system and method
US6498921B1 (en) 1999-09-01 2002-12-24 Chi Fai Ho Method and system to answer a natural-language question
US6463437B1 (en) 1999-12-16 2002-10-08 General Electric Company Method and system for processing customer issues
US6571240B1 (en) 2000-02-02 2003-05-27 Chi Fai Ho Information processing for searching categorizing information in a document based on a categorization hierarchy and extracted phrases
US20010029602A1 (en) * 2000-04-05 2001-10-11 Nec Corporation System development method, development-support system and storage medium storing program of same
US7584079B2 (en) * 2000-12-08 2009-09-01 Configit Software A/S Method of configuring a product
US20020165701A1 (en) * 2000-12-08 2002-11-07 Jakob Lichtenberg Method of configuring a product
US20020138315A1 (en) * 2001-03-20 2002-09-26 Mineo Nozaki Technical support system
US20030088454A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha System, method and computer program product for complaint report issue
US20030088590A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha Method, system and computer program product for providing backup data for use in studying claims
US20030088453A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha System, method and computer program product for rank assignment
US20030088641A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha Technical support system
US20030088451A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha Technical support system
US20030115087A1 (en) * 2001-11-02 2003-06-19 Toshiba Tec Kabushiki Kaisha Technical support system
US7024411B2 (en) 2001-11-02 2006-04-04 Toshiba Tec Kabushiki Kaisha Method, system and computer program product for providing backup data for use in studying claims
US20030088330A1 (en) * 2001-11-02 2003-05-08 Toshiba Tec Kabushiki Kaisha Method, system and computer program product for coping with the changes in hardware
US20030091025A1 (en) * 2001-11-15 2003-05-15 International Business Machines Corporation Scalable call management system
US7058046B2 (en) 2001-11-15 2006-06-06 International Business Machines Corporation Scalable call management system
US20030115169A1 (en) * 2001-12-17 2003-06-19 Hongzhuan Ye System and method for management of transcribed documents
US20030135817A1 (en) * 2002-01-11 2003-07-17 G.E. Information Services, Inc. Automated method, system and software for storing data in a general format in a global network
US20040083213A1 (en) * 2002-10-25 2004-04-29 Yuh-Cherng Wu Solution search
US20070136342A1 (en) * 2005-12-13 2007-06-14 Sap Ag Processing a user inquiry
US20140114645A1 (en) * 2012-10-23 2014-04-24 Ilan Kleinberger Information management systems and methods
US9424341B2 (en) * 2012-10-23 2016-08-23 Ca, Inc. Information management systems and methods

Similar Documents

Publication Publication Date Title
US5446883A (en) Method and system for distributed information management and document retrieval
US5404518A (en) System for building a user-determined database of solution documents from queries that fail within it and from the search steps that do provide a solution
US6516337B1 (en) Sending to a central indexing site meta data or signatures from objects on a computer network
USRE42051E1 (en) Peer-to-peer automated anonymous asynchronous file sharing
CN101334792B (en) Personalized service recommendation system and method
US7233940B2 (en) System for processing at least partially structured data
Marcus An experimental comparison of the effectiveness of computers and humans as search intermediaries
Bowman et al. Harvest: A scalable, customizable discovery and access system
US6006217A (en) Technique for providing enhanced relevance information for documents retrieved in a multi database search
CN100504861C (en) Method and system for generation of meaningful names in flattened hierarchical structures
US7502810B2 (en) Tagging of facet elements in a facet tree
US6983282B2 (en) Computer method and apparatus for collecting people and organization information from Web sites
CA2319501A1 (en) Navigating network resources using metadata
CN105989426A (en) Customer relationship management system facing standard information service industry
US20090019021A1 (en) Method and apparatus for creating an index of network data for a set of messages
CN101171583B (en) Automatic intranet service publishes and service access
EP1190475A1 (en) User support system and method
Norgard et al. The online catalog: From technical services to access service
Postel et al. White Pages Meeting Report
Rosen E-mail Classification in the Haystack Framework
Boisvert et al. Digital software and data repositories for support of scientific computing
Cotter DoD Gateway Information System
Maa et al. Lyceum: A multi-protocol digital library gateway
Kitaoka Establishing Ada repositories for reuse
Konrad USE OF THE LBLSTAFF DATABASE

Legal Events

Date Code Title Description
AS Assignment

Owner name: ANSWER COMPUTER, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST.;ASSIGNORS:KIRKBRIDE, LOUISE;EISEMANN, TODD;REEL/FRAME:006375/0079

Effective date: 19921214

AS Assignment

Owner name: ANSWER SYSTEMS, INC., CALIFORNIA

Free format text: CHANGE OF NAME;ASSIGNOR:ANSWER COMPUTER, INC.;REEL/FRAME:007482/0112

Effective date: 19950301

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FEPP Fee payment procedure

Free format text: PAT HLDR NO LONGER CLAIMS SMALL ENT STAT AS SMALL BUSINESS (ORIGINAL EVENT CODE: LSM2); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: PLATINUM TECHNOLOGY IP, INC., ILLINOIS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FREEDMAN, LARRY S.;REEL/FRAME:009662/0513

Effective date: 19981221

FPAY Fee payment

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

REMI Maintenance fee reminder mailed
FPAY Fee payment

Year of fee payment: 8

SULP Surcharge for late payment

Year of fee payment: 7

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: COMPUTER ASSOCIATES THINK, INC., NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PLATINUM TECHNOLOGY IP, INC.;REEL/FRAME:017344/0789

Effective date: 20060310

FPAY Fee payment

Year of fee payment: 12

AS Assignment

Owner name: PLATINUM TECHNOLOGY, INC., NEW YORK

Free format text: MERGER;ASSIGNOR:ANSWER SYSTEMS, INC.;REEL/FRAME:023556/0441

Effective date: 19971223

Owner name: PLATINUM TECHNOLOGY IP, INC., NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PLATINUM TECHNOLOGY, INC.;REEL/FRAME:023556/0445

Effective date: 19981221

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: CA, INC., NEW YORK

Free format text: MERGER;ASSIGNOR:COMPUTER ASSOCIATES THINK, INC.;REEL/FRAME:032113/0267

Effective date: 20120327