JP2010225076A - Business document processor and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the following problem: after a document prepared on business is finally presented, it is not known which document is a final presentation version or which document is an in-preparation version. <P>SOLUTION: This business document processor decides that a business document wherein an imprint is extracted from a scan image is the final presentation version. Thereafter, the business document processor decides whether or not file data is file data corresponding to the final presentation version by comparison between an imprint removal scan image obtained by removing imprint data from the scan image corresponding to the final presentation version and a print image of each piece of file data. That is, the business document processor decides that each piece of file data wherein the print image accords with the imprint removal scan image is file data of the in-preparation version. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for efficiently managing file data of business documents existing in a large amount and in a distributed manner. The present invention relates to a business document processing apparatus and a program for realizing a processing function corresponding to the business document processing apparatus through a computer, for example.

  In many organizations such as corporations, various documents such as planning documents, proposals, reports, and the like (hereinafter referred to as “business documents”) are created on business. There are many differences in the production process of business documents as well as the format differences described above. For example, there are those that are reviewed multiple times before the final version. In addition, some revisions are made after the review of the superior, and the final version is finalized when the approval of the superior is finally obtained. Further, business documents are generally created using office software such as word processing software that runs on a computer. However, for the reasons listed below, the creation process is not always simple.

(Reason 1) Each version may be created as a different file. The reason why files with different versions are created in this way is that, for example, a single document is created by multiple people, for example, so that the versions can be easily traced. For example, in order to avoid the risk of handling the file by mistake (overwriting or deleting), for example, to avoid the risk of the file being damaged during overwriting, etc. For this reason, the creator name, date, version number, etc. are often added to the file name or folder name of each file. Prefixes such as "Copy ~" and "Copy (2) ~" indicating that the file was copied and pasted may be added to the beginning of the file name.

(Reason 2) The plurality of files described in the reason 1 described above may be stored in a plurality of folders. The reason why the folders are divided is that, for example, a plurality of creators are saved on the local PC, so for example, they are usually saved on the creator's local PC. To submit as a file (using mail, shared folder, file server, workflow, groupware, etc.), for example, to submit to the secretariat department, for example, to provide as reference information to others .

(Reason 3) The progress of the edition may branch in the middle of repeated reviews and peer review. The reason for this branching is that multiple revisions were considered for the review results of the superior, and the intention to make corrections was reversed and returned. Because it has advanced, it is mentioned.

(Reason 4) The latest file creation date may not be the final submitted version. The reason for this is that once the final version was completed, it was canceled due to changes in the situation and the previous version was finally submitted, so the version file in the process of creation was accidentally overwritten and the creation date changed. For this reason, the time setting is different between the server and the local computer.

JP 2008-176521 A JP 2006-309781 A JP-A-9-229646

