JP4634011B2 - Image database transfer method and system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an image database transfer method and system for transferring necessary image data from one image database system to another image database system between different image databases.
[0002]
[Prior art]
Various images are digitized and registered in a database. For example, seals, signatures, and various image contents are stored in an electronic database. Such electronic image database systems are provided by various manufacturers. In some cases, image data is transferred between such image database systems.
[0003]
For example, various manufacturers provide electronic seal database systems for financial services. However, integration of different financial institutions has continued, and customer's seal data that has been electronically managed can be transferred between different systems after integration. It is necessary to transfer and transfer to each other.
[0004]
Such data transfer between systems can be easily copied if image data and management information are shared between systems. However, in the management / operation of seals, each manufacturer and each user often uses a unique management format and operation. If each manufacturer cannot disclose information in order to protect its own technology (such as an image data compression method), data cannot be simply copied from the A system to the B system.
[0005]
For example, the seal data management method in the financial business is that a database section is constructed for each store number, and a plurality of seal data is managed under the account number of the customer managed under that store number. Generally, the combination is used as a key to make it unique.
[0006]
As described above, in the financial business, the link between the store number-account number and customer seal data is universal for all users and manufacturers, but the management format of the information attached to the account and the information attached to the seal data is different. There are often differences between systems.
[0007]
In addition, account numbers that have existed uniquely in individual systems until then may be duplicated by integration by financial institutions, and the uniqueness of account numbers may be lost.
[0008]
In such a case, it is easy to integrate a small database, and in the merger of small financial institutions, the electronic seal stamp database system that has been introduced to each other has been unified into one manufacturer.
[0009]
[Problems to be solved by the invention]
However, in the case of a merger of a large-scale financial institution, it is required to introduce the electronic seal stamp database system of manufacturers that are held together. This is because a large amount of labor is required to unify the operations of the stamp business that financial institutions have independently implemented, and the labor to unify the vast amounts of customer data held by each other. .
[0010]
Therefore, it is urgent to organize customer data due to the merger of stores resulting from the merger, and once the store consolidation is completed, it becomes a procedure to unify the system. Data must be exchanged between manufacturers.
[0011]
For this reason, the method of manually registering seal data in each system based on a unique account number and seal slip newly allocated by the user requires a lot of labor and time, and it takes time to transfer the database. There is also a problem that it takes a long time and there is a possibility that an error in registration may occur.
[0012]
Accordingly, it is an object of the present invention to provide an image database transfer method and system for automating transfer of image files between different image database systems.
[0013]
Another object of the present invention is to provide an image database transfer method and system for automating transfer of image files between image database systems of different management formats even when the management formats are not disclosed mutually. There is.
[0014]
Another object of the present invention is to provide an image database transfer method and system for transferring image files between image database systems of different management formats in a short time even if the management formats are not disclosed mutually. Is to provide.
[0015]
[Means for Solving the Problems]
  The present invention provides a second image database that stores a second image file configured in a second format from a first image database system that stores a first image file configured in a first format. In the image database transfer method for transferring the first image file to the system, the step of extracting the first image file to be transferred from the first image database system and the extracted image file in common Convert to format image fileFirst transformationAnd converting the converted image file into the image file of the second format.Second conversionAnd storing the image file in the second format format in the second image database system,FirstThe converting step includes a first image file having item data and image data of the extracted transfer source file name.Converting the image data compressed by the first compression method into image data of a common format,The common format is converted into a common format defined by the transfer source file name and the transfer destination file name of the second image database, and the file name is a combination of the transfer source file name and the transfer destination file name. A step of creating a list file for storing a delivery file for storing a plurality of image files and a file name combining the transfer source file name and the transfer destination file name.TheHaving the secondconversionThe step extracts the common format image file from the delivery file with the file name of the list file, and stores the storage file from the extracted image file according to a reference table that defines the storage target items of the transfer destination. Extract target items,Converting the image data of the common format into image data of the second compression method;Converting to an image file of the second format defined by the transfer destination file name.
