JP2008217500A - Print control system, and print log control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a volume of stored print log, while making the print log remain surely, by changing a storage method for the print log in response to whether a printing document is being edited or not, or the like. <P>SOLUTION: This print control system of the present invention includes a client, and a server provided with a print log control system for controlling the print log. A printer driver calls out the print log control system, when the client receives a print indication from a user, stores a print job data when the printing document is being edited, and stores a document file when the printing document is not being edited. The print log control system stores the print job data when the printing document is being edited, in response to the call-out from the printer driver, and stores the document file when the printing document is not being edited. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a processing technique for collecting print logs.

  In recent years, information leakage has become a problem in companies. Among them, there is information leakage caused by the printed matter flowing out.

  One way to identify leaked information is to print all the print data from the client side via the server, acquire the print log, and store and store the acquired print log and print data. There are technologies that allow you to track when it happens. However, with this technology, particularly when a large-scale company collects print logs for a long period of time, the amount of data becomes enormous, and it becomes difficult to secure the cost for managing this and the installation space for physical devices. . Also, it becomes difficult to detect an illegal print log from a large amount of data.

In order to solve this, a technique for reducing the capacity of a print log to be managed has been proposed. For example, in Patent Document 1, identification information is embedded in print data in advance and registered in the print log DB. If the registered print data is printed, the identification information is stored instead of storing the print data as a print log. Is stored.
JP 2006-189929 A

  By the way, in the print log collection device described in Patent Document 1, when a document corresponding to registered print data is edited and printed without adding confidential information and stored, the print log contains the registered print data. Identification information remains, and there is a problem that confidential information added as a result of editing does not remain in the print log. For this reason, in the apparatus described in Patent Document 1, the fact that information leakage has occurred may be concealed.

  Further, in the apparatus described in Patent Document 1, it is pointed out that the entire print data must be managed at least once for all documents, so that the management cost is high.

  The present invention has been made in view of such circumstances, and determines whether a print document is being edited, whether it is managed by a history management system, and the like, and a print log storage method according to the determination result The purpose of this is to reduce the capacity of the print log to be saved while ensuring that the print log remains.

  In order to solve the above problems, a print management system according to the present invention includes a client for which a user issues a print instruction, and a print log management system for managing a print log. The print log management system includes a print log and job storage unit that stores print job data of a print document as a print log, and a print log and document storage unit that stores a document file of the print document as a print log. . Also, the client calls the print log and job storage means to print when the print document is being edited when the print application receives the print instruction and the print application receives the print instruction. A printer driver that saves the job data and calls a print log and a document saving unit to save the document file when the print document is not being edited; According to this invention, when the print document is not being edited, the document file having a smaller capacity than the print job data is saved, thereby reducing the capacity of the print log and the document being edited saves the print job data. Thus, it is possible to reliably leave the print contents in the log.

  Preferably, when the print application receives a print instruction, the client receives whether the print document is being edited from the print application, and print job data based on whether the print document is being edited. And a plug-in that determines which of the document file is saved as a print log and stores the determined save method as a print log addition method. When the print application receives a print instruction, the printer driver acquires the print log addition method stored by the plug-in and determines which of the print log and job storage unit and the print log and document storage unit to call. To do. According to this invention, the plug-in can select a method for adding a print log based on whether or not the print document is being edited.

  The print log management system is preferably configured to be able to refer to a history management system that manages document histories. At this time, the print log and document storage means has history management document identification information in which the document file of the print document is managed by the history management system, and the document name and version number of the document file in the history management system can be identified. Is acquired, it is preferable to store the history management document identification information as a print log instead of the document file. According to this invention, when the document is not being edited and the document is managed by the history management system, the history management document identification information having a smaller capacity than the document file, that is, information that can identify the document name and the version number is stored. By saving, the capacity can be further reduced.

  More preferably, the print log management system includes a document name change inconsistency resolution unit that resolves an inconsistency related to the change of the document name when the document name of the document managed by the history management system is changed. Preferably, the print log management system further includes a document deletion inconsistency resolution unit that resolves inconsistencies related to document deletion when a document managed by the history management system is deleted. According to this invention, even when the document name and version number are stored as the print log, the document name is changed in the history management system or the document is deleted so that the print log is not inconsistent. In this case, it is possible to call the print log inconsistency solving means to prevent inconsistency and to leave the print log with certainty.

  Preferably, the print log management system includes a document file of the updated document and a document file managed as a print log by the print log management system when the document managed by the history management system is updated. And a document update inconsistency resolution unit for correcting the history management document identification information of the document updated as a print log when the two match. According to this invention, when the document file of the updated document matches the document file stored as the print log when the document of the history management system is updated, the history management document identification information of the updated document is displayed in the print log. By deleting the document file that was originally stored, the print log capacity can be reduced.

  Further, the printer driver has a list of information to be added to the print document as a printer driver setting, and if one or more information is set to be added from the list, whether or not the print document is being edited. Regardless, the print log and job storage means are called to store the job data. According to this invention, when information is added by the printer driver, the print job data is saved as the print contents so that the information remains as a print log, and the print log remains reliably.

  In addition, the client according to the present invention has a print application that performs print processing in response to a user's print instruction, and when the print application receives a print instruction, a print document is being edited to the print log management system. A printer driver that saves the print job data and saves the document file when the print document is not being edited.

  Further, the print log management system according to the present invention includes a print log and job storage means for storing print job data of a print document as a print log when a print instruction is being edited at the client when a user instructs printing. When the user issues a print instruction, if the print document is not being edited at the client, a print log and a document storage unit that stores a document file of the print document as a print log are provided.

  A print log management method according to the present invention is a method for managing a print log in a print management system including a client for which a user gives a print instruction and a print log management system for managing the print log. Includes a step of receiving a print instruction from the user, and a means for saving the print job data when the print driver is editing the print log management system when the print driver of the client receives the print instruction. If the print document is not being edited, the step of calling the means for saving the document file and the print log management system when the print document is being edited in response to the call from the printer driver If the print document is not being edited, save the document file. Includes a step, a.

  Furthermore, the program of the present invention causes a computer to execute each step of the print log management method of the present invention. The program of the present invention can be installed or loaded on a computer through various recording media such as an optical disk such as a CD-ROM, a magnetic disk, or a semiconductor memory, or via a communication network.

  In this specification and the like, the means does not simply mean a physical means, but includes a case where the functions of the means are realized by software. Further, the function of one means may be realized by two or more physical means, or the functions of two or more means may be realized by one physical means.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In addition, the same code | symbol is attached | subjected to the same element and the overlapping description is abbreviate | omitted.

  FIG. 1 is a block diagram showing the overall configuration of a client server type print management system including a print log management system 41 according to an embodiment of the present invention. As shown in FIG. 1, the client server type print management system including the print log management system 41 includes a client 10, a server 30, and a printing apparatus 70, which are connected to each other via a network. It is constituted by.

  The client 10 is a client terminal device (computer) for a user to issue a print instruction, and includes a print application 11 that performs printing in response to a user's print instruction, a printer driver 18, and a system spooler 19.

  The print application 11 includes a printing unit 12 and a plug-in 13. Then, it has a function of determining whether or not the print document is being edited, passing information indicating whether or not the print document is being edited, and calling the pre-print processing means 14 of the plug-in 13.

  The plug-in 13 includes a pre-print processing unit 14 and a print log addition method acquisition unit 17 and is called from the print application 11 before printing. Then, based on whether the print document is being edited, it has a function of storing an optimum method as a print log addition method.

  The printer driver 18 has a function of adding a log to the print log management system 41 by calling the print log and job storage unit 43 or the print log and document storage unit 42 of the print log management system 41 of the server 30. At this time, the printer driver 18 calls the print log addition method acquisition unit 17 of the plug-in 13 to acquire the print log addition method stored by the plug-in 13 and the print log management system 41 of the print log management system 41 according to the acquired addition method. It is determined which of the print log and job storage unit 43 or the print log and document storage unit 42 is to be called. If the document is not being edited, the document file is stored as the print contents.

  The printer driver 18 has a list of information to be added to the print document and printed as a setting of the printer driver 18. If the printer driver 18 is set to add one or more pieces of information from the list of information to be added to the print document and printed, the printer driver 18 regardless of whether the print document is being edited or not. Calls the print log and job storage means 43 of the print log management system 41 provided in the server 30 to store the print job data. In this way, when information is added by the printer driver 18, the print job data is saved as the print contents so that the information remains as a print log, so that the print log remains reliably.

  The server 30 includes a history management system 31 that manages document histories and a print log management system 41 that manages print logs.

  The history management system 31 is a document management system that manages what update history a file has and can acquire an arbitrary version of an arbitrary document. Note that since change history management is one of the requirements for document management in ISO 9001, some companies that have obtained ISO 9001 certification have met and satisfied a document history management system.

  In the present embodiment, the history management system 31 transmits a document name acquisition unit 32 that transmits a document name of a document managed by the history management system 31 and a document file of a document managed by the history management system 31. Document file acquisition means 33, version number acquisition means 34 for transmitting the version number of the document managed by the history management system 31, document update means 35 for updating the document managed by the history management system 31, and history A document deleting unit 36 for deleting a document managed by the management system 31 and a document name (path) changing unit 37 for changing the document name of the document managed by the history management system 31 are provided.

  When called, the document update unit 35 calls the document update inconsistency resolution unit 46 of the print log management system 41, and the document file of the updated document and the print log management system 41 manage the document file as print contents. If it matches the log document file, the log is corrected so as to manage the document name and version number (history management document identification information) of the document updated as the print content.

  When the document deletion unit 36 is called, the history management system 31 calls the document deletion inconsistency resolution unit 45 of the print log management system 41. When the document name changing unit 37 is called, the history management system 31 calls the document name change inconsistency solving unit 44 of the print log management system 41.

  The print log management system 41 includes a print log and document storage unit 42 that stores a document file of a print document as print contents, a print log and job storage unit 43 that stores print job data as print contents, and a history management system 31. Document name change inconsistency resolution means 44 that is called when the document name change means 37 is called, document deletion inconsistency resolution means 45 that is called when the document deletion means 36 is called in the history management system 31, and a history management system And a document update inconsistency resolution means 46 called when the document update means is called at 31.

  When the print log and document storage unit 42 is called, the document name acquisition unit 32 and the version number acquisition unit 34 of the history management system 31 are called, and the document name and version number (history management document identification information) can be acquired. In this case, the document name and version number (history management document identification information) are stored as the print contents.

  The printing device 70 is a device that prints a document or the like, and for example, a printer can be applied.

  The network is a communication line for transmitting and receiving information between the client 10, the server 30, and the printing device 70. For example, any of a LAN, the Internet, a dedicated line, a packet communication network, a telephone line, a corporate network, other communication lines, combinations thereof, and the like may be used, regardless of whether they are wired or wireless. In FIG. 1, the client 10 is illustrated as if it were connected to the server 30 and the printing apparatus 70 through physically different lines, but the network configuration is not limited to that illustrated. Needless to say, you can't.

  FIG. 2 is a block diagram illustrating an example of a hardware configuration of the client 10. The client 10 is applicable to a dedicated or general-purpose computer, and includes a CPU 21 as a control means for controlling the operation and processing of each unit, a storage unit 22 such as a hard disk for storing various information, data necessary for processing, etc. A ROM 24 that stores data, a RAM 25 that functions as a work area, an interface (I / F) 26 that mediates exchange of data, and a bus 27 that connects them. In the present embodiment, the storage unit 22 includes a print log addition method storage unit 23 that stores a print log addition method.

  FIG. 3 is a block diagram illustrating an example of the hardware configuration of the server 30. The server 30 is applicable to a dedicated or general-purpose computer, and includes a CPU 51 as a control means for controlling the operation and processing of each unit, a storage unit 52 such as a hard disk for storing various information, data necessary for processing, etc. A ROM 54 that stores data, a RAM 55 that functions as a work area, an interface (I / F) 56 that mediates exchange of data, and a bus 57 that connects them. The server 30 may be composed of a single computer or may be composed of a plurality of computers distributed on a network.

  In the present embodiment, the storage unit 52 includes a history information storage unit 61 and a checkout information storage unit 62, which form part of the history management system 31. The storage unit 52 includes a print log storage unit 63, a print job storage unit 64, an unmanaged document storage unit 65, a version mismatch document storage unit 66, and a reference history storage unit 67. It forms part of the log management system 41.

  Next, the configuration of data stored in the storage unit 22 of the client 10 and the storage unit 52 of the server 30 will be described.

  FIG. 4 is a diagram illustrating an example of a data configuration of the print log addition method storage unit 23 of the client 10. As illustrated in FIG. 4, the print log addition method storage unit 23 stores a document path 231 on the client 10, a user ID 232, and a print log addition method 233 in association with each other. In the present embodiment, the print log addition method 233 represents addition of a document (document is not being edited) when “0”, and addition of a job (document is being edited) when “1”. Yes. As with the printer queue, the documents are printed in the order of the data stored in the print log addition method storage unit 23.

  FIG. 5 is a diagram illustrating an example of a data configuration of the history information storage unit 61 of the server 30. As illustrated in FIG. 5, the history information storage unit 61 stores a document name (path) 611, a version number 612, and a document file 613 in association with each other. Here, the document file 613 stores a binary string of the document file.

  FIG. 6 is a diagram illustrating an example of a data configuration of the checkout information storage unit 62 of the server 30. As illustrated in FIG. 6, the checkout information storage unit 62 stores a computer name 621, a user ID 622, a checkout path 623, and a document name 624 in association with each other. In the present embodiment, checkout means a state in which a document file is open.

  FIG. 7 is a diagram illustrating an example of a data configuration of the print log storage unit 63 of the server 30. As illustrated in FIG. 7, the print log storage unit 63 stores a user ID 631, a print time 632, a data type 633, and a data ID 634 in association with each other.

  FIG. 8 is a diagram illustrating the relationship between the value of the data type 633 and the ID indicated by the data ID 634 in the print log storage unit 63. As shown in the figure, when the data type 633 is “1”, the ID stored in the data ID 634 of the print log storage unit 63 indicates the print job ID of the print job storage unit 64. When the data type 633 is “2”, “3”, or “4”, the ID stored in the data ID 634 of the print log storage unit 63 is the unmanaged document ID of the unmanaged document storage unit 65, respectively. The version mismatch document ID of the version mismatch document storage unit 66 and the reference history ID of the reference history storage unit 67 are shown.

  FIG. 9 is a diagram illustrating an example of a data configuration of the print job storage unit 64 of the server 30. As shown in FIG. 9, the print job storage unit 64 stores a print job ID 641 and print job data 642 in association with each other. Here, the print job data 642 stores a binary string of print job data.

  FIG. 10 is a diagram illustrating an example of a data configuration of the unmanaged document storage unit 65 of the server 30. As shown in FIG. 10, the unmanaged document storage unit 65 stores an unmanaged document ID 651 and a document file 652 in association with each other. Here, the document file 652 stores a binary string of the document file.

  FIG. 11 is a diagram illustrating an example of a data configuration of the version mismatch document storage unit 66 of the server 30. As shown in FIG. 11, the version mismatch document storage unit 66 stores a version mismatch document ID 661, a document name (path) 662 on the history management system, and a document file 663 in association with each other. Here, the document file 663 stores a binary string of the document file.

  FIG. 12 is a diagram illustrating an example of a data configuration of the reference history storage unit 67 of the server 30. As shown in FIG. 12, the reference history storage unit 67 stores a reference history ID 671, a document name (path) 672 on the history management system, and a version number 673 of a document file or the like on the history management system in association with each other. is doing.

  FIG. 13 is a diagram showing an example of an information list that is added to a print document as a setting of the printer driver 18 and printed. As shown in FIG. 13, information such as a print time 181, a print user name 182, a print user signature 183, and a document security level 184 is set as an information list, and these information are added to the document and printed. .

  Next, an operation at the time of printing of the client server type print management system including the print log management system 41 configured as described above will be described.

  FIG. 14 is a flowchart showing the flow of processing of the print application 11 during printing. First, the print application 11 checks whether the document is being edited (S110). Then, the pre-print processing means 14 of the plug-in 13 is called (S111). At this time, the print application 11 passes information relating to whether or not the document is being edited to the pre-print processing means 14. Thereafter, the print application 11 transmits a print command, the user ID of the output user, a document name, and the like to the printer driver 18 to instruct print execution (S112).

  FIG. 15 is a flowchart showing a processing flow of the printer driver 18 at the time of printing. First, the printer driver 18 determines whether print information has been received (S120). If the print information is not received (S120: NO), the reception of the print information is awaited. When print information is received (S120: YES), print job data is created from the received print command (S121). After creating the print job data, the output user ID and the document path on the client 10 are acquired (S122), and the print log adding method acquisition means 17 of the plug-in 13 is called (S123).

  Thereafter, the printer driver 18 receives a return value from the print log addition method acquisition unit 17 (S124), and if the return value is 1 (S124: YES), it acquires an output user ID, print job data, and the like (S125). ) Call the print log and job storage means 43 of the print log management system 41 (S126). In this way, the document being edited saves the print job data to ensure that the print contents remain in the log.

  On the other hand, if the return value received from the print log addition method acquisition unit 17 is not 1 in step S124 (S124: NO), the printer driver 18 determines the computer name, the document path on the client, the output user ID, the document file, etc. (S127) and the print log and document storage means 42 of the print log management system 41 is called. Thus, when the document is not being edited, the capacity of the print log is reduced by storing a document file having a smaller capacity than the print job data.

  The printer driver 18 transmits the print job data to the spooler 19 (S129), and then returns to the print information reception standby state (S120).

  FIG. 16 is a flowchart showing a processing flow of the pre-printing processing means 14 of the plug-in 13 at the time of printing. First, the pre-printing processing unit 14 receives information regarding whether or not a document is being edited (S130). Based on the received information (S131), if the document is not being edited (S130: NO), data is added to the print log addition method storage unit 23 with the addition method set to “0”. On the other hand, if the document is being edited (S131: YES), data is added to the print log addition method storage unit 23 with the addition method set to “1”. The pre-printing processing unit 14 receives the user ID and the document path on the client together from the print application 11 and registers them in the print log adding method storage unit 23.

  FIG. 17 is a flowchart showing a processing flow of the print log addition method acquisition unit 17 of the plug-in 13 at the time of printing. Upon receiving the user ID and the document path on the client from the printer driver 18 (S140), the print log addition method acquisition unit 17 adds the received user ID and the document path on the client from the print log addition method storage unit 23. The matching data is searched (S141).

  If the number of matching data is one or more as a result of the search (S142: YES), the method of adding the data added at the earliest time among the matched data is transmitted as a return value (S143). ), The data added at the earliest time is deleted from the print log adding method storage unit 23 (S144). On the other hand, if there is no matching data in step S142 (S142: NO), “1” is transmitted as a return value (S145).

  FIG. 18 is a flowchart showing the flow of processing of the print log and job storage means 43 of the print log management system 41 during printing. When receiving the user ID, print job data, and the like (S150), the print log and job storage unit 43 adds the received print job data to the print job storage unit 64 (S151). Further, “1” is entered as the data type 633 and the print job ID 641 of the print job data added in step S151 is entered as the data ID 634 in the print log storage unit 63, and data is added (S152).

  FIG. 19 is a flowchart showing a processing flow of the print log and document storage unit 42 of the print log management system 41 during printing. Upon receiving the computer name, the document path on the client, the user ID, the document file, and the like from the printer driver 18 (S160), the print log and document storage unit 42 receives the computer name, the user ID, and the like from the received data. The document path on the client is acquired (S161), and the document name acquisition unit 32 of the history management system 31 is called (S162).

  The print log and document storage unit 42 receives the return value from the document name acquisition unit 32 (S163), and if the character string length of the received document name is greater than 0 (S163: YES), the received document name and step S160 are received. The document file received in (1) is acquired (S164), and the version number acquisition means 34 of the history management system 31 is called (S165).

  The print log and document storage unit 42 receives the return value from the version number acquisition unit 34 (S166). If the character string length of the received version number is greater than 0 (S166: YES), the history management is performed in the reference history storage unit 67. Data such as the document name and version number on the system 31 is added (S167). Further, “4” is entered as the data type 633 and the reference history ID 671 of the reference history added at step S167 is entered as the data ID 634 in the print log storage unit 63, and data is added (S168).

  In step S166, if a null character string is received as a return value from the version number acquisition unit 34 (S166: NO), that is, if there is no matching data in the history information storage unit 61, the version mismatch document storage unit 66 stores it. Data such as a document name (path) and a document file are added (S169). Further, “3” as the data type 633 and the version mismatch document ID 661 of the version mismatch document added in step S169 as the data ID 634 are entered into the print log storage unit 63, and data is added (S170).

  On the other hand, if an empty character string is received as a return value from the document name acquisition unit 32 in step S163 (S163: NO), that is, if there is no matching data in the checkout information storage unit 62, the unmanaged document storage unit Data such as a document file is added to 65 (S171). Further, “2” is entered as the data type 633 in the print log storage unit 63, and the unmanaged document ID 651 of the unmanaged document added in step S171 is entered as the data ID 634, and data is added (S172).

  FIG. 20 is a flowchart showing a processing flow of the document name acquisition unit 32 of the history management system 31 at the time of printing. Upon receiving the user ID, computer name, and checkout path from the print log and document storage unit 42 (S190), the document name acquisition unit 32 receives the received user ID, computer name, and check from the checkout information storage unit 62. Data matching the out path is searched (S191). If there is matching data as a result of the search (S192: YES), the document name (path) of the matching data is transmitted (S193). On the other hand, if there is no matching data (S192: NO), an empty character string is transmitted (S194). Thus, the document name acquisition unit 32 returns the document name or the empty character string as a return value to the print log and document storage unit 42.

  FIG. 21 is a flowchart showing a processing flow of the version number acquisition unit 34 of the history management system 31 at the time of printing. When the version number acquisition unit 34 receives the document name (path) and the document file from the print log and document storage unit 42 (S200), it matches the received document name (path) and the document file from the history information storage unit 61. Data is searched (S201). Then, it is determined whether there is matching data (S202). If there is matching data (S202: YES), the version number of the matching data is transmitted (S203). On the other hand, if there is no matching data (S202: NO), an empty character string is transmitted (S204). In this way, the version number acquisition unit 34 returns the version number or the empty character string as a return value to the print log and document storage unit 42.

  Thus, when the document is not being edited and the document is managed by the history management system 31, the print log capacity can be reduced by storing a set of document name and version number having a smaller capacity than the document file. To do.

  Next, an operation when the document name (path) changing unit 37 of the history management system 31 is called will be described.

  FIG. 22 is a flowchart showing a processing flow of the history management system 31 when the document name (path) changing unit 37 is called. First, when the document name is changed in the history management system 31, the history management system 31 receives the document name (path) before the change and the document name (path) after the change (S210), and the checkout information storage unit Data that matches the document name before the change is searched from 62 (S211). If there is one or more matching data as a result of the search (S212: YES), the document name change mismatch resolution unit 44 is not called.

  On the other hand, if there is no matching data (S212: NO), the history information storage unit 61 is searched for data that matches the document name before the change (S213), and the document names of the enumerated data are changed. The name is changed (S214). Then, the document name change inconsistency resolution unit 44 of the print log management system 41 is called (S215).

  FIG. 23 is a flowchart showing a processing flow of the document name change inconsistency resolution unit 44 of the print log management system 41 when the document name (path) change unit 37 is called. Upon receiving the document name (path) before the change and the document name (path) after the change from the document name (path) changing unit 37 (S220), the document name change / inconsistency resolution unit 44 stores the reference history storage unit 67. By searching, data referring to the document name (path) before the change is listed (S221). Then, the document name of the enumerated data is changed to the changed document name (S222). Further, data referring to the document name (path) before change is listed from the version mismatch document storage unit 66 (S223), and the document name of the listed data is changed to the document name after change (S224). .

  In this way, even when the document name is changed in the history management system 31, the document name change inconsistency resolution unit 44 is called to prevent inconsistency of the print log and to ensure that the print log remains. .

  Next, an operation when calling the document deletion means 36 of the history management system 31 will be described.

  FIG. 24 is a flowchart showing a processing flow of the history management system 31 when the document deletion means 36 is called. First, when a document is deleted by the history management system 31, the history management system 31 receives the name of the document to be deleted (S240), and receives data from the checkout information storage unit 62 that matches the document name of the document to be deleted. Is searched (S241). If there is one or more matching data as a result of the search (S242: YES), the document deletion inconsistency resolution unit 45 is not called.

  On the other hand, if there is no matching data (S242: NO), the document deletion inconsistency resolution unit 45 of the print log management system 41 is called (S243). Thereafter, data matching the document name of the document to be deleted is searched from the history information storage unit 61 (S244), and the listed data is deleted from the history information storage unit 61 (S245).

  FIG. 25 is a flowchart showing a processing flow of the print log management system 41 when the document deletion unit 36 is called. Upon receiving the document name (path) of the document to be deleted (S250), the print log management system 41 searches the reference history storage unit 67 and lists data referring to the document name (path) of the document to be deleted. To do. Then, the processing from step S252 to S259 is performed on the enumerated data, that is, one case of data that matches the document name (path) of the document to be deleted.

  First, the document name (path) and version number are acquired for one of the listed data (S253), and the document file acquisition means 33 of the history management system 31 is called (S254). Then, the document file acquired from the document file acquisition unit 33 is added to the unmanaged document storage unit 65 (S255), the print log storage unit 63 is searched, and the reference history ID of one piece of data currently being processed is obtained. The matching data is listed (S256). For each of the enumerated data, the data type 633 is changed to “2”, and the data ID 634 is changed to the unmanaged document ID 651 of the data added to the unmanaged document storage unit 65 in step S255 (S257). ). Thereafter, one piece of data currently being processed is deleted from the reference history storage unit 67 (S258), and the process proceeds to the next data (S259). In this way, the processing from step S252 to S259 is repeated for all the data listed in step S251.

  Next, the version mismatch document storage unit 66 is searched to list data referring to the document name (path) of the document to be deleted (S260). Then, the processing from step S261 to S266 is performed on the enumerated data, that is, one case of data that matches the document name (path) of the document to be deleted.

  First, for one of the listed data, a document file of one data currently being processed is added to the unmanaged document storage unit 65 (S262), the print log storage unit 63 is searched, Data that matches the version mismatch document ID of one piece of data being processed is listed (S263). Then, for each of the listed data, the data type 633 is changed to “2”, and the data ID 634 is changed to the unmanaged document ID 651 of the data added to the unmanaged document storage unit 65 in step S262 (S264). ). Thereafter, one piece of data currently being processed is deleted from the version mismatch document storage unit 66 (S265), and the process proceeds to the next data (S266). In this way, the processing from step S261 to S266 is repeated for all the data listed in step S260.

  Thus, even when a document is deleted by the history management system 31, the document deletion inconsistency resolution unit 45 is called to prevent inconsistency of the print log and to ensure that the print log remains.

  Next, an operation when the document update unit 35 of the history management system 31 is called will be described.