Documentum (EMC Japan Ltd.), [online], September 3, 2007, Internet <URL: http: //japan.emc.com/products/documentum-platform/developer-components.htm> Apeos PEMaster (Fuji Xerox Co., Ltd.), [online], November 27, 2007, Internet <http://www.fujixerox.co.jp/company/tr/17/pdf/p_04.pdf> FileNet (Japan IBM Corporation), [online], December 21, 2007, Internet <http://www.ibm.com/developerworks/jp/ysl/library/db2/y-db2-filenetp8 -3 /> Yukiichi Sakai: Basics and Applications of Digital Image Processing-From Basic Concepts to Face Image Recognition-Sections 5.2-5.3 CQ Publisher (issued in 2003)

  For reason 1 and reason 2, many files remain in many folders during the creation process. Many documents have more than 10 versions to be completed. However, once the business document is finally submitted, the version in the process of being created only wastes storage capacity. Also, if access must be managed assuming that the final submitted version is confidential information, it should be considered that confidential information is also included in the version that is being created. However, as described above, a file whose version is being created that has become unnecessary is simply left as a file and cannot be included in the access management target.

  In addition, as mentioned above, the electronic data of the submitted document will be sent to the user at a later date due to the fact that unnecessary files in the middle of creation remain in the folder and that the latest creation date is not necessarily the final submitted version. It is difficult to find. It is often difficult for authors and reviewers to determine which is the final submitted version or the version that is in the process of being created, and the user spends unnecessary man-hours to check the version. Become.

  By the way, there is a specialized document management system with a function to perform version management etc. for creating documents in specialized fields such as regulatory application documents, manuals, risk control matrix of internal control (see Non-Patent Documents 1 to 3) ).

  However, the conventional techniques as listed in Non-Patent Documents 1 to 3 solve the problem that it is difficult to find the electronic data of the final submitted version because the file of the version being created consumes storage capacity It is not possible. This is because in the document management system as shown in Non-Patent Documents 1 to 3, it is assumed that each version is registered in the document management system during document creation. If each version of a document being created is registered sequentially, it can be handled in an organized manner, but it cannot be applied after the creation has been completed without registering anything. In addition, it is necessary to register the structure information about the document in advance, which is not suitable for handling miscellaneous documents.

  Therefore, the inventor performs an imprint extraction process on the scanned image captured for the business document for the purpose of solving one of the problems described above, and if the imprint is extracted, the imprint is extracted. We propose a method for judging the scanned image from which the image is extracted as the final submitted version.

  Further, the inventor removes the imprint image from the scan image determined as the final submitted version to generate one of the above-described problems, while generating the imprint imprint scan image, Read the file data from the storage area, generate the print image, and sequentially compare the imprint removal scan image with the print image, so that the file data having the print image that matches the imprint removal scan image is made into the final submitted version We propose a method to determine the corresponding file data.

  In order to solve one of the above-mentioned problems, the inventor has the file name or text data of the file data determined to be the final submission version, and each file data read from the storage area within the setting range. If the difference between the file name or the text data is less than or equal to the set condition, we propose a method for determining that the file data is in the process of being created.

  Further, the inventor intends to solve one of the problems described above, and scans the date and time of scanning the file data of the corresponding final submitted version among the file data to which metadata indicating that the version is in the process of being created We propose a method to extract only those that have passed the set period.

  According to one invention proposed by the inventor, file data corresponding to the final submitted version can be easily extracted even if it is a business document created by repeating revisions and corrections over and over again. be able to. As a result, the man-hours required for searching the file data corresponding to the final submitted version can be greatly reduced. Further, according to one invention proposed by the inventor, not only file data corresponding to the final submitted version but also file data corresponding to the intermediate version can be easily extracted. For this reason, the file data corresponding to the halfway version can be included in the access management target. In addition, the storage capacity can be effectively utilized by deleting the file data corresponding to the halfway version from the storage.

It is a functional block diagram which shows the schematic structural example of the business document processing apparatus which concerns on the form example. It is a figure which shows the example of a data structure of version information data. It is a flowchart explaining the whole processing procedure performed in the business document processing apparatus when a business document is scanned. It is a flowchart explaining the whole processing procedure performed in the business document processing apparatus at the time of business document inventory. It is a figure which shows the example of a confirmation screen displayed at the time of the inventory of a business document. It is a flowchart explaining the detailed operation example performed in a submitted version determination process part. It is a figure which shows the example of a confirmation screen displayed by the submitted version determination process part. It is a flowchart explaining the example of detailed operation | movement performed by the preparation halfway version process part. It is a figure which shows the example of a confirmation screen displayed by the preparation halfway version process part. It is a figure which shows the example of another confirmation screen displayed by the preparation middle version process part.

  Hereinafter, embodiments of a business document processing apparatus according to the present invention will be described with reference to the accompanying drawings. Needless to say, the form examples described below and their descriptions are merely examples, and various modifications can be considered in the present invention.

  In the following embodiments, the inventor often stamps the final submitted business document by the creator or approver and makes a copy of electronic data as a copy before submission. Focused on the fact that there are many. Copying electronic data is also recommended from the viewpoint of space and resource saving.

(1) Form Example (1-1) System Configuration FIGS. 1 to 9 are diagrams illustrating form examples described below. In these drawings, the same reference numerals denote the same parts, The basic configuration and operation are the same.

  FIG. 1 is a functional block diagram schematically showing the internal structure of a business document processing apparatus according to an embodiment. The business document processing apparatus includes a multifunction peripheral 100, a file storage location 101, a display device 102 for displaying data, a keyboard 103 for performing operations such as selecting a menu for the displayed data, a mouse, and the like. Pointing device 104, central processing unit 105 that performs necessary arithmetic processing, control processing, etc., program memory 106 that stores programs necessary for processing in central processing unit 105, and data that is necessary for processing in central processing unit 105 The data memory 107 is provided.

  Here, the multifunction peripheral 100 has both a scanner for capturing a business document as electronic data (scanned image) and a print engine for printing and outputting a print image on a paper medium. The file storage location 101 is a storage device or storage area that can store file data, such as a local PC, a shared file server, a mail server, a workflow system, and groupware. In an actual business document processing apparatus, a combination of all or a part of these is used as the file storage location 101.

  The central processing unit 105 includes a submitted version processing unit 108, an intermediate version processing unit 109, and an intermediate version deletion processing unit 110. In the case of this form example, it is configured by a computer, and the submitted version processing unit 108, the creation intermediate version processing unit 109, and the creation intermediate version deletion processing unit 110 are all as part of the functions of the program executed on the computer. Realized. Note that these programs are stored in the program memory 106. Further, the data memory 107 stores version information data 116 that holds version information such as whether the file is a final submitted version or a version that is being created.

