Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
2000-05-26
2004-04-06
Breene, John (Department: 2177)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000
Reexamination Certificate
active
06718334
ABSTRACT:
COPYRIGHT NOTICE
A portion of the disclosure of this patent document contains material to which a claim for copyright is made. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but reserves all other copyright rights whatsoever.
STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
Not applicable.
MICROFICHE APPENDIX
A portion of the disclosure hereof is embodied within a Microfiche Appendix comprising a total of three (3) microfiche sheets having a total of one hundred forty-five (145) frames.
FIELD OF THE INVENTION
This invention relates, generally, to computer implemented document and image management systems; and, more particularly, to such a system that operates under the Microsoft Windows®
1
shell environment and which, further, is cross-platform capable and application independent. With respect to the document or image sought to be managed, the invention, thus, operates independently of both the computer platform and the application software therein operating that was used to create the document or image.
1
Windows® is a registered trademark of the Microsoft Corporation, Redmond, Wash.
BACKGROUND OF THE INVENTION
A computer implemented document and image management system (hereinafter sometimes, “DIM system”) aids in managing information created by a user's legacy software application or applications, further empowering the legacy application by the process of “image enabling.” The terms “legacy software,” “legacy application,” “application,” and “application software,” as used herein, connotes software running either on a single computer device, or, alternatively, over a network of interconnected computers, that utilizes one or more database(s) to collect and store, on computer media, data that has been provided by the user thereof through operation of a computer and its software.
The legacy software often provides the user with an efficient interface for collecting and processing the user's data. Examples of such data might be image or graphic-based data; spreadsheet data; textual data; data acquired through a process of data acquisition (as in a manufacturing process or medical procedure), the representation of which approximates or models a physical manifestation, composition, process, or the like; or any combination(s) thereof. Many different legacy applications may operate, and inter-operate, on the user's computer and/or network.
In most cases, such information is merely created and stored by such legacy software, but is not managed thereby. The purpose, then, of a document and image management system is to provide the user with a way to collect, process, image, and manage all such information as may have been created by the legacy applications, but which the legacy applications do not otherwise manage, or do not otherwise manage with sufficient functionality to meet the computer user's needs.
For example, a user may wish to process, store, and manage information created by various individual and independent software into a common form. Such functionality is not typically provided by the legacy application. The user's desire for such control and management of data, then, defines the parameters for development of a DIM system.
The user may wish to use DIM system functionality through his legacy business application interface. In this regard, the DIM system must somehow be integrated into the user's legacy application(s). Because the legacy application(s) may run on any computer platform, integration of the features discussed above becomes very complicated.
The problem identified has been further compounded by the increasing and now widespread use of networks of computers, wherein it is common that individual computers in the network comprise varying hardware, operating system, and legacy application architectures. Such architectures, which are generally referred to herein as “platforms,” often require that data be processed, stored, and managed in formats that may not be compatible with formats required by another platform operating in a remote, but interconnected, portion of the computer network.
An effective DIM system, then, should be capable of processing and managing all such data, regardless of the type of data, the legacy application that created the data, or the platform under which the data was created. Prior DIM systems have sought to perform such integration according to three primary models.
The first model is integration of data through software directed “calls,” or redirection of the legacy application's programming logic and resulting data flow, to and through an application programming interface, or “API.” In such model, the computer programmer places API calls within the user's legacy application requiring DIM system functionality, so that when the legacy application executes to the point of call, the DIM system function will be loaded and executed.
Such programming model is undesirable, however, because the programmer must analyze each of the user's legacy applications requiring DIM system functionality, and understand such application(s) well enough to implement API calls in the correct logical sequence. This implementation must be performed for each legacy application. Such programming is time consuming, and, thereby, expensive. Program support is difficult to maintain because, should an application programming change occur that changes or affects the position of a character in a DIM required field, the API no longer accomplishes an accurate index transfer; thus, a further programming change is required to return functionality to the DIM system. This method is not platform independent and, typically, is not guaranteed to work for all of the user's legacy applications.
The second model is integration of data through a process that often is called “screen-scraping.” According to this model, screen-scraping software is provided td monitor the user's keystrokes effectuated upon the computer. Typically, a “hot-key” combination is programmed to activate the screen-scraping software. When the user presses the “hot-key” combination, the screen-scraping software identifies a display location for the information, as upon the computer's monitor or the like, according to a display matrix calculation. The screen-scraping software provides index data that is, in turn, passed to the DIM system.
According to the typical implementation of this model, however, the screen scraping software operates only on a “host-and-client” based platform, as in a network-based host machine according to the AS/400 architecture, or the like. The screen-scraping software, then, operates upon the AS/400 platform wherein the legacy application is running. This is disadvantageous in that the screen-scraping application, generally, is activated from the client machine. This implementation, therefore, usually is slow because the host computer must process the data, often while the client computer is forced to stand idle, and then send the result back to the client computer. This model is further disadvantageous because it is not, typically, guaranteed to work for all applications, and does not function within a “server-and-client” based architecture. Additionally, should the user change platforms or operating systems, the ability to “screen-scrape” is lost, along with the programming investment incurred.
The third model is integration of data through dynamic data exchange (“DDE”) or object linking and embedding “OLE” automation; i.e., the exchange of information between software applications that have been programmed according to uniform and common data exchange protocols, typically in the Microsoft Windows® environment. In accordance with this model, only those applications supporting DDE or OLE may be enabled to provide DIM system functionality. This model does not work on all platforms. Even where the model is effective, programming changes often are required on
Breene John
Inter American Data, L.L.C.
Myers & Kaplan LLC
Wassum Luke S
LandOfFree
Computer implemented document and image management system does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Computer implemented document and image management system, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Computer implemented document and image management system will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3242054