[0016]
  Further, the present invention stores a second image file configured in the second format from the first image database system storing the first image file configured in the first format. In the image database transfer system for transferring the first image file to the image database system, the first image file to be transferred is extracted from the first image database system, and the extracted image file is shared. A first server for converting the image file into a format; converting the converted image file into an image file in the second format; and converting the image file in the second format into the second image database system. A second server that stores the extracted server. First image file having a item data and the image data of the original file nameConverting the image data compressed by the first compression method into image data of a common format,The common format is converted into a common format defined by the transfer source file name and the transfer destination file name of the second image database, and the file name is a combination of the transfer source file name and the transfer destination file name. A transfer file for storing the image file, and a list file for storing a file name that is a combination of the transfer source file name and the transfer destination file name. The second server includes the transfer file and the list file. And extracting the image file in the common format from the delivery file with the file name of the list file, and from the extracted image file according to the reference table defining the storage target items of the transfer destination, Extracting the item to be stored;Converting the image data of the common format into image data of the second compression method;The image file is converted into the image file of the second format defined by the transfer destination file name.
[0017]
  In the present invention,Transfer of image files between systems is mediated by a delivery file that defines a common format, and the transfer destination system extracts the storage target items from the extracted image file according to the reference table that defines the storage target items of the transfer destination. Defined in the destination file nameSecond formatA common format defined by the transfer source file name and the transfer destination file name of the second image database, the first image file of the transfer source file name converted into the image file of And a transfer file that stores the image file in the common format with a file name that combines the transfer source file name and the transfer destination file name, and a file name that combines the transfer source file name and the transfer destination file name Because the list file is created, the transfer destination identifies the image file of the common format from the transfer file with the file name of the list file, and converts it to the image file of the second format defined by the transfer destination file name. The target data can be easily extracted at the transfer destination, and File name without having to allocate, you can store the target image file in the second database.
[0019]
  In addition, the list file name that stores the combined file names is used to extract the corresponding image file and convert it to the image file of the second format defined by the transfer destination file name, so only the information required between different systems Even if they are published to each other, converted into a common format image file, and transferred, if a problem occurs, the transferred file can be verified at the transfer source and transfer destination. Furthermore,Transfer of image files between systems that have their own compression method can be easily realized.