Returning to the description of the processing functions constituting the central processing unit 105.
The submitted version processing unit 108 includes a seal impression extraction processing unit 111, a submitted version determination processing unit 112, and a submitted version information addition processing unit 113.

  The seal imprint extraction processing unit 111 performs a process function of executing a seal imprint extraction process on a scanned image of a business document, and determining a final submitted version (that is, a final submitted version) scan image. provide.

  The submitted version determination processing unit 112 generates a seal impression removed scan image obtained by removing the seal impression from the scan image determined to be the final submitted version, and a process of generating a print image for each file existing in the file storage location 101. A processing function for performing processing for comparing the imprint scan image with the print image, and processing for determining that the file corresponding to the print image for which the match has been confirmed is electronic data (file) corresponding to the final submitted version I will provide a.

  The submitted version information addition processing unit 113 assigns, for example, metadata indicating that the file is determined to be electronic data (file) of the final submitted version, for example, the submitted version, and the date and time when the final submitted version is scanned. And processing for displaying the result on the screen of the display device 102 are provided.

  The preparation halfway processing unit 109 includes a preparation halfway version determination processing unit 114 and a preparation halfway version information addition processing unit 115.

  The creation intermediate version determination processing unit 114 determines whether the file in the file storage location 101 that is related to the electronic data (file) of the final submission version is the electronic data (file) of the creation intermediate version. A processing function for determining

  Here, the relevant file storage location 101 is, for example, the same folder as the electronic data (file) of the final submission version, a folder having a transmission or reply relationship with the electronic data (file) of the final submission version, A folder on the same workflow as the electronic data (file) of the final submission version, a folder on the same groupware as the electronic data (file) of the final submission version, and other storage locations. The relevance that defines the range to be processed is set in advance by the user. Of course, the user may set it in consideration of the purpose or the like.

  In the case of this embodiment, whether or not the electronic data (file) is in the middle of creation is determined based on whether or not only a prefix set in advance in the file name is different. For example, if the only difference between the file name of the electronic data (file) of the final submitted version is the creator name, date, version number, and prefix indicating that the file has been copied and pasted, the mid-preparation version judgment process It is assumed that the unit 114 determines that the file is electronic data (file) of an intermediate version.

  For the electronic data (file) determined to be an in-progress version, the in-progress version information addition processing unit 115 is, for example, an in-progress version, the storage location of the corresponding electronic data (file) of the final submission version, and the final submission A process of providing metadata having the date and time when the plate is scanned and a process of displaying the result on the screen of the display device 102 are provided.

  The creation intermediate version deletion processing unit 110 crawls electronic data (files) in the file storage location 101 within a preset range at the time of execution of the file inventory, and among the electronic data (files) of the creation intermediate version, Processing for displaying on the screen of the display device 102 as a candidate for deletion that has passed a predetermined period from the date and time of scanning the submitted version, and deleting the corresponding electronic data (file) when there is a deletion instruction Processing and provide.

(1-2) Version Information Data FIG. 2 shows a data structure example of the version information data 116 included in the data memory 107. The version information data includes, for example, a submitted version flag 200, a preparation version flag 201, a submitted version storage location 202, and a submitted version scan date 203. The submission version flag 200 and the preparation version 201 are set to NO at initialization. An empty character string is set in the submitted version storage location 202 and the submitted version scan date 203 at the time of initialization. The submission version storage location 202 holds a path of electronic data (file) of the final submission version. If it is determined that there are multiple electronic data (files) of the final submission number (for example, perform a review process on the local PC, copy it to the file server, attach it to an email, ask the supervisor to review it, and submit it) In the case of having received, etc.), a plurality of paths are concatenated with delimiters and held.

  FIG. 2 exemplifies version information data of a file that has already been determined to be in the middle of creation. Therefore, the submission version flag 200 is set to NO, and the creation halfway version flag 201 is set to YES. This flag state means that the final submitted version has not been determined, but has been determined to be an in-progress version. In the case of FIG. 2, the path name of the file of the final submitted version obtained by the review for this file is indicated as “C: \ tmp \ document.doc” in the submitted version storage location 202. In the case of FIG. 2, the date and time when the final submitted version corresponding to this file was scanned is shown as “January 7, 2009 at 9:00” in the submitted version scan date and time 203.