FIG. 26 is a flowchart showing a processing flow of the history management system 31 when the document update unit 35 is called.
First, when a document is updated by the history management system 31, the history management system 31 receives a user ID, a document name to be updated, and an updated document file (S 270), and checks from the checkout information storage unit 62. Data in which the user ID of the user performing the out and the document name of the document to be updated match is searched (S271). If there is no matching data as a result of the search (S272: NO), the document update inconsistency resolution unit 46 is not called.

  On the other hand, when there is one or more matching data (S272: YES), one data is added to the history information storage unit 61 (S273), and the matching data is deleted from the checkout information storage unit 62 in step S271 ( S274). Then, the document update inconsistency resolution means 46 of the print log management system 41 is called (S275).

  FIG. 27 is a flowchart showing a processing flow of the print log management system 41 when the document update unit 35 is called. When the print log management system 41 receives the document name (path), version number, and document file of the updated document from the document update unit 35 (S280), the print log management system 41 searches the version mismatch document storage unit 66 and updates it. Data in which the document name (path) of the document matches the document file is listed (S281). If there is no matching data as a result of the search (S282: NO), no particular processing is performed.

  On the other hand, if there is one or more matching data (S282: YES), one piece of data is added to the reference history storage unit 67 (S283), the print log storage unit 63 is searched, and the data listed in step S281 is retrieved. Data matching the version mismatch document ID is listed (S284). At this time, for example, by comparing the hashed document data, it is determined whether or not the binaries match. Then, for each of the enumerated data, the data type 633 is changed to “4”, and the data ID 634 is changed to the reference history ID 671 of the data added to the reference history storage unit 67 in step S283 (S285). Thereafter, the data in which the document name (path) of the updated document matches the document file is deleted from the version mismatch document storage unit 66 (S286).

  In this way, if the document file of the updated document matches the document file saved as the print log when the document is updated, the document name and version number of the updated document are saved as the print log and saved originally. The capacity of the print log is reduced by deleting the document file.

  Finally, another embodiment of the present invention will be described.

  FIG. 28 is a block diagram showing an overall configuration of a client server type print management system including a print log management system 41 according to another embodiment. The same elements as those in FIG. 1 are denoted by the same reference numerals, and redundant description is omitted.

  In the present embodiment, the print log addition method acquisition unit 17 is separated from the plug-in 13 of the print application 11 in the embodiment illustrated in FIG. 1, and the plug-in 13 includes only the pre-print processing unit 14. In addition, the client 10 newly includes a print log addition method storage device 15, and the print log addition method storage device 15 includes a print log addition method setting unit 16 and a print log addition method acquisition unit 17. As a result, the setting and acquisition processing of the print log adding method can be separated from the plug-in 13, so that it is possible to reduce the development burden of application software or plug-in when using the print log management system according to the present invention. become.

  FIG. 29 is a block diagram showing an overall configuration of a client server type print management system including a print log management system 41 according to a further different embodiment. Note that the same elements as those in FIG. 28 are denoted by the same reference numerals, and redundant description is omitted.

  The present embodiment is characterized in that the print log addition method setting unit 16 and the print log addition method acquisition unit 17 are provided not in the client 10 but in the print log management system 41 of the server 30. Since the server 30 includes the print log addition method setting unit 16 and the print log addition method acquisition unit 17, it is not necessary to provide a unit for setting and acquiring the print log addition method on the client 10 side. A server-based computing thin client system that runs on a single server can provide a better system

  According to the above embodiment, it is determined whether or not the print document is being edited. If the print document is being edited, the print job data is saved to ensure that the print content remains in the log and the print document is being edited. Otherwise, it is possible to reduce the capacity of the print log by storing a document file having a size smaller than the print job data.

  In an environment where a document file is stored and the history management system is used, it is determined whether or not the history is managed, and the optimum print log storage method is determined. Furthermore, when a document managed by the history management system is updated, the print log capacity is reduced. Further, when information is added by the printer driver, the print job data is saved even if the print document is not being edited, so that the print contents are reliably left as a log.

  The present invention is not limited to the above-described embodiment, and can be implemented in various other forms without departing from the gist of the present invention. For this reason, the said embodiment is only a mere illustration in all points, and is not interpreted limitedly. For example, the above-described processing steps can be executed in any order or in parallel as long as there is no contradiction in the processing contents.

