JP5072321B2 - Scan solution system - Google Patents

Description

  The present invention relates to a scan solution system capable of managing a paper document after output in a state of being related to business.

  FIG. 1 is a diagram showing an outline of form generation in a conventional form management system. In FIG. 1, the form management system creates a form template (including item layout information and data set information that dynamically generates data values by connecting to a data source) by an internal designer in advance. At the time of creation, a form is generated and output according to the form template.

On the other hand, in Patent Documents 1 and 3, a bar code is attached to a part of a document to be copied or transmitted by a copying machine or a facsimile machine, and reading the contents makes it easy for a user to set copying conditions and a transmission destination. Techniques to do this are disclosed. Patent Document 2 discloses a technique for extracting a barcode printed on a document.
JP 11-119597 A JP 2004-303223 A JP 2004-343564 A

  By the way, in a business that uses a form, the form is sent to the other party (by hand, sent by mail, sent by FAX, sent with a scan image attached to an e-mail, etc.), then returned after being corrected or added. Various processes such as inputting into the business system from the generated form and managing it as an original document continue.

  However, the above-described conventional form management system is specialized for form output, and the relation with the business after the form output has not been considered.

  On the other hand, none of the techniques disclosed in Patent Documents 1 to 3 are directed directly to form processing, and cannot solve the above problems.

  The present invention has been proposed in view of the above-described conventional problems, and an object of the present invention is to provide a scan solution system capable of managing a paper document after output in a state related to business. It is to provide.

In order to solve the above problems, according to the present invention, document data generating means for generating document data in which the first metadata is embedded based on a document template and a data source as described in claim 1 And printing means for printing the document data as a paper document; scanning the paper document that has undergone predetermined processing after printing to obtain a scanned image; and various information at the time of scanning as second metadata Scanning means to be acquired , a plurality of decoding means for decoding metadata from the scanned image and the second metadata, a metadata integrating means for integrating the decoding results of the plurality of decoding means, and an integrated metadata based on the data, with reference to the document template and a processing means for performing predetermined processing corresponding to the paper document scanning It is the gist of the solution system.

According to a second aspect of the present invention, document data generating means for generating document data in which the first metadata is embedded based on a document template and a data source, and printing means for printing the document data as a paper document Scanning means for acquiring a scanned image by scanning the paper document that has been subjected to predetermined processing after printing, and acquiring various information at the time of scanning as second metadata ; the scanned image and the second A plurality of decoding means for decoding the metadata from the metadata, a metadata integrating means for integrating the decoding results of the plurality of decoding means, and the above- mentioned document template based on the integrated metadata without referring to the document template A scan solution system comprising processing means for performing predetermined processing according to a paper document It is possible.

  According to a third aspect of the present invention, in the scan solution system according to the first or second aspect, a design means for designing the document template may be provided.

  Also, as described in claim 4, in the scan solution system according to claim 1 or 2, the document template includes layout information for designating a position of an item, and data to the data source. Data set information that dynamically generates data values by connection can be included, and embedded information that supports various embedded formats and can describe embedded metadata.

  Also, as described in claim 5, in the scan solution system according to claim 4, the embedding information includes a description indicating an encoding type, a description indicating an embedding location, and a description indicating a type of data to be embedded. , And a description indicating the embedded data itself.

  Further, as described in claims 6 and 7, it can be configured as a scan solution management apparatus.

  Further, as described in claims 8 and 9, it can be configured as a scan solution management method.

  In the scan solution system of the present invention, it is possible to manage the output paper document in a state where it is related to business.

  Hereinafter, preferred embodiments of the present invention will be described.

  FIG. 2 is a diagram showing a configuration example of the scan solution system of the present invention. In FIG. 2, the scan solution system includes a Web browser 1 as a client operated by a user, a form management system 2 that generates form data, a business system 3 that manages work including issuance and reception of forms, and a form. An MFP (Multi Function Printer) 4 that performs printing and scanning, and a scan data processing system 5 that performs predetermined processing based on scanned images and metadata (described later) distributed from the MFP 4.