(1-3) Overview of Processing Operation Next, an overview of processing operation executed in the business document processing apparatus described above will be described. Processing operations executed by the business document processing apparatus can be classified into two types: when a business document is scanned and when a file inventory is executed. An outline of the processing operation corresponding to each time point is shown in FIGS. FIG. 3 is a flowchart schematically showing the flow of processing when a business document is scanned. FIG. 4 is a flowchart schematically showing the flow of processing executed using the pre-creation version deletion processing unit 110 when performing file inventory.

  First, an outline of an operation when scanning a business document will be described with reference to FIG. The central processing unit 105 reads a document scan image obtained by scanning the business document (step 300). The document scan image is captured from a paper medium in the multifunction peripheral 100, for example, and stored in the file storage location 101.

  Next, the submitted version processing unit 108 executes processing for determining the submitted version (step 301). This processing is executed through the processing operations of the seal impression extraction processing unit 111, the submitted version determination processing unit 112, and the submitted version information addition processing unit 113. Details of the processing operation will be described with reference to FIG.

  After the processing operation of the submitted version processing unit 108 is completed, the creation halfway version processing unit 109 executes a process of determining a creation middle version (step 302). The processing here is executed through the processing operations of the preparation halfway version determination processing unit 114 and the preparation halfway version information addition processing unit 115. Details of the processing operation will be described with reference to FIG.

  Next, the outline of the operation at the time of inventorying a file will be described with reference to FIG. The creation intermediate version deletion processing unit 110 of the central processing unit 105 starts crawling (searching) the file storage location 101 and pays attention to the first file (step 400). Subsequently, the pre-creation version deletion processing unit 110 checks whether or not a file to be crawled still remains (step 401). If it does not remain, the process ends. On the other hand, if the file remains in the determination of step 401, the creation halfway version deletion processing unit 110 indicates that the creation halfway version flag 201 of the version information data 116 is YES and the submitted version scan date 203 is the current time. It is checked whether or not it is a certain period before (step 402).

  If this determination condition is met (in the case of YES), a confirmation screen as shown in FIG. 5 is displayed on the screen of the display device 102 (step 403). On this confirmation screen, the title "Confirmation of deletion of files being created after a certain period has passed" and that the displayed file is determined to be in the process of being created, and after the final submitted version has been submitted A message explaining to the user that a certain period has elapsed is displayed. In addition, this confirmation screen displays the “file name” of the intermediate version as a deletion candidate, the “submission file name” corresponding to the intermediate version, and the “submission scan date and time” corresponding to the date and time when the final submitted version was submitted. Is also displayed. In addition, on this confirmation screen, as an operation button, a “delete” button used to input an instruction to delete the displayed file, and a “do not delete” button used to input an instruction to save the displayed file Is displayed.

  In step 403, when the user presses the “delete” button 500 for instructing deletion, the creation intermediate version deletion processing unit 110 deletes the corresponding file from the file storage destination 101. After this deletion process or when a negative result is obtained in step 402 (in the case of N), the pre-production version deletion processing unit 110 continues to crawl the file storage location 101. That is, pay attention to the next file (step 404). Then, the process is repeated from step 401. This operation is executed until there is no file in the file storage location 101 that is the crawl destination that has not been processed in step 402 and subsequent steps.

  Through the above processing, the user can selectively delete a file in the middle of creation, and increase the free capacity of the storage capacity. It should be noted that, by making it possible to selectively delete a file in the middle of creation as in this embodiment, management according to the policy on the user side becomes possible. Of course, a program can be created to automatically delete all files after a certain time has passed since submission.

(1-4) Detailed Operation Hereinafter, a detailed operation of a processing operation executed when a business document is scanned (that is, when a business document is submitted) will be described. This processing operation corresponds to the operations of step 301 and step 302 in FIG.

