WO2017029987A1

WO2017029987A1 - Print data management system, information processing device, and program and method for acquiring print data

Info

Publication number: WO2017029987A1
Application number: PCT/JP2016/072737
Authority: WO
Inventors: 満堀籠
Original assignee: 株式会社スプラインネットワーク
Priority date: 2015-08-19
Filing date: 2016-08-03
Publication date: 2017-02-23
Also published as: JP2017041073A

Abstract

The present invention relates to a print data management system by which printed document data are reliably collected into a server. The information processing device of the print data management system has: a spool data format specification means for specifying, upon receiving a print command, a spool data format of document data to be printed from among printer drivers of an output destination printer; a spool data acquisition means for acquiring the spool data and attribute information of the spool data from a spooler; a text extraction means for extracting text data from the acquired spool data; a spool data conversion means for converting the acquired spool data into a predetermined data format; and a transmission control means for controlling transmission of print data converted into the predetermined data format, the text data, and the attribute data. A print data management server of the print data management system is equipped with: a reception means for receiving the print data, the text data, and the attribute data; and a print data storage means for storing the print data, the text data, and the attribute data.

Description

Print data management system, information processing apparatus, print data acquisition program, and method

The present invention relates to a print data management system that reliably collects printed document data at a server.

In recent years, with the development of computer systems and computer networks, many documents are often handled as electronic data, and confidential information is also digitized and stored on servers. Companies and government agencies are taking measures against information leakage, such as setting passwords for confidential information and limiting who can access it. However, there are cases where such electronic confidential documents are printed out and taken out.

By the way, in Patent Document 1, the file name is acquired from the postscript image data of the document data subjected to the printing process, the stored file is read out, sent to the server together with the postscript image data, and the printing process is executed. It has been proposed that registered documents be registered on the server.

Japanese Patent Laid-Open No. 2005-141402

However, in the method described in Patent Document 1, the file name must be described somewhere in the document to be printed, and the document data for which the file name is not described is the document data even if the printing process is performed. Cannot be acquired, and all print data cannot be registered. Furthermore, since it is necessary to always include the file name in the document data, the burden on the user is large.

Also, the method described in Patent Document 1 has a problem in that it cannot be determined whether printing has actually been performed because date information and user name of printing cannot be acquired. In addition, there is a problem that data cannot be collected unless the user inserts the file name into the document data.

An object of the present invention is to reliably acquire a print-processed document on a server without a burden on a client-side user.

In the information processing apparatus for outputting print data to a printer according to the present invention, when there is a print instruction, the spool data format of the document data instructed to be printed is designated in the desired spool data format in the printer driver of the output destination printer. Spool data format designating means, spool data obtaining means for obtaining spool data in the designated spool data format and spool data attribute information from the spooler, and text extracting means for extracting text data from the obtained spool data An information processing apparatus having transmission control means for controlling to transmit at least text data and attribute information is provided.

Further, in a print data acquisition program that is applied to a computer that outputs print data to be printed by a printer according to the present invention and acquires the print data, the spool data format of the document data instructed to be printed is output when a print instruction is issued. A spool data format specifying step for specifying the desired spool data format in the printer driver of the previous printer, and a spool data acquiring step for acquiring spool data in the specified spool data format and spool data attribute information from the spooler; A print data acquisition program is provided that executes a text extraction step for extracting text data from acquired spool data, and a transmission control step for controlling to transmit at least text data and attribute information.

Furthermore, the present invention is a print data acquisition method that is applied to a computer that outputs print data to be printed by a printer according to the present invention, and that acquires print data. When there is a print instruction, the spool data format of the document data instructed to be printed is output to A spool data format specifying step for specifying a desired spool data format in the printer driver of the printer, a spool data acquiring step for acquiring spool data in the specified spool data format and spool data attribute information from the spooler, and There is provided a print data acquisition method characterized by executing a text extraction step for extracting text data from acquired spool data, and a transmission control step for controlling to transmit at least text data and attribute information.

A print data management system having an information processing apparatus that outputs print data to a printer and a print data management server that manages the print data. Spool data format specifying means for specifying the desired spool data format in the printer driver of the output destination printer, spool data in the specified spool data format, and attribute information of the spool data from the spooler. A print data management server having spool data acquisition means for acquiring, text extraction means for extracting text data from the acquired spool data, and transmission control means for controlling to transmit at least text data and attribute information; Receive print data, text data and attribute information Receiving means that provides a print data, and text data, a print data storing means for storing the attribute information, the print data management system comprising a.

According to the present invention, since the spool data is acquired from the spooler every time a print instruction is issued by the application, the print data can be collected without any special operation by the user. In addition, since attribute information such as the print date and time of the print data and the user name can be stored in association with the print data, it is possible to verify at a later date who performed the print processing.

In addition, this print data acquisition program can reliably acquire print data regardless of the printer model, regardless of the printer processing. The acquired spool data is converted into a predetermined data format, text information is extracted, and the print data and text information in the predetermined data format are transmitted to the print data management server. The correct print data can be acquired by the management server.

Furthermore, according to the present invention, since the print acquisition program is also started when the application is started, the print data can be acquired immediately after installing the print acquisition program.

FIG. 1 is a diagram showing an example of the configuration of a print data management system according to the present invention. FIG. 2 is a diagram showing an example of a hardware configuration diagram of the client PC 120 according to the present invention. FIG. 3 is a functional block diagram of the print data acquisition program according to the present invention. FIG. 4 is a diagram showing an example of a functional block diagram of the client PC in the printing process according to the first embodiment of the present invention. FIG. 5 is an example of a flowchart for explaining a print data acquisition method in print processing according to the first embodiment of the present invention. FIG. 6 is a diagram showing an example of print data attribute information in the present invention. FIG. 7 is a diagram showing an example of functional blocks of the print data management server in the present invention. FIG. 8 is a diagram illustrating an example of a functional block diagram of the client PC in the printing process according to the second embodiment of the present invention. FIG. 9 is an example of a flowchart for explaining a print data acquisition method in print processing according to the second embodiment of the present invention.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of a print data management system according to the present invention. In the print data management system, for example, the print data management server 110 and the

client PCs

120a and 120b, the printer A 130a, and the printer B 130b are connected via the network 100, for example. The network 100 may be any network form such as the Internet, a LAN, and a WAN regardless of wired or wireless.