[0020]
In the present invention, it is preferable that the first image file of the first image database is a seal file storing a seal image compressed by the first compression method, and the second image database. The second image file is a seal file that stores a seal image compressed by the second compression method.
[0021]
As a result, it is possible to transfer the seal image between the systems without revealing the compression method of the highly confidential seal image.
[0022]
In the present invention, preferably, the step of transferring the image file converted into the common format from the first image database system to the intermediate server, and the image file converted into the common format of the intermediate server And a second image database system reading.
[0023]
As a result, since the intermediate server is used, data transfer can be automated, and leakage to others can be prevented.
[0024]
In the present invention, it is preferable that the extraction step includes a step of reading a list of image file names to be transferred, and searching the first image database system with the read image file names to search for the object. And a step of extracting an image file. As a result, the target image file can be identified and transferred.
[0025]
In the present invention, it is preferable that the second format image file stored in the second image database system is inversely converted into the common format image file, and the inversely converted image file is converted. And collating with the image file in the common format of the first image database system. Thereby, it is possible to verify whether the data transfer by the format conversion has been performed correctly.
[0026]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in the order of an image database transfer system, an image file transfer process, an image file transfer process, a consistency check process after transfer, and other embodiments.
[0027]
[Image database transfer system]
FIG. 1 is a configuration diagram of an image database transfer system according to an embodiment of the present invention, FIG. 2 is an explanatory diagram of image database transfer processing according to an embodiment of the present invention, and FIG. FIG. 4 is a configuration diagram of the number data file in FIG. 2, FIG. 5 is a configuration diagram of the list file in FIG. 2, and FIG. 6 is a configuration diagram of the delivery file in FIG. .
[0028]
FIG. 1 shows a system for transferring customer seal data of A system 1 to B system 2. As shown in FIG. 1, the transfer source electronic seal stamp system 1 includes a system server 3 and a large number of clients 10 to 1 n connected to the system server 3 by a network 100. The system server 3 has a seal stamp database file 6 for storing customer seal stamp data and a transfer application program 5 for transfer processing.
[0029]
A large number of clients 10 to 1 n are provided, for example, at each store of A financial institution and refer to the seal data in the seal database file 6 by using the store number and the account number as keys.
[0030]
On the other hand, the transfer destination electronic seal stamp system 2 includes a system server 4 and a large number of clients 20 to 2 n connected to the system server 4 by a network 102. The system server 4 has a seal database file 8 for storing customer seal data and a transfer application program 7 for transfer processing.
[0031]
A large number of clients 20 to 2n are provided in each store of the B financial institution, for example, and collate by referring to the seal data in the seal database file 8 using the store number and the account number as keys.
[0032]
For the transfer, the transfer source server 3 and the transfer destination server 4 are connected to the intermediate server 9 via the network 104. The transfer source server 3 is connected to a medium reading device 110 that reads a medium storing transfer target number data.
[0033]
Next, an overview of the transfer process will be described. FIG. 2 is an explanatory diagram of the transfer process. As shown in FIG. 3, the electronic seal stamp database 6 in FIG. 2 has a database partitioned for each store number. Inside the section for each store number, an account number part indicating the account number, an account accompanying information part for storing the incidental information of the account indicated by the account number (for example, valid / invalid of the account), and a seal image of the account number It is composed of a seal data portion that is stored in a unique compression format and a seal stamp information portion that stores supplementary information of the seal (for example, validity / invalidity of the seal).
[0034]
The reading application program 5 of FIG. 2 reads the number data file shown in FIG. 4 in which the transfer source account number and transfer destination account number prepared in advance as one set of one record from the medium reading device 110 of FIG. Based on the number data, the customer seal data of the target transfer source account is extracted from the electronic seal database 6 to create a target data file 60.
[0035]
Next, the customer seal data of the target account in the target data file 60 is converted into an open common format format delivery file 62. FIG. 6 is a configuration diagram of the delivery file 62 in the common format format. The file name is the transfer source store number-transfer destination store number. It is defined by an extension, and for each account, an account information part and a seal information part of each seal are stored.
[0036]
The account information part is composed of a transfer source account number, a transfer destination account number, the number of seal information stored, and account-accompanying information 1 to 4. The seal information section includes a seal number, a seal generation within the seal number, supplementary information 1 to 4 of the seal, and image data of the seal. As the image data of this seal stamp, the data converted from the original compression format to the general-purpose format (TIFF or the like) by the above-described conversion is stored.
[0037]
Then, a list file 63 for storing the file name of the created delivery file 62 shown in FIG. 5 is created. Further, the export application program 5 transfers the created delivery file 62 and list file 63 to the intermediate server 9.
[0038]
Next, the transfer destination server 4 executes the transfer application program 7 and transfers the customer data to its own electronic seal stamp database 8 based on the delivery file 62. As in FIG. 3, the transfer application program 7 adds an electronic seal stamp database system 8 having a database partitioned for each store number to the delivery file 62 and list file 63 having the structure described in FIGS. In addition, a transfer operation for storing customer seal data is performed.
[0039]
That is, the list file 63 and the delivery file 62 are collected from the intermediate server 9, and the file name of the delivery file 62 is recognized with reference to the list file 63. Then, based on the transfer destination store number assigned to the recognized file name, the transfer destination store number section into which data is transferred is determined, and a file 80 is created by converting the common format format of the delivery file 62 into its own format format. Then, the converted customer data to be transferred is stored in the transfer destination store number section of its own electronic seal stamp database 8. Here, as will be described later, the file format is converted into its own format, and the seal image data is converted from the general-purpose format into its own compression format.
[0040]
Next, the above-described image file (seal file) export process and import process will be described in detail.
[0041]
[Image file export processing]
First, an export process for extracting target data will be described using an example of an electronic seal stamp database system having a general existing electronic seal stamp database as shown in FIG. 7 is a processing flow diagram of the export processing program of FIG. 2, FIGS. 8 and 9 are explanatory diagrams of the operation, and FIG. 10 is a configuration diagram of the storage target item definition table of FIG.
[0042]
The export process in FIG. 7 will be described with reference to FIGS.
[0043]
(S10) In order to extract target data from the transfer source system, a number data file (FIG. 4) in which an account number serving as a key for specifying the target data is described is stored in a storage medium 112 such as a floppy disk in advance. The prepared number data file (FIG. 4) is read via the medium reader 110 (see FIG. 8). The number data is sorted in ascending order by the transfer source account.
[0044]
(S12) The store number that is the transfer source target is identified from the sort result, and is extracted from the seal database 6 for each store number section, and the transfer source store number section file 68 is created. Then, the transfer source store number section file 68 is sorted in order of account number.
[0045]
(S14) Thereafter, a common format for the target data is created. That is, one transfer source account number in the number data file (FIG. 4) is taken out and compared with the transfer source account number in the transfer source store number section file 68 sorted in order of account number. If there is no match, the process proceeds to step S22.
[0046]
(S16) If there is a matched account number, the seal data of the transfer source account number in FIG. 3 is converted into an account unit file in the common format in FIG. Then, the file name (transfer source store number-transfer destination store number in FIG. 6) is created, and the list file 63 in FIG. 5 is referred to.
[0047]
(S18) If the file name exists in the list file 63, it is added to the common format file (FIG. 6). On the other hand, if the file name does not exist in the list file 63, a common format file (FIG. 6) having the file name is newly created.
[0048]
(S20) Next, the storage target item definition table in FIG. 10 is referred to. In this storage target item reference table, items to be output (stored) at the transfer source (may be stored) are defined by ON / OFF flags. The target items defined in the storage target item definition table are extracted from the common format file and output to the delivery format file 62.
When output to the delivery format file 62, the transfer destination account number paired with the transfer source account number of the matched number data file (FIG. 4) is assigned and stored.
[0049]
(S22) It is determined whether the common format creation has been completed for all transfer source account numbers in the number data file (FIG. 4). If not completed, the process returns to step S14 to create a common format for the next transfer source account number. On the other hand, when it is finished, the common format creation is finished.
[0050]
Then, as shown in FIG. 8, the created delivery file 62 and list file 63 are transferred to the intermediate server 9. The intermediate server 9 stores the delivery file 62 and the list file 63.
[0051]
In this way, by the export process, the target seal data of the seal database 6 is extracted and converted into a format defined by the transfer source account number and the transfer destination account number (item format and general format seal image, signature image). The Further, since the transfer source store number section is extracted based on the store number indicated by the record in the number data file, a transfer file for each transfer source store number can be easily created.
[0052]
Furthermore, since the transfer source store number section is sorted in order of account number and compared with the transfer source account number, the target account number data can be extracted at high speed, and a common format file can be generated at high speed.
[0053]
[Image file transfer processing]
Next, transfer processing for storing the target data in the electronic seal stamp database will be described by taking the list file 63 and the delivery file 62 as shown in FIGS. 5 and 6 as an example. FIG. 11 is a process flow diagram of the transfer process program of FIG. 2, FIGS. 12 and 13 are explanatory diagrams of its operation, and FIG. 14 is an explanatory diagram of an example of conversion from a delivery file to a company database structure.
[0054]
The transfer process of FIG. 11 will be described with reference to FIGS.
[0055]
(S30) The list file 63 and the delivery file 62 provided from the transfer source are read from the intermediate server 9 and stored (see FIG. 12). With reference to the list file 63, the file name of the delivery file in which the customer data to be transferred is stored is obtained, and the delivery file 62 is read with the obtained file name. Then, the delivery file 62 is sorted in the order of the transfer destination account number.
[0056]
(S32) Next, an intermediate file is created. Data of each account number in the common format format of the delivery file sorted in order of the transfer destination account number is extracted.
[0057]
(S34) The storage target item definition table in FIG. 10 is referred to for the extracted account number. In this storage target item reference table, an item to be stored at the transfer destination is defined by an ON / OFF flag. The target items defined in the storage target item definition table are extracted from the common format file and output to the intermediate file 84. At this time, the read image data or the like is converted into its own format to create an intermediate file 84 (see FIGS. 12 and 13). FIG. 14 shows an example of such conversion. For example, an SJIS code system delivery file is converted into an EUC code system, and the Western calendar is converted into a Japanese calendar, and a general-purpose compression format (TIFF) seal image, etc. is uniquely compressed. Convert to a stamp image of the format. Furthermore, necessary items are stored in the company database.
[0058]
(S36) It is determined whether the creation of the intermediate file 84 has been completed for all the transfer destination account numbers. If not completed, the process returns to step S32 to create an intermediate file of the next transfer destination account number. On the other hand, if completed, creation of the intermediate file 38 is terminated.
[0059]
(S38) The transfer destination store number section is directly identified by the transfer destination store number assigned to the file name of the delivery file 62, the transfer destination store number section 82 is sucked up from the seal stamp database 8, and the data of the transfer destination store number section 82 + intermediate A composite file 86 that is data of the file 84 is created.
[0060]
(S40) This composite file 86 is stored in the transfer destination store number section of the seal stamp database 8.
[0061]
(S42) It is determined whether the transfer process for all the delivery files 62 has been completed. If not completed, the process returns to step S30. If completed, the transfer process is terminated.
[0062]
In this way, by the transfer process, the target seal data of the delivery file in the common format format is extracted and converted into the format defined by the transfer destination account number (item format and general format seal image, signature image). In addition, since the transfer destination store number section is extracted from the delivery file name, processing for each transfer destination store number can be performed.
[0063]
Furthermore, since the files are sorted in order of the transfer destination account number and compared with the transfer destination account number, an intermediate file can be created at high speed from the common format file. It is possible to transfer customer data between different electronic seal database systems.
[0064]
In this way, by supporting the transfer processing method that interposes the list file and the delivery file defined as a common format, the target data is extracted from its own database at the transfer source and output to the common format format. The system does not need to be aware of the database structure of different partners.
[0065]
Further, since the account number of the transfer destination is assigned to the target data extracted at the transfer source, there is no need to allocate an account number again in the transfer destination system. Furthermore, since the transfer source store number and the transfer destination store number are given to the delivery file name created at the transfer source, the transfer destination system can recognize the transfer destination store number section in the seal stamp database only by referring to the file name.
[0066]
Further, since the transfer source store number and the transfer destination store number are given to the delivery file name created at the transfer source, it is clear which customer data to be transferred is transferred from which data to which store number. Thereby, the transfer process of the transfer destination is simplified as a whole.
[0067]
[Consistency check after transfer]
Next, a method for checking the validity of the stored image data after storing the mutually transferred data will be described. In other words, image data is often managed by each manufacturer using its own compression method, and each manufacturer recognizes that it should be protected as a unique technology. Therefore, there is no tendency to disclose these technologies to other companies in the same industry, and it is unlikely to provide raw data.
[0068]
Therefore, as described above, a method has been proposed in which image data stored in a common format is converted into a general-purpose compression method and stored. With this method, data can be delivered while protecting the manufacturer's original technology, but the raw image data is once converted into a general-purpose compression format and then transferred to the original format. Since it is stored, data conversion is interposed twice.
[0069]
In this respect, since it is predicted that a means for verifying whether or not data deterioration has occurred is required, a method of verifying the validity of the transfer result after data transfer between different manufacturers is shown in FIG. And FIG. 16 demonstrates.
[0070]
As shown in FIG. 15, the transfer source server 3 backs up the created delivery file 62-1 and list file 63-1. On the other hand, the transfer destination server 4 stores the transfer data in its own system based on the transferred file 62. After the storage is completed, a return account number is extracted, and data stored in the transfer destination database 6 is extracted from the seal stamp database 8 to create a delivery file (hereinafter referred to as a return file 88). The created return file 88 is transferred to the intermediate server 9, and the operation of the transfer destination server 4 is completed.
[0071]
This return file 88 includes account data converted from the company database format described above with reference to FIG. 14 to the common format format.
[0072]
Next, in order to perform the verification work, as shown in FIG. 16, the transfer source server 3 acquires the return file 88 from the intermediate server 9, and acquires the acquired return file 88 and backup data (the delivery file 62-1 and the list). Compare with file 63-1) to check consistency.
[0073]
This makes it possible to verify the transfer result even if the format forms are different and without disclosing each other's format.
[0074]
[Other embodiments]
Although the image database has been described as an image database in the example of the seal stamp database as shown in FIG. 1, it can be applied to a signature database and other image content databases.
[0075]
Further, although an intermediate server is interposed, a portable storage medium such as an optical disk, a magnetic disk, or a magnetic tape may be used.
[0076]
As mentioned above, although this invention was demonstrated by embodiment, in the range of the meaning of this invention, this invention can be variously deformed, These are not excluded from the scope of the present invention.
[0077]
(Supplementary Note 1) A second image database that stores a second image file configured in the second format from a first image database system that stores the first image file configured in the first format. In the image database transfer method for transferring the first image file to the system, the step of extracting the first image file to be transferred from the first image database system and the extracted image file in common A step of converting the image file into a format, a step of converting the converted image file into an image file of the second format, and an image file of the second format in the second image database system. And storing the image database. Scan transfer methods.
[0078]
(Supplementary Note 2) The step of converting into the image file in the common format includes the step of converting the image file compressed by the first compression method into an image file in the common format, and the image in the second format format. The method of transferring an image database according to appendix 1, wherein the step of converting into a file comprises the step of converting the image file of the common format into an image file of the second compression method.
[0079]
(Supplementary note 3) The first image file of the first image database is a seal file storing a seal image compressed by the first compression method, and the second image database of the second image database. The image database transfer method according to appendix 2, wherein the image file is a seal file storing a seal image compressed by the second compression method.
[0080]
(Supplementary Note 4) Transferring the image file converted into the common format from the first image database system to an intermediate server, and the image file converted into the common format of the intermediate server into a second image database The method of transferring an image database according to claim 1, further comprising a step of reading by the system.
[0081]
(Supplementary Note 5) The extraction step includes a step of reading a list of image file names to be transferred, a search of the first image database system with the read image file name, and a search for the target image file. The method for transferring an image database according to appendix 1, characterized by comprising the step of extracting.
[0082]
(Additional remark 6) The step which reversely converts the image file of the said 2nd format format stored in the said 2nd image database system into the image file of the said common format, the said reversely converted image file, and the said 1st The method for transferring an image database according to appendix 1, further comprising the step of collating with the image file of the common format of the image database system.
[0083]
(Supplementary Note 7) A second image database storing a second image file configured in a second format from a first image database system storing a first image file configured in a first format In the image database transfer system for transferring the first image file to the system, the first image file to be transferred is extracted from the first image database system, and the extracted image file has a common format. A first server for converting into an image file; and converting the converted image file into an image file in the second format, and storing the image file in the second format in the second image database system. An image database transfer system characterized by comprising: Temu.
[0084]
(Supplementary Note 8) The first server converts the image file compressed by the first compression method into an image file of a common format, and the second server converts the image file of the common format to the first format. 8. The image database transfer system according to appendix 7, wherein the image database is converted into an image file of the compression method of 2.
[0085]
(Supplementary note 9) The first image file of the first image database is a seal file storing a seal image compressed by the first compression method, and the second image database of the second image database. The image database transfer system according to appendix 8, wherein the image file is a seal file storing a seal image compressed by the second compression method.
[0086]
(Supplementary Note 10) An intermediate server that stores the image file converted to the common format transferred from the first server and transfers the stored image file converted to the common format to the second image database system. The image database transfer system according to appendix 7, further comprising:
[0087]
(Supplementary Note 11) The first server reads a list of image file names to be transferred, searches the first image database system with the read image file name, and selects the target image file. The image database transfer system according to appendix 7, wherein the image database transfer system is extracted.
[0088]
(Supplementary Note 12) The second server reversely converts the second format image file stored in the second image database system into the common format image file, and the first server The image database transfer system according to appendix 7, wherein the reversely converted image file is compared with the image file in the common format of the first image database system.
[0089]
【The invention's effect】
  Thus, according to the present invention, transfer of image files between systems is mediated by a delivery file that defines a common format.,In the transfer destination system, the storage target item is extracted from the extracted image file according to the reference table that defines the storage target item of the transfer destination, and the second destination defined by the transfer destination file name is output in the common format format. Since it is converted into an image file in the format format, transfer can be executed without having to be aware of the database structure of different partners. In addition, the first image file having the item data and the image data of the extracted transfer source file name is defined by the transfer source file name and the transfer destination file name of the second image database at the transfer source. A transfer file that stores the image file in the common format with a file name that combines the transfer source file name and the transfer destination file name, and a file name that combines the transfer source file name and the transfer destination file name Since the list file is created, the transfer destination identifies the image file in the common format from the delivery file with the file name of the list file, and the image in the second format defined by the transfer destination file name. It can be converted into a file, and the target data can be easily extracted at the transfer destination. Anew file name without having to allocate, can store the target image file in the second database. In addition, since a file name combining the transfer source file name and the transfer destination file name is allocated, only the necessary information between different systems is disclosed to each other, converted into a common format image file, and transferred. If this occurs, the converted file can be verified at the transfer source and transfer destination.Furthermore, it is possible to easily transfer image files between systems that have their own compression method.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of an electronic image database transfer system according to an embodiment of the present invention.