(A) Detailed Operation of Step 301 First, details of the processing operation corresponding to step 301 will be described according to the flowchart shown in FIG. The submitted version processing unit 108 performs an imprint extraction process on the document scan image (step 600). This process is executed by the seal impression extraction processing unit 111. In addition, about extraction processing, the existing technique (refer patent documents 1-3) is applicable. Therefore, detailed description of the processing operation is omitted.

  Next, the submitted version processing unit 108 determines whether or not an imprint has been extracted in Step 600 (Step 601). This is because all document scan images are not necessarily business documents to be submitted. When it is determined in step 601 that the seal imprint has not been extracted, the submitted version processing unit 108 determines that the business document to which the document scan image is finally submitted has not been scanned. In this case, it is not necessary to perform the subsequent processing. Therefore, the submitted version processing unit 108 ends the process. On the other hand, when it is determined in step 601 that the seal impression has been extracted, the submitted version processing unit 108 executes the processing from step 602 onward. The processing after step 602 is executed by the submitted version determination processing unit 112.

  The submitted version determination processing unit 112 starts crawling the file storage location 101 and focuses on the first file (step 602). Next, it is determined whether there are still files to be crawled (step 603). If not, the submitted version determination processing unit 112 ends the subsequent processing.

  On the other hand, if it is determined in step 603 that the file remains, the submitted version determination processing unit 112 has initialized the version information data (the submitted version flag 200 and the in-progress version flag of the version information data 116). 201 is both NO), and it is determined whether the print image of the currently focused file matches the document scan image (imprint removal scan image) excluding the seal image extracted in step 600 ( Step 604).

  A known technique (see, for example, Non-Patent Document 4) can be applied to determine whether or not two images match. Since various methods already exist, detailed description is omitted here.

  When it is determined in step 604 that the determination condition is satisfied, the submitted version information addition processing unit 113 that has taken over the processing from the submitted version determination processing unit 112 sets YES in the submitted version flag 200 of the version information data 116 (step 605), the current time is set in the submitted version scan date 203 (step 606).

  Thereafter, the submitted version information addition processing unit 113 creates a confirmation screen as shown in FIG. 7 based on the contents set in steps 605 and 606, and displays it on the screen of the display device 102 (step 607). This confirmation screen shows that the title “Confirmation / Registration Confirmation of Submitted Version File” and the printed image of the displayed file are the same except for the scanned image and the seal image, and that it has been judged as electronic data of the final submitted version. A message explaining to the user is displayed.

  In addition, “file name”, “submission version flag”, “creation version flag”, and “submission version scan date / time” are also displayed on this confirmation screen. In the case of this embodiment, the path 700 of the currently focused file is also displayed in the “file name” column. Similarly, the setting contents 701 of the submitted version flag 200 registered in the version information data 116 are displayed in the column of “submitted version flag”. In the case of FIG. 7, the setting content is displayed by a black circle display on the YES side. Similarly, the setting contents 702 of the creation intermediate version flag 201 are displayed in the column of “creation intermediate version flag”. In the case of FIG. 7, the setting contents are displayed by a black circle display on the NO side. In addition, the setting content 703 of the submitted version scan date and time 203 is displayed in the column of “submitted version scan date and time”. Based on these displays, the user confirms the validity of the determination content, and if necessary, executes a work for correcting the setting content on the confirmation screen.

  In addition to these, on the confirmation screen, as an operation button, a “Browse” button for confirming the contents of the file specified by the file name, and “Cancel” used for inputting an instruction to cancel registration of the displayed file are displayed. ”Button and a“ Register ”button used to input an instruction for registering the displayed file.

  If the “Cancel” button or “Register” button is operated in Step 607 or if it is determined that the file does not match in Step 604, the submitted version determination that succeeds the process from the submitted version information addition processing unit 113. The processing unit 112 continues to crawl the file storage location 101 and focuses on the next file (step 608). Then, the process is repeated from step 603.