The print data management server 110 is a server that receives, saves, and manages print data, which is a document printed by each client PC, from each client PC. Print data transmitted from the client PC, text information included in the print data, and attribute information thereof are stored in a storage unit such as a database in association with each other. The print data management server 110 does not have to be a single server device, and may be configured by being distributed to a plurality of servers.

The client PCs 120a and 120b accept user operations, create various document data using applications such as document creation software and table creation software that operate on an operating system such as Windows (registered trademark), and add and modify the data. PC (personal computer) that can be an information processing apparatus. For example, printer programs for printing with the printer A 130a and the printer B 130b are installed in the

client PCs

120a and 120b, and the user operates on the application and selects the printer, so that the corresponding printer is selected. The printer program is activated, and the printer A 130a or the printer B 130b can print the document data desired by the user. In addition, a print data acquisition program is installed in the

client PCs

120a and 120b, and the print data acquisition program acquires print data in the middle of print processing regardless of which printer the print data is printed on. The acquired print data is sent to the print data management server 110. The number of client PCs (information processing devices) is not limited to two, and a plurality of client PCs are connected to the network.

The printer A 130a and the printer B 130b receive the document data for which a print instruction has been received in the client PC as print data, and print it out. The printer may be an apparatus having a plurality of functions such as a copier and a FAX apparatus as well as an apparatus having a function of a single printer.

FIG. 2 is a diagram showing an example of a hardware configuration diagram of the client PC 120 according to the present invention. In FIG. 2, the information processing apparatus configuring the client PC 120 includes a CPU 211, a ROM 212, a RAM 213, an external interface 214, a communication interface 215, an input / output interface 216, and a storage device 217 that are connected to each other via a bus. The CPU 211 reads the application 230, operating system (OS) 240, printer program 250, and print data acquisition program 260 from the storage device 217 and executes them.

The ROM 212 stores, for example, a BIOS and a start program, and the RAM 213 operates as a memory that temporarily stores data necessary as a work memory when the CPU executes each process.

The external interface 214 is an interface for mounting a USB cable or a storage medium 218. The storage medium 218 is a recording medium such as a USB memory or an optical disk. The communication interface 215 is an interface for connecting a LAN card or an Internet cable, and is connected to the printer 130 and the print data management server 110 via the network 100. In response to an instruction from the CPU 211, the print data is transmitted to the printer 130 and the print data management server 110.

The input / output interface 216 is an interface such as a mouse 219, a keyboard 220, and a display 221 that accepts an operation instruction from a user and outputs a processing result based on the operation instruction. Note that the present invention is not limited thereto, and a touch panel, a speaker, a microphone, and the like may be connected.

The storage device 217 is a hard disk or flash memory, and stores an application 230, an operating system 240, a printer program 250, and a print data acquisition program 260. The application 230 is a software program such as document creation software, spreadsheet software, or presentation creation software. The operating system 240 is also called an OS, and is Windows (registered trademark), Linux (registered trademark), or the like. The printer program 250 is a program for printing electronic data such as document data with a printer, and stores the printer program of each connected printer. The print data acquisition program 260 is a program according to the present invention, which acquires spool data to obtain print data, text information, and data, regardless of which printer prints data instructed to be printed by the application. This program acquires attribute information.

Examples of the storage medium 218 include a removable medium such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory. The print data acquisition program is stored in these removable media or downloaded from a server (not shown). The print data acquisition program is distributed, stored in the storage device 217, and executed by the CPU 211 to execute various functions. Let

FIG. 3 is a functional block diagram of the print data acquisition program according to the present invention. As shown in FIG. 3, the print data acquisition program 260 includes a spool data format designation unit 261, a spool data acquisition unit 262, a text extraction unit 263, a spool data conversion unit 264, a print data transmission control unit 265, a registry writing unit 266, A function rewriting unit 267 is provided.

When there is a print instruction for the data created by the application, the spool data format designation unit 261 changes the spool data format of the data in the printer driver of the output destination printer designated to be the desired spool data format. specify. In other words, the print data acquisition program forcibly specifies the desired spool data format regardless of the spool data format set by each printer driver. In the present invention, the spool data format is designated as the EMF data format in the designated output destination printer driver. Here, the EMF data format is used. However, the EMF data format is not limited to the EMF, and the data format does not depend on the printer model, that is, the data format does not depend on the printer and can be processed by the designated printer driver. A spool data format may be used. When the application receives a print instruction, the spool data format specification unit 261 always calls the spool data format specification unit 261 regardless of what printer is instructed by rewriting the function address. Further, when the EMF data format is specified in the printer driver, the spool data format specifying unit 261 returns it to the GDI. The spool data format designation unit 261 mediates exchange between the GDI and the printer driver, except for setting EMF data in the printer driver. Note that when the XPS spool is also supported, the spool data format designating unit 261 designates the spool data format only in the case of GDI print processing, and therefore does not perform any processing on the XPS spool.

The spool data acquisition unit 262 acquires spool data in the designated spool data format and attribute information of the spool data from the spooler. Specifically, the spool data acquisition unit 262 acquires the spool file originally sent from the spooler to the print processor together with the attribute information of the spool data sent simultaneously with the spool file. The spool data acquisition unit 262 acquires the spool data and the attribute information of the spool data by rewriting the function address so that the function address for accessing the print processor from the spooler is accessed to the spool data acquisition unit. The spool data acquisition unit 262 mediates the exchange between the print processor and the spooler, except for acquiring spool data and attribute information. The attribute information is information including the file name, user name, machine name, printing date and time of the data to be printed, and is information that can be acquired from the spooler together with the spool data, and is provided as a metafile in XML data format or the like. Is done. Further, the spool data acquisition unit 262 determines the spool data format of the received spool data. Specifically, it is determined whether or not the specified spool data format (for example, EMF data) is used. Whether it is EMF data is determined by checking the data format. In the case of dealing with XPS data, whether the data is XPS data is determined by reading the data as XPS data and determining whether the data can be opened.

The text extraction unit 263 extracts text information from the spool data acquired by the spool data acquisition unit 262. The text extraction unit 263 may extract not only text information included in the spool data but also image data. The text information may be extracted not only from the spool data but also from the attribute information. In accordance with the spool data format determined by the spool data acquisition unit 262, the text extraction unit 263 performs text data extraction processing from EMF data if it is EMF data, and text data extraction processing from XPS data if it is XPS data. I do.