1 is a block diagram showing the overall configuration of a client server type print management system including a print log management system 41. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a client 10. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a server 30. FIG. 6 is a diagram illustrating an example of a data configuration of a print log addition method storage unit 23. FIG. It is a figure which shows an example of the data structure of the log | history information storage part. It is a figure which shows an example of a data structure of the checkout information storage part. 6 is a diagram illustrating an example of a data configuration of a print log storage unit 63. FIG. 6 is a diagram illustrating a relationship between a value of a data type 633 and an ID indicated by a data ID 634. FIG. 6 is a diagram illustrating an example of a data configuration of a print job storage unit 64. FIG. 6 is a diagram illustrating an example of a data configuration of an unmanaged document storage unit 65. FIG. 5 is a diagram illustrating an example of a data configuration of a version mismatch document storage unit 66. FIG. 6 is a diagram illustrating an example of a data configuration of a reference history storage unit 67. FIG. 4 is a diagram illustrating an example of an information list to be added to a print document as a setting of the printer driver and printed. FIG. 6 is a flowchart illustrating a processing flow of the print application 11 during printing. 6 is a flowchart illustrating a processing flow of the printer driver 18 during printing. It is a flowchart which shows the flow of a process of the pre-printing process means 14 at the time of printing. It is a flowchart which shows the flow of a process of the printing log addition method acquisition means 17 at the time of printing. 7 is a flowchart illustrating a processing flow of a print log and job storage unit 43 during printing. 6 is a flowchart illustrating a processing flow of a print log and document storage unit 42 during printing. It is a flowchart which shows the flow of a process of the document name acquisition means 32 at the time of printing. It is a flowchart which shows the flow of a process of the plate number acquisition means 34 at the time of printing. 7 is a flowchart showing a flow of processing of the history management system 31 when a document name (path) changing unit 37 is called. 10 is a flowchart showing a flow of processing of a document name change inconsistency resolution unit 44 when a document name (path) change unit 37 is called. 7 is a flowchart showing a flow of processing of the history management system 31 when the document deletion unit 36 is called. 7 is a flowchart showing a processing flow of the print log management system 41 when the document deletion unit 36 is called. 6 is a flowchart showing a flow of processing of the history management system 31 when the document update unit 35 is called. 4 is a flowchart showing a processing flow of a print log management system 41 when a document update unit 35 is called. It is a block diagram which shows the whole structure of the client server type | mold print management system containing the print log management system 41 which concerns on other embodiment. It is a block diagram which shows the whole structure of the client server type | mold print management system containing the print log management system 41 which concerns on further different embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Client, 11 Print application, 12 Printing means, 13 Plug-in, 14 Pre-print processing means, 15 Print log addition method storage device, 16 Print log addition method setting means, 17 Print log addition method acquisition means, 18 Printer driver, 19 System spooler, 23 Print log addition method storage unit, 30 server, 31 history management system, 32 document name acquisition means, 33 document file acquisition means, 34 version number acquisition means, 35 document update means, 36 document deletion means, 37 document name (Path) change means, 41 print log management system, 42 document storage means, 43 job storage means, 44 document name change inconsistency resolution means, 45 document deletion inconsistency resolution means, 46 document update inconsistency resolution means, 61 history information Storage unit, 62 Checkout information storage unit, 63 printing Grayed storage unit, 64 print job storage unit, 65 non-managed document storage unit, 66 Ed mismatch document storage unit, 67 reference history storage unit, 70 printer