(B) Detailed Operation of Step 302 Next, details of the processing operation corresponding to Step 302 will be described with reference to the flowchart shown in FIG. First, the halfway version determination processing unit 114 of the halfway version processing unit 109 determines whether one or more files of the final submitted version have been determined (step 800). If it is determined that there is no final file, there is no point in determining the file that is being created. In this case, the creation intermediate version determination processing unit 114 ends the process at this point.

  On the other hand, if it is determined that there are one or more files of the final submitted version, the creation intermediate version determination processing unit 114 crawls a file storage location located around the file determined to be the final submitted version as a crawl target. And pay attention to the first file (step 801). Here, “peripheral” means, for example, the same folder as the electronic data (file) of the final submitted version, a folder having a transmission or reply relationship with the electronic data (file) of the final submitted version, and the electronic data of the final submitted version A folder on the same workflow as the data (file), a folder on the same groupware as the electronic data (file) of the final submission version, and other storage locations. The peripheral range is set in advance by the user. Of course, the user may set it in consideration of the purpose or the like.

  Next, the creation intermediate version determination processing unit 114 determines whether or not a file to be crawled remains (step 802). If it is determined in step 802 that no file remains, the creation version determination processing unit 114 ends the process at that time.

  On the other hand, if it is determined in step 802 that the file remains, the creation version determination processing unit 114 has initialized the version information data (the submitted version flag 200 of the version information data 116 and the creation process). Version flags 201 are both NO), and the file name difference between the currently focused file and the final file is the creator name (difference such as “document_matsumoto.doc”), date ( Differences such as "document_20090109.doc"), version numbers (differences such as "document_rev06.doc"), prefixes (differences such as "Copy ~ document.doc" and "Copy (2) ~ document.doc") )) (Step 803).

  When the determination condition is satisfied, the preparation intermediate version information addition processing unit 115 that has taken over the processing from the preparation intermediate version determination processing unit 114 sets YES to the preparation intermediate version flag 201 of the version information data 116 (step 804), and the submitted version The file path of the submitted version is set in the storage location 202 (step 805), and the value of the submitted version scan date 203 set in step 606 is transferred to the final submitted version file in the submitted version scan date 203 (step 806). .

  Thereafter, the preparation halfway information addition processing unit 115 creates a confirmation screen as shown in FIG. 9 based on the contents set in steps 804 to 806 and displays it on the screen of the display device 102 (step 807). On this confirmation screen, the title “Verification / registration confirmation of the version file being created” and the displayed file were determined to be a file in the middle of creation found around the final submitted version file. And a message explaining to the user.

  In addition, on this confirmation screen, “file name”, “submission version flag”, “creation version flag”, “submission version storage location”, and “submission version scan date / time” are also displayed. In the case of this form example, the path 900 of the currently focused file is also displayed in the “file name” column. Similarly, the setting contents 901 of the submitted version flag 200 registered in the version information data 116 are displayed in the “submitted version flag” column. In the case of FIG. 9, the setting contents are displayed by a black circle display on the NO side. Similarly, the setting contents 902 of the creation intermediate version flag 201 are displayed in the column of “creation intermediate version flag”. In the case of FIG. 9, the setting content is displayed by a black circle display on the YES side. Also, in the column of “submission version storage location”, a file path (setting contents of the submission version storage location 202) 903 corresponding to the currently focused file is displayed. In addition, the setting contents 904 of the submitted version scan date / time 203 is displayed in the column of “submission date scan date / time”. Based on these displays, the user confirms the validity of the determination content, and if necessary, executes a work for correcting the setting content on the confirmation screen.

  In addition to these, on the confirmation screen, as an operation button, a “Browse” button for confirming the contents of the file specified by the file name, and “Cancel” used for inputting an instruction to cancel registration of the displayed file are displayed. ”Button and a“ Register ”button used to input an instruction for registering the displayed file.

  If the “Cancel” button or “Register” button is operated in Step 807, or if it is determined that the file does not match in Step 803, the creation intermediate version information addition processing unit 115 takes over the processing from The halfway version determination processing unit 114 continues to crawl the file storage location 101 and focuses on the next file (step 808). Then, the process is repeated from step 802.