The spool data conversion unit 264 converts the spool data acquired by the spool data acquisition unit 262 into a predetermined data format. Since the spool data is data generated in the middle of the printing process of the data for which the print instruction has been received, the original document data may not be reproduced without being garbled by another information processing apparatus. Therefore, the spool data conversion unit 264 converts the acquired spool data (for example, EMF data) into a predetermined data format to obtain print data. The predetermined data format is a data format that can be reproduced by any information processing apparatus, for example, PDF or XPS. In XPS printing, spool data is not converted because XPS is spool data.

The print data transmission control unit 265, if there is print data converted into a predetermined data format by the spool data conversion unit 264, converted data, text data extracted from the spool data by the text extraction unit 263, and a spool data acquisition unit The communication interface 215 controls to transmit the attribute information acquired by the H.262 to the print data management server 110 via the network 100.

The registry writing unit 266 writes the name of the function rewriting unit 267 in the registry related to the module loaded when the application is activated. By writing the name of the function rewriting unit in the registry of the module loaded at the time of starting the application, the function rewriting unit 267 is surely started at the time of starting the application, and a predetermined function address is rewritten. 261 and the spool data acquisition unit 262 are accessed. For example, when Windows (registered trademark) is an OS, the registry writing unit 266 writes the program module name (DLL name) of the function rewriting unit 267 in the APPInit_DLLs registry. This is because, in Windows (registered trademark), when it is registered in the APPInit_DLLs registry, a module registered in the APPInit_DLLs registry is forcibly loaded when the application is started. When the print data acquisition program 260 is installed in the information processing apparatus, the program module name of the function rewriting unit 267 is written in the registry relating to the module loaded when the application is activated. Since it is a simple process that simply writes the module name, the print data can be acquired by the management server immediately after the program is installed.

The function rewriting unit 267 rewrites a predetermined function address related to printing when the application is activated. Since the registry writing unit 266 writes the program module name of the function rewriting unit 267 in the registry loaded when the application is started, the function rewriting program is started and printed by loading the registry when the application is started. Rewrite the predetermined function address for. Specifically, the function rewriting unit 267 rewrites the function address for the GDI to access the printer driver so as to call the spool data format specifying unit 261, and the function address for the spooler to call the print processor. The function address is rewritten so as to call the print data acquisition unit 262. In this way, the print data acquisition unit can acquire all the spool data and attribute information sent to the print processor.

(First embodiment)
In the first embodiment, a case will be described in which only a GDI printer driver is installed in a client PC. In the case of a GDI printer driver, spooling is performed using an EMF or RAW spool.
FIG. 4 is a diagram showing an example of a functional block diagram of the client PC in the printing process according to the first embodiment of the present invention. The client PC 120 includes an application 230, a printer program 250, and a print data acquisition program 260 that operate on a Windows (registered trademark) operating system (OS) 240. Although only one printer program is shown here, when a plurality of printer programs are installed, the client PC 120 has a plurality of printer programs.

The application 230 is, for example, a document creation software, a table creation software, an image creation software, a presentation software, an email software, etc., and is a program that creates document data having characters, images, and the like. When the user instructs the application 230 to print document data, print data is generated.

The operating system (OS) includes a GDI (Graphics Device Interface) 241, a spooler 242, a print provider 243, a language monitor 244, and a port monitor 245. When the print data acquisition program of the present invention is installed in the information processing apparatus, a predetermined function address related to printing is rewritten when the application is started, and the OS can execute the spool data format designation unit 261 of the print data acquisition program or the spool. The data acquisition unit 262 is accessed. Accordingly, when the application receives a print instruction from the user, the GDI 241 is called by the application 230 and accesses the spool data format designation unit 261 according to the rewritten function address. The spool data format designation unit 261 forcibly designates the spool data format in the printer driver 251 and returns the designated spool data format to the GDI 241. Therefore, the GDI 241 generates spool data in the designated spool data format.

Here, the spool data format is a spool data format determined by spooling when printing document data, and examples of spooling using GDI include RAW spooling and EMF spooling. . RAW spooling is a method of converting data into spool data that is optimal for the printer and spooling the data. Although it depends on the individual printer model, it takes a long time to release the application from the printing process. EMF spooling is a method of spooling with EMF data that does not depend on the printer model, and then generating and printing print data unique to the printer, and can release an application from print processing at an early stage. .

In the present invention, the registry writing unit 266 writes the name of the function rewriting unit 267 in the registry related to the module loaded when the application is activated when the print data acquisition program is installed. Therefore, when the application is activated, the function rewriting unit 267 rewrites all the function addresses that the GDI 241 calls the printer driver 251 to call the spool data format specifying unit 261. Accordingly, the spool data format designation unit 261 is always called, and the spool data format is designated in the printer driver and returned to the GDI 241, for example, so that the spool data format is the same regardless of which printer is used for printing. The spool data format specified by the spool data format specifying unit 261 is used. The GDI 241 generates spool data in a designated spool data format (for example, EMF data) and sends it to the spooler 242.

When the spool data of the document data is all spooled, the spooler 242 notifies the print processor of the designated printer that it is despooled. At this time, since the function rewriting unit 267 rewrites the function address for accessing the print processor so as to access the spool data acquisition unit 262 when the application is started, even when spooling is performed by the print processor of any printer. The spooler 242 always accesses the spool data acquisition unit 262. The spool data acquisition unit 262 acquires spool data and attribute information sent to the print processor of the printer designated by the spooler 242, and then the spool data acquisition unit 262 spools the spool data to the print processor of the designated printer. Send data and attribute information.