FIG. 2 is an explanatory diagram of electronic image database transfer processing according to the embodiment of this invention.
FIG. 3 is a configuration diagram of the electronic image database of FIG. 2;
4 is a configuration diagram of a transfer number file in FIG. 2;
FIG. 5 is a configuration diagram of the list file of FIG. 2;
6 is a configuration diagram of the delivery file of FIG. 2. FIG.
FIG. 7 is a flow chart of export processing according to an embodiment of the present invention.
FIG. 8 is an operation explanatory diagram of the export process of FIG. 7;
9 is a relationship diagram of files in the export process of FIG. 7;
10 is a configuration diagram of a storage target item definition table in FIG. 7;
FIG. 11 is a flowchart of import processing according to the embodiment of the present invention.
12 is an operation explanatory diagram of the transfer process of FIG. 11. FIG.
13 is a relationship diagram of files in the import process of FIG. 11. FIG.
14 is an explanatory diagram of a format conversion example of the import process of FIG. 11. FIG.
FIG. 15 is an explanatory diagram of transfer verification processing according to the embodiment of this invention;
16 is an explanatory diagram of the verification process of FIG. 15;
[Explanation of symbols]
1 First electronic seal database system
2 Second electronic seal database system
3, 4 System server
5 Export application program
6 First seal database
7 Transfer application program
8 Second seal database
9 Intermediate server
10-1n, 20-2n client