(1-5) Summary As described above, in the business document processing apparatus according to this embodiment, when the scanned image captured for the business document is stored in the data storage unit 101, the imprint extraction processing unit 111 scans the scanned image. The process of extracting the seal impression from Then, the submitted version determination processing unit 112 determines that the scanned image from which the seal impression has been extracted is the final submitted version. This determination procedure makes it possible to distinguish the final submitted version from other business documents with sufficient practical accuracy.

  In the business document processing apparatus according to the form example, an image obtained by removing the imprint image from the scan image determined to be the final submitted version (an imprint removal scan image) and the file storage location 101 within the setting range are read. The submitted version determination processing unit 112 executes a process for comparing the file data with the print image image, and determines that the file data corresponding to both is the file data corresponding to the final submitted version. With this processing operation, necessary electronic data (file data) can be easily found within an accessible file storage area.

  In addition, in the business document processing apparatus according to the form example, the file data determined to be the final submitted version is given at least metadata indicating that it is the final submitted version, and the confirmation screen is displayed on the screen, thereby determining It is possible to give the user an opportunity to confirm whether or not the result is correct. In addition, the determination result can be changed to the correct content as necessary.

  Further, in the business document processing apparatus according to the form example, the difference between the file name of the file data determined to be the final submitted version and the file name of each file data read from the storage area within the setting range is set in advance. If there are only items, the file data is determined to be an intermediate version. By this processing operation, it is possible to effectively find out the file data used in the process of creating the final submitted business document. By installing this function, file data that consumes unnecessary storage capacity can be easily deleted.

  Further, in the business document processing apparatus according to the embodiment, at least metadata indicating that the version is in the process of being created is added to the file data determined to be in the process of being created, and the confirmation screen is displayed on the screen, thereby determining It is possible to give the user an opportunity to confirm whether or not the result is correct. In addition, the determination result can be changed to the correct content as necessary.

  Also, in the business document processing apparatus according to the embodiment, the date and time when the file data of the final submitted version corresponding to the extracted file data is scanned among the file data to which the metadata indicating that the version is in the process of being created It is determined whether or not a set period or more has elapsed since. By installing this function, it is possible to automatically determine whether the document has a long time since the date and time when the business document was finally submitted, and the short document.

  In the business document processing apparatus according to the form example, a screen for confirming the file data of the pre-production version that has been determined that the predetermined period or more has passed with respect to the date and time when the file data of the final submitted version is scanned is displayed. indicate. By installing this function, it becomes possible to selectively delete file data that has become less necessary.

(2) Other Embodiments In the case of the above-described embodiment examples, the case where the file data determined to be in the process of being created is deleted by the function of the in-process version deletion processing unit 110 has been described. However, an operation for saving to the backup area instead of deleting may be mounted.

  Further, in the case of the above-described embodiment, a case has been described in which a confirmation screen as shown in FIG. 9 is displayed when file data of an in-progress version is found. That is, the case has been described where the setting contents are displayed on the screen every time one piece of file data determined to be in the middle of creation is found. However, as shown in FIG. 10, it is also possible to simultaneously display a plurality of halfway-created version file data found for one final submitted version file data in a list format on the screen. In the case of FIG. 10, the file data of the pre-production version found around the file of the final submission version is displayed in the display column 1000 in a list format. Incidentally, FIG. 10 shows a display example when the number of file data determined to be in the middle of creation exceeds the number that can be displayed in the display column 100. For this reason, a scroll bar is displayed on the right side of the display field 1000.

  In the case of this display format, the submitted version flag 1001, the intermediate version flag 1002, the path to the submitted version storage location (setting contents of the submitted version storage location 202) 1003, the submitted version scanning date and time (the setting contents of the submitted version scanning date and time 203) The display contents 1004 are all set to the same value.

  Further, in the case of the confirmation screen shown in FIG. 10, instead of the “reference” button (FIG. 9) for confirming the contents of the file data designated by the file name as the operation button, an “add” button, “edit” Button, "Delete" button is displayed. The “add” button is an operation button used when adding file data not included in the list. The “edit” button is an operation button used when changing the setting contents of specific file data in the list. The “delete” button is an operation button used when deleting specific file data from the list. Of course, a “Cancel” button and a “Register” button are also displayed on the confirmation screen.

  In the case of the above-described embodiment, the case where it is determined whether or not the file data is in the process of creation based on the comparison of the file storage location and the file name is illustrated. However, the file is created based on the text data (content). It may be determined whether the file data is an intermediate version. For example, a method for calculating a known alignment score, a method for examining the appearance frequency of a shared character string, or the like may be applied. In either case, the calculated value or detected value is compared with the threshold value, and if the degree of coincidence exceeding the threshold value is obtained (or if the difference between the two values is less than or equal to the threshold value), it is determined that the file data is in the process of being created. good.

  Further, in the case of the above-described embodiment, each of the submitted version processing unit 108, the in-progress version processing unit 109, and the in-progress version deletion processing unit 110 is realized as a function of a program executed by the central processing unit 105. Explained the case. However, this function can also be realized in hardware. Moreover, you may distribute in the state which stored all or one part of the said program in the storage medium. Further, all or a part of the program may be distributed in a communication or broadcast form via a network.

