Method for preventing improper correction of a database during an updating process

[0002] This non-provisional application claims priority from provisional application No. 60/362,310, filed on Mar. 8, 2002.

[0003] This invention relates generally to methods for updating information contained in a first database, by reference to information contained in a second database, through the use of an early warning system that limits the risk of improper correction.

[0004] There are various circumstances in which it is appropriate to correct information in a first database, by reference to information contained in a second database. For example, the Postal Service and other organizations that maintain address databases have a regular need to update those address databases so that they contain accurate information. An updating process, in this regard, serves to improve the accuracy of the address database by removing or correcting inaccurate addresses.

[0005] In the past, the updating of an address database was accomplished by running that database through a coding engine, whereby the entries in the address database would be compared to entries in a reference database, containing all possible addresses within a particular region. In the event that the Coding engine determined that a checked address matched one contained in the reference database, the coding engine would leave the checked address unchanged. However, if the checked address did not match the standard addresses contained in the reference database, the coding engine would delete or change the checked address.

[0006] However, the reference database utilized by the coding engine will often lag behind changes that occur in the particular region that they cover. For example, newly added streets may not be reflected in the reference database, with the result that a proper new address in an address database is erroneously recognized as being incorrect, and is either deleted or changed.

[0007] A need therefore existed for a method for updating and correcting address databases, that permits a coding engine to take into account recent address-related changes that are not contained in the reference database. In particular, a need existed for an updating and correcting method that relies on the use of an update file that acts as an Early Warning System, limiting the occurrence of improper changes or deletions during the updating process. The present invention satisfies these needs and provides other, related, advantages.

[0008] It is an object of the present invention to provide a method for updating and correcting address databases, that permits a coding engine to take into account recent address-related changes that are not contained in a reference database.

[0009] It is a further object of the present invention to provide a method for updating and correcting address databases, that relies on the use of an update file that acts as an early warning system, limiting the occurrence of improper changes or deletions during the updating process.

[0010] It is a yet further object of the present invention to provide a method for updating and correcting information contained in a first database, by comparing the information therein to information contained in a reference database, and utilizing an early warning system that incorporates more recent information than that contained in the reference database and that screens information in the first database that has been flagged for change or deletion.

[0011] The method of the present invention may be embodied in a computer system executing program instructions for carrying out the steps of the method, and further in a computer program product comprising media for storing the program instructions.

[0012] In accordance with one embodiment of the present invention, a method for updating information contained in a database is disclosed. The method comprises comprising the steps of: providing a first database containing a plurality of data entries; providing a reference database containing a plurality of reference data entries; providing an update file containing data that is supplemental to that contained in the reference database; comparing the data entries in the first database to the reference data entries in the reference database; identifying a suspect data entry among the data entries in the first database by locating one the data entry that does not match any of the reference data entries in the reference database; comparing the suspect data entry to information contained in the update file; in the event that the suspect data entry matches information contained in the update file, leaving the suspect data entry in the first database in an unchanged condition in the first database; and in the event that the suspect data entry does not match information contained in the update file, one of deleting the suspect data entry from the first database and correcting the data entry in the first database to match the information in the update file.

[0013] In accordance with another embodiment of the present invention, a method for updating information contained in a database comprising the steps of: providing a first database containing a plurality of data entries; wherein the first database is an address database; providing a reference database containing a plurality of reference data entries; wherein the reference database is a coding engine; providing an update file containing data that is supplemental to that contained in the reference database; comparing the data entries in the first database to the reference data entries in the reference database; identifying a suspect data entry among the data entries in the first database by locating one the data entry that does not match any of the reference data entries in the reference database; comparing the suspect data entry to information contained in the update file; in the event that the suspect data entry matches information contained in the update file, leaving the suspect data entry in the first database in an unchanged condition in the first database; in the event that the suspect data entry does not match information contained in the update file, one of deleting the suspect data entry from the first database and correcting the data entry in the first database to match the information in the update file; and periodically updating the update file; wherein the step of periodically updating the update file further comprises the step of removing from the update file information that has an age in excess of a specified period of time.

[0014] In accordance with yet another embodiment of the present invention, there is disclosed a computer program product comprising signal-bearing media for execution within a computer system that includes a memory for storing program instructions and data coupled to a processor for executing the program instructions, and a data store for storing a first database, a reference database and an update file, and wherein the program instructions comprising program instructions for: comparing data entries in the first database to reference data entries in the reference database; identifying a suspect data entry among the data entries in the first database by locating one the data entry that does not match any of the reference data entries in the reference database; comparing the suspect data entry to information contained in the update file; in the event that the suspect data entry matches information contained in the update file, leaving the suspect data entry in the first database in an unchanged condition in the first database; and in the event that the suspect data entry does not match information contained in the update file, one of deleting the suspect data entry from the first database and correcting the data entry in the first database to match the information in the update file.

[0015] FIG. 1 is an example of a data contained in an update file.

