Attribute portion based document retrieval system with system query language interface

• US 5,600,833 A
• Filed: 03/24/1995
• Issued: 02/04/1997
• Est. Priority Date: 09/17/1993
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Digital Equipment Corporation (HP Inc.)
• Inventors: Brown, Andrew D., Lucas, Peter, Senn, Jeffrey A.
• Primary Examiner(s): KIM, KENNETH S
• Application Number:
  US08/410,593
• Time in Patent Office: 683 Days
• Field of Search: 395/500, 395/600, 395/700
• US Class Current: 1/1
• CPC Class Codes: G06F 16/3332 Query translation
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

A system for retrieval of documents in a client-server environment is disclosed. The system provides compatibility between an attribute based document display system and diverse query languages within remote document repositories. The system includes a local process running on a client module, and a remote process running within each document repository. Each remote process is designed for the particular model of computer used for the server. Each remote process executes a System Query Language (SQL) used by a particular database program running on the server. A particular server may have several database programs implemented thereon, and each database program has a dedicated remote process, where the remote process is matched to the particular database program. The local process on the user'"'"'s workstation launches inquiries in a first format on the network. Each remote process receiving an inquiry translates the received inquiry into the System Query Language required by its server and its database program. When the database program returns a response to the System Query language inquiry, the remote process translates the response into the first format, and returns the response to the local process by transmitting a reply over the network.

Claims

1. A document retrieval system, comprising:

one or more documents, each of said one or more documents having one or more attribute components, each of said one or more attribute components having a name portion and a value portion;

a user system having a display device and a cache, said cache for local storage of at least one attribute component of said documents;

one or more repositories, coupled with said user system such that messages may be sent between said one or more repositories and said user system, for permanent storage of said documents, each of said one or more repositories having a particular database program, and each of said one or more repositories having a system query language (SQL), said particular database program responsive to said system query language;

a client module on said user system, coupled with said one or more repositories, for issuing document requests to said one or more repositories, said document requests having a first format, each one of said document requests in said first format including a set of one or more attribute component name portions; and

a repository interface within each of said one or more repositories, for receiving and responding to said document requests, and for translating each said attribute component name portion in said document requests into one or more calls to functions defined in said system query language.

2. The system as in claim 1,

said repository interface having a database system query language library, containing said functions defined in said system query language.

3. The system as in claim 2, further comprising:

said client module on said user system coupled with said repository interface through a local area network (LAN).

4. The system as in claim 2, further comprising:

said repository interface contained within a repository node, said repository node having a disc drive coupled with said repository interface.

5. The system as in claim 4, further comprising:

said functions defined in said system query language returning information stored on said disc drive coupled with said repository interface; and

an attribute component interpreter process, responsive to said document requests and said calls to functions defined in said system query language returning said information, for sending a response to said client module on said user system, said response including said returned information.

6. The system as in claim 5, said attribute component interpreter process further formatting said response to said document requests into a set of returned attribute components, each one of said set of returned attribute components having a name portion and a value portion, each said name portion equal to one of said set of one or more attribute component name portions in one of said document requests, and each said value portion equal to some portion of said information stored on said disk drive returned by said calls to functions defined in said system query language.

7. The system as in claim 1, further comprising:

a script engine coupled with said client module in said user system;

one of said value portions in said returned attribute components equal to a portion of script language, capable of being interpreted by said script engine.

8. A document retrieval system, comprising:

a document having a plurality of attribute components, each of said plurality of attribute components having a name portion and a value portion;

a user system having a display device and a cache, said cache for local storage of at least one of said plurality of attribute components in said document;

a repository, coupled with said user system such that messages may be sent between said repository and said user system, for permanent storage of said document, said repository having a database program, and having a system query language (SQL), said data base program responsive to said system query language;

to a client module on said user system, coupled with said repository, for issuing a document request to said repository, said document request including a set of attribute component name portions, each one of said set of attribute component name portions equal to one of said name portions of said plurality of attribute components in said document, said set of attribute component name portions corresponding to a subset of said plurality of attribute components in said document; and

a repository interface within each of said one or more repositories, for receiving said document request, and for translating said set of attribute component name portions in said document request into one or more calls to functions defined in said system query language.

9. The system as in claim 8, said repository interface having a database system query language library, containing said functions defined in said system query language.

10. The system as in claim 9, further comprising:

said client module on said user system coupled with said repository interface through a local area network (LAN).

11. The system as in claim 9, further comprising:

said repository interface contained within a repository node, said repository node having a disc drive coupled with said repository interface.

12. The system as in claim 11, further comprising:

said calls to functions defined in said system query language returning information stored on said disc drive coupled with said repository interface; and

an attribute component interpreter process, responsive to said document request and said calls to functions defined in said system query language returning said information, for sending a response to said client module on said user system, said response including said returned information.

13. The system as in claim 12, said attribute component interpreter process further formatting said response to said document request into a set of returned attribute components, each one of said set of returned attribute components having a name portion and a value portion, each said name portion equal to one of said set of attribute name portions in said document request, and each said value portion equal to some portion of said information stored on said disk drive returned by said calls to functions defined in said system query language.

14. The system as in claim 8, further comprising:

a script engine coupled with said client module in said user system;

one of said value portions in said returned attribute components equal to a portion of script language, capable of being interpreted by said script engine.