DESCRIPTION OF SYMBOLS 100 ... MFP 101 ... File storage location 102 ... Display device 103 ... Keyboard 104 ... Pointing device 105 ... Central processing unit 108 ... Submission version processing unit 109 ... Creation Intermediate version processing unit 110 ... Preparation intermediate version deletion processing unit 111 ... Seal imprint extraction processing unit 112 ... Submission version determination processing unit 113 ... Submission version information addition processing unit 114 ... Preparation intermediate version determination processing 115: Preproduction version information addition processing unit 106: Program memory 107: Data memory

Claims (14)

A data storage unit for storing scanned images captured for business documents;
An imprint extraction unit that performs an imprint extraction process on the scanned image;
A business document processing apparatus comprising: a submitted version determination unit that determines, when a seal imprint has been extracted, a scan image from which the seal imprint has been extracted as a scan image for the final submitted version. The submission version determination unit
A processing unit that generates an imprint removal scan image by removing an imprint image from the scan image for the final submitted version;
A processing unit that reads file data from a storage area within a setting range and generates a print image of each file data;
A comparison unit that sequentially compares the imprint removal scan image and the print image;
The business document processing apparatus according to claim 1, further comprising: a determination unit that determines that the file data corresponding to the print image that matches the imprint removal scan image is file data corresponding to the final submitted version. . The determination unit
The business document processing apparatus according to claim 2, wherein at least metadata indicating that the file is the final submission version is added to the file data determined to be the final submission version, and a confirmation screen is displayed on the screen. Difference between the file name or text data of the file data determined to be the final submitted version in the determination section and the comparison section that compares the file name or text data of each file data read from the storage area within the setting range 4. The business document processing apparatus according to claim 2, further comprising: an intermediate version determination unit including a determination unit that determines that the file data is an intermediate version when the file data is equal to or less than the set condition. The intermediate version determination unit
5. The business document processing apparatus according to claim 4, wherein at least metadata indicating that the version is in the process of being created is added to the file data determined to be in the process of being created, and a confirmation screen is displayed on the screen. Whether the processing unit that extracts the file data to which metadata indicating that it is in the process of being created has been added, and whether the file data of the final submitted version corresponding to the extracted file data has been scanned for a set period or more The business document processing apparatus according to claim 5, further comprising: a second intermediate version determination unit including a determination unit that determines whether or not. The second intermediate version determination unit
The screen for confirming the file data of the pre-production version that has been determined that the predetermined period or more has passed with respect to the date and time when the file data of the final submitted version was scanned is displayed. Business document processing device. A process of performing an imprint extraction process on a scanned image captured for a business document,
A program for causing a computer to execute a process of determining a scanned image from which an imprint has been extracted as a scanned image for the final submitted version when a stamp has been extracted. Processing to remove the imprint image from the scanned image for the final submitted version and generate an imprint removal scan image;
A process of reading file data from a storage area within a setting range and generating a print image of each file data;
A process of sequentially comparing the imprint removal scan image and the print image;
The program according to claim 8, wherein the computer executes processing for determining that the file data corresponding to the print image that matches the imprint removal scan image is the file data corresponding to the final submitted version. 10. The file data determined to be the final submitted version is given at least metadata indicating that it is the final submitted version, and causes the computer to execute a process of displaying a confirmation screen on the screen. Program. A process of comparing the file name or text data of the file data determined to be the final submission version with the file name or text data of each file data read from the storage area within the setting range;
The program according to claim 9 or 10, wherein if the difference between the two is equal to or less than a set condition, the computer executes a process of determining that the file data is an in-progress version. The file data determined to be in the process of being created is assigned at least metadata indicating that it is in the process of being created and causes the computer to execute a process for displaying a confirmation screen on the screen. Program. A process of extracting file data to which metadata indicating that the version is in the process of being created,
13. The program according to claim 12, further comprising: causing a computer to execute a process of determining whether or not a set period or more has elapsed from the date and time when the file data of the final submitted version corresponding to the extracted file data is scanned. . A feature that causes the computer to execute a process for displaying a screen for confirming the file data of the pre-production version that has been determined that the predetermined period or more has passed with respect to the date and time when the file data of the final submitted version was scanned The program according to claim 13.

Images