The MFP 4 includes a printer unit 401 that prints a form, an operation panel 402 that is operated by a user, and a scan delivery unit 405 that scans the form and delivers a scanned image and metadata. The operation panel 402 includes a Web browser 403 that displays a UI (User Interface) screen and an embedded GUI (Graphical User Interface) 404. The scan distribution unit 405 includes a scanner unit 406 that scans a form, and a scanned image file using various information at the time of scanning (login user information, operation date and time, contents selected on the operation panel 402, IP address of the MFP 4, etc.) as metadata. Add to name or XML (eXtensible
A metadata adding unit 407 for adding a separate file such as Markup Language) and a data transmitting unit 408 for transmitting the scan image and metadata to the scan data processing system 5 are provided.

  The business system 3 includes a business UI providing unit 301 that provides a business UI, a logic processing unit 302 that performs data processing in accordance with logic according to the business content, and a data connection unit 303 for connecting to data storage inside and outside the system. And a data source 304 such as various databases, and a scan image storage unit 305 that accumulates scan images of forms.

  FIG. 3 is a diagram illustrating a configuration example of the form management system 2. In FIG. 3, the form management system 2 includes a form designer 201 that designs forms by operations of a business management user, a form management unit 205 that manages forms, and an embedded plug that embeds metadata into form images. IN 214, a metadata storage unit 215 that holds metadata embedded in the form image, and a form template storage unit 216 that holds a form template. The form designer 201 includes a UI providing unit 202 that provides a UI, a template creation unit 203 that creates a form template, a management unit calling unit 204 that calls the form management unit 205 in various inquiries and registration of the created form template, and the like. It has. The form management unit 205 includes a management service providing unit 206 that provides a form management service, a form image output unit 207 that outputs the generated form data in a format such as PDF (Portable Document File), and a form based on the form template. The template processing unit 208 that performs the generation process, the external resource connection unit 212 that connects to external resources in order to include external resource data in the form, and the form template created by the form designer 201 are stored in the form template storage unit 216. A template storage unit 213. The template processing unit 208 includes a data set processing unit 209 that processes a data set that is a source of data to be included in a form, a layout processing unit 210 that performs layout processing of each item of the form, and a two-dimensional barcode ( An embedding processing unit 211 for embedding data by various methods such as QR code.

FIG. 4 is a diagram illustrating a configuration example of the scan data processing system 5. In FIG. 4, the scan data processing system 5 includes a scan image / metadata receiving unit 501 that receives a scan image and metadata from the MFP 4, and decodes metadata that is embedded in the scan image or file name or added as a separate file. A metadata decode management unit 502 that manages the metadata, and various types of decoders such as a two-dimensional barcode decoder, barcode decoder, dot embedding decoder, file name metadata decoder, invisible decoder, and XML decoder And a metadata integration unit 504 that integrates metadata decoded by various decoders of the metadata decoder 503. The scan data processing system 5 includes a metadata processing unit 505 that performs predetermined processing corresponding to the integrated metadata, and BPEL (Business Process Execution Language) that actually executes the predetermined processing corresponding to the metadata. Plug-in, plug-in call plug-in, workflow plug-in, MFPUI (Multi
And a metadata processing plug-in 506 including various plug-ins such as a Function Printer User Interface) plug-in.

  5 to 8 are diagrams showing examples of configuration patterns of the scan solution system. FIG. 5 shows a basic configuration in which FIGS. In FIG. 6, a printer 6 for printing a form is provided separately from the MFP 4, and an embedded plug-in 214, a metadata storage unit 215, a form template storage unit 216, a data source 304, a scanned image storage unit 305, and a metadata decoder 503. The metadata processing plug-in 506 is separated from each system and placed in a separate system. FIG. 7 shows the scan data processing system 5 and the scan image storage unit 305 in FIG. In this case, since the scan data processing system 5 is in the MFP 4, it is possible to save the labor of server management, and the processing speed and operability can be improved when the scan image and the UI on the MFP 4 are closely related. FIG. 8 shows that the scan data processing system 5 is placed as one of the components in the business system 3 in FIG. In this case, overhead costs with the business system 3, such as authentication and network boundaries, can be reduced.

  FIG. 9 is a diagram illustrating an example of a form template managed in the form management system 2. In FIG. 9, the form template refers to data set information internally, layout information for specifying the position of an item, data set information for dynamically generating data values by connecting to a data source, It includes embedded information that supports an embedded format and can describe embedded metadata. The embedded information can also refer to the data set information.

  FIG. 10 is a diagram showing an example of layout information. The left side shows layout information, and the right side shows a corresponding form. In this example, the position corresponding to the form item a1 and the reference data set are described by a11 and a12, respectively, and the position corresponding to the form item a2 and the reference data set are described by a21 and a22, respectively.

  FIG. 11 is a diagram showing an example of data set information, a description b1 that refers to an external RDB (Relational Data Base), a description b3 that refers to an external XMLDB, and a description b2 that refers to a data set based on the description b3. An example including

  FIG. 12 is a diagram showing examples of embedding information. Descriptions c1 and c5 indicating the encoding type, descriptions c2 and c6 indicating the embedding location, and description c3 indicating the type of data to be embedded (ID, raw text, parameter, etc.) , C7 and descriptions c4 and c8 indicating the embedded data itself. The description c41 included in the embedded data c4 is a description that refers to the data set.

  13 to 16 are diagrams illustrating examples of data to be embedded included in the embedded information.

  FIG. 13 shows an example of data for calling a BPEL plug-in, and shows an example including a description d1 indicating a plug-in execution class and a description d2 indicating data for plug-in execution. The plug-in that has received this data performs processing according to the description d2 by the BPEL execution system.

  FIG. 14 shows an example of data for calling a plug-in with a SOAP (Simple Object Access Protocol) message, which includes a description d3 indicating the execution class of the plug-in and a description d4 indicating a SOAP message for executing the plug-in. An example is shown. The plug-in that has received this data functions as a SOAP message relay server.

  FIG. 15 shows an example of data for sequentially executing a plurality of plug-ins, and shows an example including a description d5 about the first plug-in and a description d6 about the second plug-in. . In this example, an image is stored in a document management system that can be connected by a repository document class using a first plug-in, and a BPEL plug-in that is a second plug-in is called. It is also possible to execute a plurality of plug-ins in parallel.

  FIG. 16 shows an example of embedding an ID, and shows an example including a description d7 indicating the ID and a description d8 indicating the location of the resource specified by the ID. In this case, the same data as in FIGS. 13 to 15 can be acquired by inquiring the value of the location of the description d8 using the ID of the description d7 as a key. Although the data to be embedded in the form is the minimum necessary data, the capacity may be insufficient depending on the embedding method. In such a case, the capacity shortage can be compensated by embedding only the ID.

  The operation of the above embodiment will be described below.

  FIG. 17 is a flowchart showing an example of processing for creating and saving a form template. In FIG. 17, the business management user activates the form designer 201 of the form management system 2 (step S101).

  The UI providing unit 202 of the form designer 201 inquires the management unit calling unit 204 about capabilities (details of functions) for creating a form template (step S102), and the management unit calling unit 204 sends an embedded plug to the form management unit 205. Inquires about information such as the type of in, settable parameters, connectable data source, and necessary parameters (step S103).

  The management service providing unit 206 of the form management unit 205 returns the inquired capability (step S104), the management unit calling unit 204 of the form designer 201 acquires the capability from the form management unit 205 (step S105), and provides the UI. The unit 202 generates a UI and presents it to the user (step S106). FIG. 18 is a diagram illustrating an example of an information embedding dialog as a UI. A radio button e1 for selecting an embedding method, a display e2 for referring to a data set, an area e3 for inputting embedded data, and an instruction to save or cancel In this example, the button e4 to be included is included.

  Returning to FIG. 17, the user inputs necessary information and saves (requests) the form template (step S107).

  The template creation unit 203 generates a form template (data) and makes a template storage request to the management service providing unit 206 of the form management unit 205 through the management unit calling unit 204 (step S108).

  The management service providing unit 206 makes an inquiry to the template processing unit 208 to check whether the generated form template can be processed normally (step S109).

  The template processing unit 208 checks whether the number of embedded characters has been exceeded or the connection with the data source has failed (step S110), and determines whether the form template is normal (step S111).

  If it is determined that the form template is normal, the template storage unit 213 stores the form template in the form template storage unit 216, and returns a registration completion message to the form designer 201 via the management service providing unit 206 (step). S112).

  If it is determined that the form template is not normal, an error message, a warning message, or a message suggesting another solution is generated and returned to the form designer 201 via the management service providing unit 206 (step S113).

  The user modifies the form template in accordance with the message and re-registers (step S114). If the amount of embedded data is too large, a dialog for changing to the reference method is created by the UI providing unit 202, corrected according to these instructions, and re-registered. FIG. 19 is a diagram illustrating an example of an information embedding dialog in a state where a message is displayed when the amount of embedded data is too large.

  20 to 23 are diagrams showing an outline of processing of the scan solution system after the form template is created.

  In FIG. 20, metadata is not embedded in the form image itself, but metadata is added when the form is scanned by the MFP 4.

  In FIG. 20, the normal user accesses the business system 3 from the Web browser 1 and instructs the output (printing) of the form, so that the form management system 2 controls the form template storage unit 216 under the control of the business system 3. Based on the stored form template and the data source 304, form data is generated and output (step S11).

  The form data is printed by the MFP 4 and the printer 6 via the Web browser 1 or the like or directly from the form management system 2 (step S12).

  The printed form is corrected and added as appropriate (step S13). This correction / addition may be performed at a place not far from the place where the form is printed, or may be performed after being sent to the other party by mail, personal delivery, FAX, or the like.

  Next, as a business flow after correction / addition, the form 4 is scanned by the MFP 4 (step S14).

  The MFP 4 obtains the scanned image of the form, and also logs in the scanned image using the login user information, operation date and time, contents selected on the operation panel 402 (including a template ID indicating the type of form), the IP address of the MFP 4, and the like as metadata. It is added to the file name or added as another file such as XML and distributed to the scan data processing system 5 (step S15).

  The scan data processing system 5 extracts metadata from the received data, and passes the metadata to the metadata processing plug-in 506 to perform predetermined processing (step S16). Here, an item extraction process plug-in for extracting an item from a scanned image according to the layout information of the form template and supporting input to the business system 3 and business processing including accumulation of the scanned image in the business system 3 are performed. An example of a business processing plug-in to be performed is shown.

  When it is necessary to refer to the form template in the metadata extraction / processing in the scan data processing system 5, an inquiry based on the template ID is made to the form management system 2 (step S17).

  FIG. 21 shows an example in which metadata is embedded in a form image.

  In FIG. 21, the normal user accesses the business system 3 from the Web browser 1 and instructs the output (printing) of the form, so that the form management system 2 controls the form template storage unit 216 under the control of the business system 3. Based on the stored form template and data source 304, form data is generated and metadata is generated. The embedded plug-in 214 embeds the metadata in the form image and outputs it (step S21).

  The form data is printed by the MFP 4 and the printer 6 via the Web browser 1 or the like or directly from the form management system 2 (step S22).

  The printed form is corrected and added as appropriate (step S23). This correction / addition may be performed at a place not far from the place where the form is printed, or may be performed after being sent to the other party by mail, personal delivery, FAX, or the like.

  Next, as a business flow after correction / addition, the form 4 is scanned by the MFP 4 (step S24).

  The MFP 4 obtains the scanned image of the form, and also logs in the scanned image using the login user information, operation date and time, contents selected on the operation panel 402 (including a template ID indicating the type of form), the IP address of the MFP 4, and the like as metadata. It is added to the file name or added as another file such as XML and distributed to the scan data processing system 5 (step S25).

  The scan data processing system 5 extracts metadata from the received data (scanned image file, file name, attached file, etc.) and passes the metadata to the metadata processing plug-in 506 to perform predetermined processing ( Step S26). Here, an item extraction process plug-in for extracting an item from a scanned image according to the layout information of the form template and supporting input to the business system 3 and business processing including accumulation of the scanned image in the business system 3 are performed. An example of a business processing plug-in to be performed is shown.

  When it is necessary to refer to the form template in the metadata extraction / processing in the scan data processing system 5, an inquiry based on the template ID is made to the form management system 2 (step S27).

  FIG. 22 shows an example applied across company A and company B without system connection, in which form layout information is embedded in the form image in addition to normal metadata.

  In FIG. 22, the normal user on the company A side accesses the business system 3 from the Web browser 1 and instructs the output (printing) of the form, so that the form management system 2 controls the form template under the control of the business system 3. Based on the form template stored in the storage unit 216 and the data source 304, form data is generated and metadata (including layout information) is generated, and the embedded plug-in 214 embeds the metadata in the form image. Output (step S31).

  The form data is printed by the MFP 4 and the printer 6 via the Web browser 1 or the like or directly from the form management system 2 (step S32).

  The printed form is sent from Company A to Company B by mail, personal delivery, FAX, etc., and is corrected and added as appropriate (step S33).

  Next, the company B scans the form by the MFP 4 as a business flow after correction / addition (step S34).

  The MFP 4 acquires the scanned image of the form, and adds the login user information, the operation date and time, the selection contents on the operation panel 402, the IP address of the MFP 4 and the like as metadata to the file name of the scanned image or as another file such as XML. Then, it is distributed to the scan data processing system 5 (step S35).

  The scan data processing system 5 extracts metadata including layout information from the received data (scanned image file, file name, attached file, etc.), and causes a predetermined process to be performed by a predetermined plug-in (step S36). Since the layout information of the form can be extracted, items can be cut out from the scanned image on the B company side without making an inquiry to the A company side.

  FIG. 23 shows an example applied across company A and company B that can be connected to the system, in which the form template ID is embedded as metadata in the form image.

  In FIG. 23, the normal user accesses the business system 3 from the Web browser 1 on the company A side and instructs the output (printing) of the form, so that the form management system 2 controls the form template under the control of the business system 3. Based on the form template and data source 304 stored in the storage unit 216, form data is generated and metadata is generated, and the embedded plug-in 214 embeds the metadata in the form image and outputs it (step S41). .

  The form data is printed by the MFP 4 and the printer 6 via the Web browser 1 or the like or directly from the form management system 2 (step S42).

  The printed form is sent from Company A to Company B by mail, personal delivery, FAX, etc., and is corrected and added as appropriate (step S43).

  Next, the company B scans the form by the MFP 4 as a business flow after correction / addition (step S44).

  The MFP 4 acquires the scanned image of the form, and adds the login user information, the operation date and time, the selection contents on the operation panel 402, the IP address of the MFP 4 and the like as metadata to the file name of the scanned image or as another file such as XML. Then, it is distributed to the scan data processing system 5 (step S45).

  The scan data processing system 5 extracts metadata from the received data (scanned image file, file name, attached file, etc.), and performs predetermined processing by a predetermined plug-in (step S46).

  When it is necessary to refer to the form template in the metadata extraction / processing in the scan data processing system 5, an inquiry based on the template ID is made to the form management system 2 of company A (step S47).

  FIG. 24 is a flowchart illustrating an example of a form creation process. In FIG. 24, the normal user logs in to the business system 3 via the Web browser 1 (step S201).

  When the user selects a form creation process from the UI, the logic processing unit 302 of the business system 3 passes the template ID and parameters, and requests the form management system 2 to output a form (step S202).

  The management service providing unit 206 of the form management system 2 acquires a form template from the form template storage unit 216 using the received template ID as a key (step S203).

  The management service providing unit 206 passes the template and parameters to the template processing unit 208 (step S204).

  The data set processing unit 209 of the template processing unit 208 connects to the data set described in the template via the external resource connection unit 212, and creates a necessary data set (step S205).

  The layout processing unit 210 of the template processing unit 208 creates a form image from the layout information and the data set (step S206).

  The embedding processing unit 211 of the template processing unit 208 generates embedding information from the data set and the embedding information, calls an appropriate embedding plug-in 214, and embeds data in the created image (step S207).

  At this time, it is determined whether or not the reference ID is embedded (step S208). If the reference ID is embedded, the template processing unit 208 automatically generates an ID by the generation method described in the template and uses it as a key. The embedded data is stored in the metadata storage unit 215. The generated ID is embedded in the form image (step S209).

  If the reference ID is not embedded, the template processing unit 208 embeds the embedded data as it is in the form image (step S210).

  Then, when the above processing is completed normally, the management service providing unit 206 passes the form image to the form image output unit 207, returns the image in the requested format to the logic processing unit 302 of the business system 3, and there is an abnormality. If so, an error is returned (step S211).

  The logic processing unit 302 provides a form image to the user via the business UI providing unit 301 (step S212), and the user prints the form image from the printer by a print operation (step S213).

  FIG. 25 is a flowchart showing an example of scan of a form and processing of scan data. FIG. 26 is a diagram showing the flow of processing in the scan data processing system 5.

  In FIG. 25, when the user scans a form (paper) with the MFP 4 (step S301), the metadata adding unit 407 of the MFP 4 adds appropriate metadata at the time of scanning (step S302). Depending on the system, the scan logic is provided from the business system, and the added data can be customized.

  The data transmission unit 408 of the MFP 4 transmits the scan image + metadata to the scan data processing system 5 (step S303). Note that the transmission destination may be described in the metadata or may be set by the system.

  The scanned image / metadata receiving unit 501 of the scan data processing system 5 receives the image and metadata from the MFP 4 (step S304).

  The metadata decode management unit 502 executes the registered metadata decoder 503 (step S305).

  The metadata decoder 503 acquires metadata from various sources such as an image, a file, and a file name (step S306).

  At this time, it is determined whether or not the metadata is a reference ID (step S307). If the metadata is a reference ID, the metadata decoder 503 inquires the metadata itself to the external resource using the ID as a key (step S308).

  Thereafter, the metadata integration unit 504 integrates each metadata acquired from the metadata decoder 503 (step S309).

  Then, the metadata processing unit 505 extracts a part related to plug-in processing from the integrated metadata, and executes an appropriate metadata processing plug-in 506 (step S310).

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