Claims (4)

The first image database system that stores the first image file configured in the first format format to the second image database system that stores the second image file configured in the second format format. In the image database transfer method of transferring one image file,
Extracting the first image file to be transferred from the first image database system;
A first conversion step of converting the extracted image file into a common format image file;
A second conversion step of converting the converted image file into an image file of the second format;
Storing the second format image file in the second image database system;
The first conversion step includes:
The image data compressed by the first compression method of the first image file having the item data and image data of the extracted transfer source file name is converted into image data of a common format, and the transfer An image in the common format is converted to a common format defined by the original file name and the transfer destination file name of the second image database, and the file name is a combination of the transfer source file name and the transfer destination file name. Creating a list file for storing a delivery file for storing a file, and a file name combining the transfer source file name and the transfer destination file name,
The second conversion step includes:
Extracting the image file in the common format from the delivery file with the file name of the list file, and according to the reference table that defines the storage target item of the transfer destination, the storage target item from the extracted image file Extracting , converting the image data of the common format into image data of the second compression method, and converting the image data to the image file of the second format format defined by the transfer destination file name. A method for transferring a featured image database. The first image file of the first image database is
A seal file storing a seal image compressed by the first compression method;
The second image file of the second image database is:
The method for transferring an image database according to claim 1 , wherein the seal stamp file stores a seal stamp image compressed by the second compression method. Back-converting the image file of the second format format stored in the second image database system into the image file of the common format;
The image database transfer method according to claim 1, further comprising a step of collating the reversely-converted image file with the image file of the common format of the first image database system. The first image database system that stores the first image file configured in the first format format to the second image database system that stores the second image file configured in the second format format. In the image database transfer system for transferring one image file,
A first server that extracts the first image file to be transferred from the first image database system and converts the extracted image file into an image file of a common format;
A second server that converts the converted image file into an image file of the second format format and stores the image file of the second format format in the second image database system;
The first server converts the image data compressed by the first compression method of the first image file having the extracted transfer source file name item data and image data into a common format image data Is converted into a common format defined by the transfer source file name and the transfer destination file name of the second image database, and the transfer source file name and the transfer destination file name are combined. Create a list file that stores a transfer file that stores the image file in the common format by name, and a file name that combines the transfer source file name and the transfer destination file name,
The second server receives the delivery file and the list file, extracts the common format image file from the delivery file with the file name of the list file, and stores the transfer destination storage item Is extracted from the extracted image file, the image data in the common format is converted into image data of the second compression method, and defined by the transfer destination file name An image database transfer system, wherein the image file is converted into the image file of the second format.

Images