The print provider 243 performs processing for switching the output destination of the print data. For example, if the designated printer is a local printer, it is set to output to the local printer, and if it is a printer shared on the network, it is set to output to the network shared printer. In the processing of the print provider 243, spool data is sent from the spooler 242, spool data is reproduced by the print processor 252, spool data reproduced by the GDI 241 is drawn, and the printer driver 251 uses a printer model-dependent data format (RAW This is done after being converted to (data).

The language monitor 244 transmits / receives print status data to / from the printer. If necessary, processing such as printer job command control is performed on the print data. The port monitor 245 performs output processing for print data according to the type of printer port (USB, TCP / IP, etc.).

The spool file 300 is data generated by the GDI 241 and includes spool data and attribute information data. The spool data is data of document data to be printed, and the attribute information data includes attribute information related to the document data to be printed, for example, the printing date and time, the file name of the document data, and the user name. In this embodiment, since the spool data format designation unit 261 always designates a predetermined spool data format (for example, EMF data), the spool designated by the spool data format designation unit 261 is used for any printer. Spooled in data format.

The print data acquisition program 260 includes a spool data format designation unit 261, a spool data acquisition unit 262, a text extraction unit 263, a spool data conversion unit 264, and a print data transmission control unit 265. In order to facilitate understanding of the printing process, the registry writing unit 266 and the function rewriting unit 267 are not shown, but these are also installed in the client PC 260 as a part of the print data acquisition program 260. When the print data acquisition program 260 is installed, the registry writing unit 266 writes the name of the function rewriting unit 267 in the registry related to the module loaded when the application is activated. The spool data format designation unit 261 accesses the spool data format designation unit 261 because the function rewriting unit 267 rewrites a function address related to predetermined printing when the application is activated. The spool data format designating unit 261 designates a bit for designating a spool data format in the printer driver of the designated printer that the GDI 241 should have accessed to designate a predetermined spool data format, so that the GDI 241 Returns the specified spool data format. The spool data format designation unit 261 forcibly designates the spool data format within the printer driver. When there is other processing between the GDI 241 and the printer driver 251, the spool data format designation unit 261 performs mediation.

The spool data acquisition unit 262 acquires the spool file 300 sent from the spooler 242. Since the function rewriting unit 267 rewrites the function address when the spooler 242 sends the spool file to the print processor 252 when the application is activated, the spooler 242 sends the spool file 300 regardless of which printer is specified. Therefore, the spool data acquisition unit 262 is accessed. The spool data acquisition unit 262 acquires spool data and attribute information included in the spool file 300. The spool data is document data expressed in a predetermined spool data format. The attribute information is information relating to document data to be printed, such as the printing date and time, the file name of the document data to be printed, and the name of the user who performed printing. The spool data acquisition unit 262 performs only mediation when there is other processing between the spooler 242 and the print processor 252 except for acquiring the spool file 300 sent from the spooler 242. The spool data acquisition unit 262 determines the data format of the acquired spool data. Specifically, it is determined whether the data format is EMF. When it is confirmed that the data is EMF data, the spool data acquisition unit 262 sends the acquired spool data (EMF data) and attribute information to the text extraction unit 263.

The text extraction unit 263 extracts text data from the spool data acquired by the spool data acquisition unit 262. The text extraction unit 263 may extract not only text information but also image data and the like. Since the text data is extracted by the same device as the device that generated the EMF data, the text data can be reliably extracted without causing problems such as garbled characters.

The spool data conversion unit 264 converts the spool data acquired by the spool data acquisition unit 262 into a predetermined data format. The predetermined data format is, for example, PDF data or XPS data, but any data format may be used as long as it does not cause garbled characters or errors in any information processing apparatus. By converting the spool data into such a data format and then sending it to the print data management server, the contents and mode of the printed document data can be reliably acquired.

The print data transmission control unit 265 performs print data management on attribute information acquired by the print data acquisition unit 262, text information extracted by the text extraction unit 263, and print data in a predetermined data format converted by the spool data conversion unit. Control transmission to the server via the network.

The printer program 250 includes a printer driver 251 and a print processor 252. The printer driver 251 stores print data format setting information, and generates printer-specific print data. The print processor 252 reproduces the print data (EMF data in the present embodiment) sent from the spooler 242 and performs, for example, editing processing such as aggregation and bookbinding for each page of the print document.

FIG. 5 is an example of a flowchart for explaining a print data acquisition method in print processing according to the first embodiment of the present invention. When the user selects an application such as document creation software or image creation software, the selected application is activated on the OS of the client PC (step S501).

At the same time when the application is activated, the function rewriting unit 267 is activated and rewrites a predetermined function address (step S502). When the print data acquisition program is installed in the client PC, the registry writing unit 266 stores the function rewriting unit 267 in the registry of the module loaded when the application is activated so that the function rewriting unit 267 is activated at the same time as the application is activated. This is because the module name is written. Specifically, the module name of the function rewriting unit 267 is written in the APPInit_DLLs registry by the registry writing unit 266 when the print data acquisition program is installed. One of the predetermined function addresses is a function address related to a process in which the GDI 241 calls the printer driver 251 in order to inquire about the spool data format. For example, the function address of a function such as LoadLibrary () API or DrvEnableDriver () API is used as the printer address. Rewriting from the driver 251 to the spool data format designation unit 261. The other is a function address related to processing that the spooler 242 calls to send the spool file 300 to the print processor 252. For example, OpenPrintProcessor () API, PrintDocumentOnPrintProcessor () API, ClosePrintProcessor () API, ControlPrintProcessor () API, etc. The function address of the function is rewritten from the print processor 252 to the spool data acquisition unit 262.

Next, the application receives a print instruction from the user using a mouse, a keyboard, or the like (step S503). For example, the user selects “print” from the application menu, selects a printer to print, the number of sheets, the output paper size, and the like, and executes a print instruction. Next, when the application receives a print instruction, the GDI 241 refers to the registry in order to access the printer driver that is the print instruction target (step S504). The GDI 241 calls the spool data format designation unit 261 to use the designated printer driver (step S505). As described above, all the function addresses (for example, LoadLibrary () API and DrvEnableDriver () API) for the function rewriting unit 267 to access the printer driver 251 from the GDI 241 are rewritten to access the spool data format specifying unit 261. Therefore, regardless of which printer driver is called, the spool data format designation unit 261 is called.

The spool data format designation unit 261 calls the printer driver 251 (step S506). A printer driver activation command or the like from the GDI 241 is transmitted to the printer driver 251 via the spool data format designation unit 261. Further, the spool data format specifying unit 261 calls the printer driver 251 to acquire the driver interface, and returns the function address of the spool data format specifying unit 261 to the GDI 241.

The spool data format designation unit 261 sets the spool format designation bit in the printer driver 251 to EMF and returns it to the GDI 241 (step S507). Since the function address of the spool data format designation unit 261 is returned to the GDI 241 as the driver interface, the spool data format designation unit 261 is also called for an inquiry about the spool data format from the GDI 241. In response to a spool data format inquiry (specifically, the DrvEnablePDEV () function), the spool data format specifying unit 261 accesses the printer driver 251 to enable the printer driver 251, and spool data in the printer driver 251. The bits whose format is determined are set by changing or holding the bits so as to be in a predetermined spool data format (for example, EMF data). Then, the spool data format designation unit 251 returns the spool data format set in the printer driver to the GDI 241.

The GDI 241 generates a spool file of EMF data and sends it to the spooler 242 (step S508). When, for example, EMF data is designated as a predetermined data format, the GDI 241 generates EMF data of document data for which printing has been instructed and sends it to the spooler 242.

When the EMF data is spooled, the spooler 242 calls the spool data acquisition unit 262 (step S509). Regardless of which printer is selected, the function rewriting unit 267 rewrites the function addresses of the functions such as OpenPrintProcessor () API, PrintDocumentOnPrintProcessor () API, ClosePrintProcessor () API, and ControlPrintProcessor () API, so the spooler 242 Calls the spool data acquisition unit 262 instead of the print processor of the selected printer. The spool data acquisition unit 252 mediates exchange of commands between the spooler 242 and the print processor 262 except for acquiring the spool file 300 sent from the spooler 242 to the print processor 252.

The spool data acquisition unit 252 acquires EMF data and attribute information (step S510). The spool data acquisition unit 252 acquires EMF data, which is spool data included in the spool file 300 sent from the spooler 242, and attribute information of document data that has received a print instruction. The document data is EMF data, but the attribute information is described in, for example, an XML format, and includes a file name of the document data to be printed, a printing date, a user name, a machine name, and the like.

Here, the process is divided into a normal print process and a process for managing print data. First, processing for managing print data will be described. As a process for managing print data, the spool data acquisition unit 262 determines the spool data format (step S511). The acquired spool data should be in the data format designated by the spool data format designation unit 261, that is, EMF data. Specifically, the spool data acquisition unit 262 checks and determines whether or not the acquired spool data has the data format of EMF data. When it is confirmed that the data is EMF data, the spool data acquisition unit 262 sends the acquired spool data (EMF data) and attribute information to the text extraction unit 263, and the text extraction unit 263 extracts the text data from the spool data. Is extracted (step S512). Note that the text extraction unit 263 may extract not only text data but also image data.

Next, the spool data conversion unit 264 converts the data format of EMF data, which is spool data, into a predetermined data format (step S513). The predetermined data format is a data format that can be stably reproduced by any information processing apparatus, for example, PDF or XPS. In the case of the EMF data format that is spool data, font information is not included, so if the EMF data is opened on a device other than the device that generated the EMF data, the characters are garbled and the contents of the document data cannot be confirmed. Therefore, the data format is converted here. The converted data is transmitted to the print data management server as document data print data and stored.

The print data converted by the spool data conversion unit 264, the text data extracted by the text extraction unit 263, and the attribute information acquired by the spool data acquisition unit 262 are transmitted to the print data transmission control unit 265 (step S514). Here, the spool data acquisition unit 262 extracts not only all the acquired attribute information but only predetermined items, for example, the user name and file name, the printing date and time, and transmits the extracted information to the print data transmission control unit 265. Also good. Since the attribute information includes fairly fine information such as the data amount, the transmission data amount can be reduced by extracting only predetermined items.

The print data transmission control unit 265 constantly monitors whether print data, text information, and attribute information have been received, and when detecting that all print data, text information, and attribute information have been received, the print data management server The transmission to 110 is controlled (step S515).

Next, normal printing processing will be described. After acquiring the spool data and its attribute information, the spool data acquisition unit 262 calls the print processor 252 (step S516). Since the spooler 242 calls the spool data acquisition unit 262 to call the print processor 252, the spool data acquisition unit 262 calls the print processor 252 in order to continue the printing process normally.

The spool file 300 sent out by the spooler 242 is sent out from the spool data acquisition unit 262 to the print processor 252 as it is, and when there is a process required by the print processor 252, the process is performed. For example, page-by-page aggregation or bookbinding processing. After processing by the print processor 252, the GDI 241 is called by the print processor 252 (step S517), and the processed data is sent to the GDI 241.

The GDI 241 reproduces the received EMF data (step S518) and performs drawing on the printer device context. Thereafter, the GDI 241 calls the spool data format designation unit 261 for processing by the printer driver. The spool data format designation unit 261 calls the printer driver 251, and the printer driver 251 generates printer-specific print data (RAW data) (step S519). At this time, the spool data format specifying unit 261 does not particularly perform processing such as changing the processing result of the printer driver, and mediates exchange with the GDI 241 as an interface of the printer driver.

If necessary, the print provider 243 performs processing for switching the output destination of the print data (step S520). Further, the language monitor 244 performs processing on the print data if necessary after processing at the print provider (step S521). The port monitor 245 performs output processing on the print data according to the type of printer port (USB, TCP / IP, etc.) (step S522). The print data processed in this way is sent to the designated printer via the network and output from the printer.

FIG. 6 is a diagram showing an example of print data attribute information in the present invention. The attribute information acquired from the spooler together with the EMF data is configured as a property file including the attributes of the print data, and is in an XML data format, for example. Accordingly, since a lot of information is included, the print data acquisition unit 262 sends only some items of the acquired attribute information to the print data transmission control unit 263 in order to reduce the transmission data amount. May be. As attribute information transmitted to the print data management server, for example, as shown in FIG. 6, the printer name (LBP5900 # 3) to which the print data is output, the file name of the document data to be printed (TestDoc.txt), the printer The printer name (here LBP5900 # 3, which is the same as the printer name), the machine name of the client PC network that issued the print instruction (here \\ abc-F5522), and the client PC And the print job completion time (here, 7:51:27 on April 16, 2013) which is the print completion time of the print data on the printer. However, the present invention is not limited to these, and other items such as the print job start time and the paper size (A4) of the document data to be printed may be included.

FIG. 7 is a diagram showing an example of functional blocks of the print data management server according to the present invention. The print data management server 110 includes a print data receiving unit 701, a print data storage unit 702, a token analysis unit 705, an index storage unit 706, a search unit 707, a notification condition setting unit 710, and a notification unit 711. The print data storage unit 702 includes an attribute information storage unit 703 and a print data storage unit 704. The search unit 707 includes a search condition analysis unit 708 and a search page generation unit 709.

The print data receiving unit 701 receives print data, text data, and attribute information transmitted by the transmission control of the print data transmission control unit 265 of the client PC. The print data receiving unit 701 divides the received print data, text data, and attribute information thereof into a print data file, a text data file, and an attribute information file, and the print data and attribute information are divided into print data storage units. 702 is stored. The print data file is stored in the print data storage unit 704, and the attribute information file is stored in the attribute information storage unit 703. In addition, the print data receiving unit 701 sends text data and attribute information to the token analysis unit 705.

The print data storage unit 702 includes an attribute information storage unit 703 and a print data storage unit 704. The print data storage unit 702 stores print data (for example, PDF data) and attribute information data received by the print data receiving unit 701 in the print data storage unit 704 and the attribute information storage unit 703, respectively. At this time, the print data storage unit 702 stores the print data and the attribute information corresponding to the print data in association with each other so that one can be acquired from the other. For example, the same ID number is assigned to the print data and the attribute information, and the ID number is stored in the attribute information storage unit 703 and the print data storage unit 704, respectively.

The token analysis unit 705 generates index data by performing token analysis of text data and attribute information data sent from the client PC to the print data reception unit 701. Specifically, a process of extracting a token (word) is performed so that a full-text search can be performed quickly and easily from text data. Here, the token analysis unit 705 has been described with the configuration in which the token analysis is performed when the print data reception unit 701 receives the data. However, the text data is temporarily stored in the index storage unit 707, and the token analysis unit 706 extracts and analyzes the token in a timely manner. You may comprise as follows.

The index storage unit 706 stores print data and text data of attribute information and index data generated by token analysis. The index storage unit 706 is associated with the attribute information storage unit 703 and the print data storage unit 704 so as to be associated with the original print data and its attribute information.

The search unit 707 provides a search page for extracting desired data from a large amount of print data and its attribute information stored in the print data management server. For example, a Web search page capable of inputting a search word is provided, and a user can extract desired print data by inputting a keyword or the like. The search unit 707 includes a search condition analysis unit 708 and a search page generation unit 709. The search condition analysis unit 708 analyzes the search condition input on the search page, and searches for corresponding print data based on the index data in the index storage unit 706. The search page generation unit 709 generates a search page for inputting search conditions in order to provide a search service for stored print data and attribute information to the user. The search page is provided as a Web page via a network, for example. When the search condition analysis unit 708 extracts print data and attribute information that match the input search conditions, the search page generation unit 709 displays them as a list or displays the contents and attribute information of the print data. .

The notification condition setting unit 710 is set in association with a notification condition and a notification destination when a predetermined notification destination is notified. The notification condition is a condition for notifying a predetermined notification destination when there is print data or attribute information that meets the predetermined condition. The notification condition can be set so as to extract print data including a predetermined keyword, print data printed at a predetermined date and time, and the like. For example, when print data including the words “confidential” and “confidential” is detected, it can be set to notify a predetermined mail address. The notification condition can be set by filling a predetermined form and sending it to the print data management server, setting the notification condition from the search page, setting from the notification condition setting web page, or any other method. It does not matter. In one example, whether there is a print page or attribute information that satisfies the conditions set in the notification condition setting unit 710 is received as new print data, the print data is stored in the print data storage unit 702, and the token analysis unit In 705, the text data is searched at the timing of token analysis, and when print data matching the notification condition is detected, the notification condition setting unit is notified of the fact. In another example, when a notification condition is newly set, the notification condition setting unit 710 searches the index storage unit 706 every predetermined time and detects print data that matches the notification condition. May be.

The notification unit 711 notifies a predetermined notification destination when print data matching the notification condition set in the notification condition setting unit 710 is detected and the notification destination is notified from the notification condition setting unit 710. The notification method may be any method such as mail transmission to the set notification destination, automatic call to the set notification destination, and the like.

In FIG. 7, the print data management server 110 is illustrated as being configured by a single server device, but may be configured by a plurality of distributed servers.

(Second embodiment)
In the second embodiment, a case where a GDI printer driver and an XPS printer driver are installed in a client PC will be described. In the case of a GDI printer driver, spooling is performed using an EMF or RAW spool, whereas an XPS printer driver performs spooling using XPS. Note that description of the same points as in the first embodiment, that is, processing for printing using the printer driver (GDI driver) 251 via the GDI 241 is omitted.
FIG. 8 is a diagram illustrating an example of a functional block diagram of the client PC in the printing process according to the second embodiment of the present invention. As in the first embodiment, the client PC 120 includes an application 230, a printer program 250, and a print data acquisition program 260 that operate on a Windows (registered trademark) operating system (OS) 240. . Here, one printer driver (GDI driver) 251 and one printer driver (Filter driver) 282 are shown in the printer program 250, but a plurality of GDI driver printer drivers and a plurality of Filter drivers are installed. It may be.

In the second embodiment, the operating system (OS) 240 has a GDI 241, a spooler 242, a print provider 243, a language monitor 244, a port monitor 245, and a Filter Pipeline Manager 281. The Filter / Pipeline / Manager 281 is used in the printing process in the XPS spool format, and generates XPS spool data. When the application 230 receives a print instruction from the user, a printer to be printed is selected. At this time, if the selected printer driver is an XPS printer driver, Filter Pipeline Manager 281 is called by the application. Since the function rewriting unit 267 rewrites only the function address that the GDI 241 calls the printer driver 251 so as to call the spool data format specifying unit 261, the Filter Pipeline Manager 281 does not call the spool data format specifying unit 261, A driver (Filter driver) 282 is called. This is because, in the case of XPS printing processing, the output spool data format is XPS, so that it can be reproduced by any information processing apparatus. Therefore, the print data acquisition program does not perform function rewriting for calling the spool data format designation unit 261 for the XPS printer driver, and does not go through the spool data format designation unit 261.

Since the spooler 242, the print provider 243, the language monitor 244, and the port monitor 245 are the same as those in the first embodiment, description thereof is omitted. However, in the printing process by the GDI printer driver, the processing in the language monitor 244 and the port monitor 245 continues after the process in the print provider 243. In the printing process by the XPS printer driver, in the print provider 243, After the above process, the process is performed by the port monitor 245 without going through the language monitor 244.

The spool file 300 is data generated by the GDI 241 or the Filter Pipeline Manager 281 and includes spool data and attribute information data. In the present embodiment, the spool data is EMF data or XPS data.

The print data acquisition program 260 includes a spool data format designation unit 261, a spool data acquisition unit 262, a text extraction unit 263, a spool data conversion unit 264, and a print data transmission control unit 265. Since the function rewriting unit 267 rewrites only the function address at which the GDI 241 calls the printer driver 251 so that the spool data format specifying unit 261 is called when the application is activated, the spool data format specifying unit 261 is changed. When an access is received from the GDI 241, a bit for designating a spool data format in the printer driver (GDI driver) 251 of the printer that has received the print instruction is set to a predetermined spool data format, for example, an EMF data format. The specified spool data format is returned to the GDI 241. Note that in the case of printing processing by an XPS printer driver, function rewriting is not performed, and thus the print data does not go through the spool data format designation unit 261.

The spool data acquisition unit 262 acquires the spool file 300 sent from the spooler 242. The spooler 242 sends the spool data format (for example, EMF data) and attribute information data designated by the spool data format designation unit 261 in the case of GDI printing processing, and the XPS data in the case of XPS printing processing. Spool data and attribute information data are sent out. Since the function address when the spooler 242 sends the spool file to the print processor 252 is rewritten by the function rewriting unit 267 when the application is activated, the spooler 242 sends the spool file 300 to the spool data acquisition unit 262. to access. The spool data acquisition unit 262 acquires the spool file 300 sent from the spooler 242 regardless of whether the spool data is EMF data or XPS data. Except for the acquisition, when there is other processing between the spooler 242 and the print processor 252, only mediation is performed. Then, the spool data acquisition unit 262 determines the data format of the acquired spool data. Specifically, it is first determined whether or not the data format is EMF. If it is not EMF data, it is determined whether or not data can be read as XPS data. When it is confirmed that the data is EMF data or XPS data, the spool data acquisition unit 262 sends the acquired spool data (EMF data or XPS data) and attribute information to the text extraction unit 263.

The text extraction unit 263 extracts text data from spool data that is EMF or XPS data acquired by the spool data acquisition unit 262.

The spool data conversion unit 264 converts EMF data out of the spool data acquired by the spool data acquisition unit 262 into a predetermined data format (for example, PDF data or XPS data). In XPS printing processing, spool data is already XPS data, and any information processing apparatus has a data format that does not cause garbled characters or errors, so that spool data conversion is not required. Therefore, in the case of XPS type printing processing, the processing in the print data transmission control unit 265 is performed without going through the spool data conversion unit 264.

The print data transmission control unit 265 is a network that transmits the attribute information acquired by the print data acquisition unit 262, the text information extracted by the text extraction unit 263, and the print data in a predetermined data format to the print data management server. Control to transmit via.

The printer program 250 includes a printer driver (GDI driver) 251, a printer driver (Filter driver) 282, and a print processor 252. A printer driver (GDI driver) 251 is a printer driver that performs printing processing using the GDI 241 of the OS, and a printer driver (Filter driver) 282 is a printer driver that performs printing processing using Filter Pipeline Manager 281. Regardless of the type of printer driver, print data format setting information is stored, and printer-specific print data is generated. The print processor 252 reproduces print data (EMF data or XPS data) sent from the spooler 242 and performs, for example, editing processing such as aggregation and bookbinding for each page of the print document.

FIG. 9 is an example of a flowchart for explaining a print data acquisition method in print processing according to the second embodiment of the present invention. When the user selects an application such as document creation software or image creation software, the selected application is activated on the OS of the client PC (step S901).

At the same time when the application is activated, the function rewriting unit 267 is activated and rewrites a predetermined function address (step S902). When the print data acquisition program is installed in the client PC, the registry writing unit 266 writes the module name of the function rewriting unit 267 in the registry of the module loaded when the application is started. The unit 267 is activated to rewrite a predetermined function address. The function address to be rewritten is the same as in the first embodiment. In the XPS printing process, since spooling is performed by XPS, it is not necessary to forcibly specify the spool data format by the print data acquisition program, and the spooler 242 can be used in both the GDI printing process and the XPS printing process. This is because the function address is the same because the process called to send the spool file 300 to the print processor 252 is common. Therefore, the function address of the function for calling the printer driver 251 to inquire the spool data format by the GDI 241, for example, the function address of the function such as LoadLibrary () API or DrvEnableDriver () API, is sent from the printer driver 251 to the spool data format designation unit. The function address related to the processing that the spooler 242 calls to send the spool file 300 to the print processor 252, for example, functions such as OpenPrintProcessor () API, PrintDocumentOnPrintProcessor () API, ClosePrintProcessor () API, ControlPrintProcessor () API The function address is rewritten from the print processor 252 to the spool data acquisition unit 262.

Next, the application receives a print instruction from the user using a mouse, a keyboard, or the like (step S903). For example, the user selects “print” from the application menu, selects the printer to be printed, the number of sheets, the output paper size, and the like. Execute the instructions. At this time, if the user selects a GDI printer driver, the processing is the same as the processing in and after step S504 in FIG. 5 of the first embodiment. The case where is selected will be described below.

When the user selects an XPS printer driver, the Filter Pipeline Manager 281 is called. The Filter / Pipeline / Manager 281 generates a spool file of XPS data and sends it to the spooler (step S904). As described above, since the Filter Pipeline Manager 281 generates a spool file of XPS data, the print data acquisition program does not intervene in specifying the spool file format.

Next, when the XPS data is spooled, the spooler 242 calls the spool data acquisition unit 262 (step S905). Even when an XPS printer is selected, the function rewriting unit 267 sets the function address of the function that the spooler calls the printer processor such as OpenPrintProcessor () API, PrintDocumentOnPrintProcessor () API, ClosePrintProcessor () API, ControlPrintProcessor () API. Since rewriting is performed, the spooler 242 calls the spool data acquisition unit 262 instead of the print processor of the selected printer.

The spool data acquisition unit 252 acquires XPS data and attribute information (step S906). The spool data acquisition unit 252 acquires XPS data, which is spool data included in the spool file 300 sent from the spooler 242, and attribute information of document data that has received a print instruction. The document data is XPS data, but the attribute information is described in XML format, for example, and includes the file name of the document data to be printed, the date and time of printing, the user name, the machine name, and the like.

Here, as in the first embodiment, there are two processes: a normal print process and a process for managing print data. First, processing for managing print data will be described. As a process for managing print data, the spool data acquisition unit 262 determines the spool data format (step S907). The acquired spool data is XPS data, but a discrimination process is performed here. Specifically, the spool data acquisition unit 262 checks and determines whether or not the acquired spool data has the data format of EMF data. If it is determined that the data is not EMF data, data is read as XPS data. Here, if the data can be read as XPS data, it is determined that the data is XPS data. If the data cannot be read, an error occurs and the process ends. When it is determined as XPS data, the spool data acquisition unit 262 sends the acquired spool data (XPS data) and attribute information to the text extraction unit 263, and the text extraction unit 263 extracts text data from the spool data. (Step S908). Note that the text extraction unit 263 may extract not only text data but also image data.

Text data extracted by the text extraction unit 263, XPS data that is spool data acquired by the spool data acquisition unit 262, and attribute information are transmitted to the print data transmission control unit 265, respectively (step S909). Since the spool data is already XPS data, spool data conversion processing is not necessary. Here, the spool data acquisition unit 262 extracts not only all the acquired attribute information but only predetermined items, for example, the user name and file name, the printing date and time, and transmits the extracted information to the print data transmission control unit 265. Also good.

The print data transmission control unit 265 always monitors whether print data, text information, and attribute information, which are XPS data, has been received, and when detecting that all print data, text information, and attribute information have been received, Transmission to the print data management server 110 is controlled (step S910).

Next, normal printing processing will be described. After acquiring the spool data and its attribute information, the spool data acquisition unit 262 calls the print processor 252 (step S911). Since the spooler 242 calls the spool data acquisition unit 262 to call the print processor 252, the spool data acquisition unit 262 calls the print processor 252 in order to continue the printing process normally.

After the necessary processing is performed by the print processor 252, the print processor 252 calls the Filter Pipeline Manager 281 (step S <b> 912). Data processed by the print processor 252 is sent to the Filter Pipeline Manager 281.

The Filter®Pipeline® Manager 281 reproduces the received XPS data (step S913) and draws it on the printer device context. Thereafter, the Filter / Pipeline / Manager 281 calls the printer driver (Filter driver) 282, and the printer driver (Filter driver) 282 generates print data (RAW data) unique to the printer (Step S914).

The print provider 243 performs a process of switching the output destination of the print data if necessary (step S915). The port monitor 245 performs output processing on the print data in accordance with the type of printer port (USB, TCP / IP, etc.) (step S916). The print data processed in this way is sent to the designated printer via the network and output from the printer.

As described above, according to the present invention, it is possible to reliably acquire print data information regardless of whether the printer is a GDI system or an XPS system.

100 Network 110 Print Data Management Server 120 Client PC
130 Printer

Claims

An information processing apparatus that outputs print data to a printer,
Spool data format designating means for designating the spool data format of the document data instructed to be printed in the printer driver of the output destination printer in the desired spool data format when there is a print instruction;
Spool data acquisition means for acquiring spool data in a specified spool data format and attribute information of the spool data from a spooler;
Text extraction means for extracting text data from the acquired spool data;
An information processing apparatus comprising: transmission control means for controlling to transmit at least the text data and the attribute information.
A function rewriting means for rewriting a predetermined function address related to printing when the application is started;
The spool data format designating unit designates a spool data format when the function address is rewritten by the function rewriting unit, and the spool data obtaining unit obtains the spool data. 1. An information processing apparatus according to 1.
The function rewriting means rewrites the function address for the GDI to access the printer driver of the output destination printer, so that the spool data format designating means designates the spool data format and the spooler calls the print processor. The information processing apparatus according to claim 2, wherein the spool data is acquired by rewriting an address.
4. The information processing apparatus according to claim 3, further comprising registry writing means for writing a name of the function rewriting means in a registry relating to a module loaded when an application is started.
5. The information processing apparatus according to claim 1, wherein the spool data format specified by the spool data format specifying means is EMF data.
6. The information processing apparatus according to claim 1, wherein the attribute information of the print data includes at least a print date, a document data name, and a user name.
Furthermore, it has a spool data conversion means for converting the acquired spool data into a predetermined data format,
The information processing apparatus according to any one of claims 1 to 6, wherein the transmission control unit controls transmission of print data converted into a predetermined data format.
The information processing apparatus according to claim 7, wherein the spool data conversion means converts when the spool data format is EMF data.
The information processing apparatus according to claim 7 or 8, wherein the spool data conversion means converts the acquired spool data into PDF or XPS data.
A print data acquisition program that is applied to a computer that outputs print data to be printed by a printer and acquires the print data,
A spool data format designation step for designating the spool data format of the document data for which printing is instructed in a desired spool data format in the printer driver of the output destination printer;
A spool data acquisition step for acquiring spool data in the specified spool data format and spool data attribute information from the spooler;
A text extraction step of extracting text data from the acquired spool data;
A print data acquisition program for executing a transmission control step of controlling to transmit at least the text data and the attribute information.
A function rewriting step of rewriting a predetermined function address related to printing when the application is activated;
The spool data format designating unit designates a spool data format when the function address is rewritten by the function rewriting step, and the spool data obtaining step obtains the spool data. The print data acquisition program according to 10.
12. The print data acquisition program according to claim 11, further comprising a registry writing step for writing a name of the function rewriting step in a registry relating to a module loaded when the application is started.
A print data acquisition method that is applied to a computer that outputs print data to be printed by a printer and acquires the print data,
A spool data format designation step for designating the spool data format of the document data for which printing is instructed in a desired spool data format in the printer driver of the output destination printer;
A spool data acquisition step of acquiring spool data in a specified spool data format and attribute information of the spool data from a spooler;
A text extraction step of extracting text data from the acquired spool data;
A print data acquisition method comprising: executing a transmission control step of controlling to transmit at least the text data and the attribute information.
A print data management system comprising: an information processing apparatus that outputs print data to a printer; and a print data management server that manages the print data,
The information processing apparatus includes:
Spool data format designating means for designating the spool data format of the document data instructed to be printed in the printer driver of the output destination printer in the desired spool data format when there is a print instruction;
Spool data acquisition means for acquiring spool data in a specified spool data format and attribute information of the spool data from a spooler;
Text extraction means for extracting text data from the acquired spool data;
Transmission control means for controlling to transmit at least the text data and the attribute information;
The print data management server
Receiving means for receiving the print data, the text data, and the attribute information;
Print data storage means for storing the print data, the text data, and the attribute information;
A print data management system.
The print data management server
Further, index storage means for storing index data generated based on the text data and the attribute information;
Search means for searching for the print data based on the index data;
The print data management system according to claim 14.
16. The print data management system according to claim 15, further comprising token analysis means for generating index data by token analysis of the text data.
The print data management server
A notification condition setting unit for notifying a predetermined notification destination when print data having a predetermined condition is stored in the print data storage unit;
The print data management system according to any one of claims 14 to 16, further comprising notification means for notifying a predetermined notification destination when print data matching a predetermined condition is detected by the notification condition setting means.