It is a figure which shows the outline | summary of the form production | generation in the conventional form management system. It is a figure which shows the structural example of the scan solution system of this invention. It is a figure which shows the structural example of a form management system. It is a figure which shows the structural example of a scan data processing system. FIG. 2 is a diagram (part 1) illustrating an example of a configuration pattern of a scan solution system. FIG. 6 is a second diagram illustrating an example of a configuration pattern of a scan solution system. FIG. 10 is a third diagram illustrating an exemplary configuration pattern of a scan solution system. FIG. 6 is a diagram (part 4) illustrating an example of a configuration pattern of a scan solution system; It is a figure which shows the example of a form template. It is a figure which shows the example of layout information. It is a figure which shows the example of data set information. It is a figure which shows the example of embedding information. FIG. 6 is a diagram (part 1) illustrating an example of data to be embedded. It is a figure (the 2) which shows the example of the data to embed. FIG. 11 is a third diagram illustrating an example of data to be embedded; FIG. 10 is a diagram (part 4) illustrating an example of data to be embedded; It is a flowchart which shows the example of a process of preparation and preservation | save of a form template. FIG. 10 is a diagram (part 1) illustrating an example of an information embedding dialog. FIG. 10 illustrates an example of an information embedding dialog (part 2); It is FIG. (1) which shows the outline | summary of a process of a scan solution system. FIG. 5 is a diagram (part 2) illustrating an overview of processing of a scan solution system. FIG. 11 is a diagram (part 3) illustrating an overview of the process of the scan solution system. FIG. 6 is a diagram (part 4) illustrating an overview of processing of a scan solution system. It is a flowchart which shows the example of a process of form creation. 10 is a flowchart illustrating an example of a form scan and scan data processing. It is a figure which shows the flow of a process in a scan data processing system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Web browser 2 Form management system 201 Form designer 202 UI provision part 203 Template creation part 204 Management part calling part 205 Form management part 206 Management service provision part 207 Form image output part 208 Template processing part 209 Data set processing part 210 Layout processing part 211 Embedded processing unit 212 External resource connection unit 213 Template storage unit 214 Embedded plug-in 215 Metadata storage unit 216 Form template storage unit 3 Business system 301 Business UI provision unit 302 Logic processing unit 303 Data connection unit 304 Data source 305 Scan image storage Part 4 MFP
401 Printer 402 Operation Panel 403 Web Browser 404 Embedded GUI
405 Scan distribution unit 406 Scanner unit 407 Metadata addition unit 408 Data transmission unit 5 Scan data processing system 501 Scan image / metadata reception unit 502 Metadata decode management unit 503 Metadata decoder 504 Metadata integration unit 505 Metadata processing unit 506 Metadata processing plug-in 6 Printer