[0016] FIG. 2 is a flow chart, illustrating a method consistent with the present invention.

[0017] FIG. 3 is a block diagram depicting a computer system in which the method of the present invention is practiced.

[0018] This invention is concerned with the updating of information contained in a first database, through the use of a coding engine (sometimes referred to herein as a “ZIP+4 Engine”). In a preferred embodiment, the first database is an address database. Each data entry in an address database reflects an individual address. This information can include ZIP code information, a street name, a street number, a pre-directional address element (e.g., “N” for north, “E” for east), a street suffix (e.g., “AVE” for avenue, “LN” for lane, etc.), and a post-directional address element (e.g., “SE” for southeast). It should be apparent that data entries could also comprise Post Office box addresses, commercial mail receiving agency addresses, or the like.

[0019] Upon inputting of the address database into a coding engine, the coding engine will check the data entries contained therein against a reference database. The reference database will contain all possible addresses within a particular region, preferably with the same level of specificity as contained in the address database. Of course, the particular reference database used by a coding engine to update an address database should include all possible addresses within the area covered by the address database.

[0020] The coding engine will further utilize an update file, referred to herein as either an update file or an early warning system. The update file contains information of the same general type as that contained in the reference database; however, the information contained in the update file contains particular information that has been generated since the last updating of the reference database. Referring now to FIG. 1, it contains an example of an excerpt from an update file. As reflected in this excerpt, the update file may contain information at a more general level than the address database or reference file. Thus, as shown in FIG. 1, the update file contains a listing of street names, including ZIP code, pre-directional element, post-directional element, and suffix. However, individual street addresses are not required to be included, though of course it would be possible to include them if desired.

[0021] For example, the reference database may reflect that, in a particular geographic area, there is an Oak Street but no Oak Drive. Subsequent to the last updating of the reference database, an Oak Drive is added to that geographic area. In this instance, the addition of Oak Drive (including all then known street address associated therewith) will be reflected in the update file.

[0022] Referring now to FIG. 2, the operation of an updating method consistent with the present invention is shown. A street address is presented to a coding/ZIP+4 engine. The coding engine will compare the presented address with the content of a reference database. If the particular address is present in the reference database exactly as presented, the coding engine will not change the address, and the coding engine will then examine the next address.

[0023] On the other hand, if the particular address is not present in the reference database exactly as presently but needs to be changed, the coding engine will present the address to the early warning system. If the address (or at a minimum the portion of the address contained in the update file) is present in the early warning system, the coding engine will not change it, and it will then examine the next address. If the address is not present in the early warning system it will change the address to conform it to the information contained in the reference database or, optionally, will delete it.

[0024] Continuing with the example provided above, if the address provided to the coding engine is an Oak Drive address, the coding engine will compare that address to the reference database. Because Oak Drive was added subsequent to the most recent updating of the reference database, a comparison with the reference database will indicate that the address is not correct. However, instead of changing the address as a prior art coding engine would, the Oak Drive address will be presented to the update file. That file will reflect the addition of this new address, and, as a result, the coding engine is warned not to change or delete it.

[0025] It will be desired to keep the update file current, through a periodic updating process. For example, the update file could be updated weekly, monthly, or at any other desired interval. As part of the process of updating the update file, it will be desired to remove older information contained therein. At a minimum, as the reference database is itself revised, it will be desired to purge the update file of all information that predates the date of such revision.

[0026] While the example of a coding engine utilized to update address databases has been presented, it should be understood that the invention disclosed has broader application. Specifically, it is intended to encompass any method by which information of any kind that is contained in a first database is updated by comparing it to information contained in a second database, wherein an update file is also utilized to prevent improper corrections or deletions relating to new information that post-dates the last revision of the reference database. For example, such a coding engine could be utilized to update a database of amino acid sequences, DNA sequences, or the like.

[0027] Referring now to FIG. 3, there is depicted a computer system 30 within which a method may be performed via the execution of program instructions forming a computer program product in accordance with an embodiment of the present invention. The method may employ program instructions located within a memory 39 of a workstation computer 34 and executed by a central processing unit 38 (CPU) and the databases of the present invention may be located entirely within a storage media 33A and memory 39. Alternatively, workstation computer 34 may be coupled via a network 31 connection for coupling workstation computer 34 to a network such as a local-area network (LAN), wide-area network (WAN) or the Internet. In a network implementation, the data store and/or program instructions for implementing the methods of the present invention may be located within a database server 32 coupled to a storage media 33B.

[0028] The method of the present invention provides database update tracking by an end-user for execution on workstation computer 14 or access to the database and execution of the program via the Internet or other network. Other combinations such as local-hosted program with a remote database, local database with remote-hosted program are possible and should be understood to be variations in accordance with embodiments of the present invention.

[0029] While the invention has been particularly shown and described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that the foregoing and other changes in form and details may be made therein without departing from the spirit and scope of the invention.