Claims (11)

A print management system comprising a client for a user to issue a print instruction and a print log management system for managing a print log,
The print log management system includes:
A print log and job storage means for storing print job data of a print document as a print log;
A print log and document storage means for storing a document file of a print document as a print log;
With
The client
A print application that performs print processing in response to a user's print instruction;
When the print application receives the print instruction, if the print document is being edited, the print log and job storage means are called to save the print job data, and if the print document is not being edited, the print document A printer driver that calls the log and document storage means to save the document file;
A print management system comprising: The client
When the print application receives the print instruction, it receives from the print application whether or not a print document is being edited, and print job data and a document file based on whether or not the print document is being edited A plug-in that decides which to save as a print log, and stores the determined save method as a print log addition method,
With
When the print application receives the print instruction, the printer driver acquires the print log addition method stored by the plug-in, and selects any of the print log and job storage unit and the print log and document storage unit. To determine whether to call
The print management system according to claim 1. The print log management system is configured to be able to refer to a history management system that manages a history of a document,
The print log and document storage means obtains history management document identification information in which a document file of a print document is managed by the history management system, and the document name and version number of the document file in the history management system can be identified. If it can, save the history management document identification information as a print log instead of the document file.
The print management system according to claim 1, wherein the print management system is a print management system. The print log management system includes:
A document name change inconsistency resolution unit that resolves an inconsistency related to the change of the document name when the document name of the document managed by the history management system is changed;
Comprising
The print management system according to claim 3. The print log management system includes:
A document deletion inconsistency resolution means for resolving inconsistency related to document deletion when a document managed by the history management system is deleted;
Comprising
The print management system according to claim 3 or 4, wherein The print log management system includes:
When a document managed by the history management system is updated, if the document file of the updated document matches the document file managed as the print log by the print log management system, the document is updated as a print log. Document update inconsistency resolution means for correcting the history management document identification information of the stored document, and
Comprising
The print management system according to claim 3, wherein the print management system is a print management system. The printer driver is
When the printer driver has a list of information to be added to the print document and set to add one or more information from the list, regardless of whether the print document is being edited or not, Calling the print log and job storage means to store the print job data;
The print management system according to claim 1, wherein the print management system is a print management system. In a client configured to be able to communicate with a print log management system that manages a print log, and a user issues a print instruction,
A print application that performs print processing in response to a user's print instruction;
When the print application receives the print instruction, the print log management system saves the print job data if the print document is being edited, and saves the document file if the print document is not being edited. A printer driver to save,
With client. In a print log management system that is configured to be communicable with a client in which a user issues a print instruction and manages a print log,
A print log and job storage means for storing print job data of the print document as a print log if the print document is being edited in the client when the user instructs printing;
A print log and a document storage unit for storing a document file of the print document as a print log when a print instruction is not being edited in the client when the user instructs printing;
A print log management system comprising: A method for managing a print log in a print management system comprising a client for a user to issue a print instruction and a print log management system for managing a print log,
The print application of the client receives a print instruction from a user;
When the print instruction is received, if the print driver is editing the print log management system when the print document is being edited, the client printer driver calls a means for storing the print job data, and the print document is not being edited. Calls a means to save the document file;
The print log management system storing print job data when a print document is being edited in response to a call from the printer driver, and storing a document file when the print document is not being edited; ,
A print log management method comprising:   A program for causing a computer to execute the print log management method according to claim 10.

Images