Claims (9)

Document data generation means for generating document data in which the first metadata is embedded based on the document template and the data source;
Printing means for printing the document data as a paper document;
Scanning means for scanning the paper document that has undergone predetermined processing after printing to obtain a scanned image, and obtaining various types of information at the time of scanning as second metadata;
A plurality of decoding means for decoding metadata from the scanned image and the second metadata;
Metadata integration means for integrating the decoding results of the plurality of decoding means;
A scan solution system comprising processing means for performing predetermined processing according to the paper document with reference to the document template based on the integrated metadata . Document data generation means for generating document data in which the first metadata is embedded based on the document template and the data source;
Printing means for printing the document data as a paper document;
Scanning means for scanning the paper document that has undergone predetermined processing after printing to obtain a scanned image, and obtaining various types of information at the time of scanning as second metadata;
A plurality of decoding means for decoding metadata from the scanned image and the second metadata;
Metadata integration means for integrating the decoding results of the plurality of decoding means;
A scan solution system comprising: processing means for performing predetermined processing according to the paper document without referring to the document template based on the integrated metadata . In the scanning solution system according to claim 1 or 2,
A scan solution system comprising a design means for designing the document template. In the scanning solution system according to claim 1 or 2,
The above document template
Layout information to specify the position of the item,
Data set information to dynamically generate data values by connecting to the data source,
A scan solution system that supports various embedding formats and includes embedding information that can describe embedding metadata. The scan solution system according to claim 4,
The above embedded information
A description indicating the encoding type,
A description indicating where to embed,
A description indicating the type of data to be embedded,
A scan solution system including a description indicating the embedded data itself. Based on the document template and the data source, the document data is printed from the document data in which the first metadata is embedded, and after the printing, a paper document is scanned to obtain a scanned image, and various information at the time of scanning is also obtained. Scanning means for obtaining second metadata;
A plurality of decoding means for decoding metadata from the scanned image and the second metadata;
Metadata integration means for integrating the decoding results of the plurality of decoding means;
A scan solution management apparatus comprising processing means for performing predetermined processing according to the paper document with reference to the document template based on the integrated metadata . Based on the document template and the data source, the document data is printed from the document data in which the first metadata is embedded, and after the printing, a paper document is scanned to obtain a scanned image, and various information at the time of scanning is also obtained. Scanning means for obtaining second metadata;
A plurality of decoding means for decoding metadata from the scanned image and the second metadata;
Metadata integration means for integrating the decoding results of the plurality of decoding means;
A scan solution management apparatus comprising: processing means for performing predetermined processing according to the paper document without referring to the document template based on the integrated metadata . Based on the document template and the data source, the document data is printed from the document data in which the first metadata is embedded, and after the printing, a paper document is scanned to obtain a scanned image, and various information at the time of scanning is also obtained. A scanning process to be acquired as second metadata;
A plurality of decoding steps for decoding metadata from the scanned image and the second metadata;
A metadata integration process for integrating the decoding results of the plurality of decoding processes;
A scan solution management method comprising: a processing step of performing predetermined processing according to the paper document with reference to the document template based on the integrated metadata . Based on the document template and the data source, the document data is printed from the document data in which the first metadata is embedded, and after the printing, a paper document is scanned to obtain a scanned image, and various information at the time of scanning is also obtained. A scanning process to be acquired as second metadata;
A plurality of decoding steps for decoding metadata from the scanned image and the second metadata;
A metadata integration process for integrating the decoding results of the plurality of decoding processes;
A scan solution management method comprising: a processing step for performing a predetermined process according to the paper document without referring to the document template based on the integrated metadata .

Images