The present disclosure relates to printing, and more particularly, to recording and updating various print history information into an electronic document as part of the electronic document's properties.
Various application programs generate information about electronic files/documents as the electronic files/documents are created within the application programs. Information is typically saved within an electronic document under various properties of the document. These properties are viewable by users through a document properties tab accessible through a pull-down menu within an application. Although the information can vary from application to application, it is typically related to the document's creation. The information might therefore be categorized in properties such as an origination property that includes the document's author, creation date, revision number, who last saved the document and the date they saved it. Another property might be a statistical property containing information such as the number of pages, paragraphs, lines, words, and characters the document contains.
Although such information may be useful to the author of a document, it does not help in understanding what happens to the document after the document has been completed. Information regarding how a document is used after it has been created may be useful for various purposes. For example, print history information including when, where, and by whom a document has been printed may be a useful tool to help track the use of the document. Such information may be of particular benefit for tracking secure documents that have restricted access. Such print history information might also be useful in maintaining document databases and for metrics reporting purposes. For example, documents that have little or no print history over a given time period may be deemed to be of no use and therefore removed from a database, while those with recently active print histories might be retained in the database as still being useful.
Accordingly, the need exists for a way to accumulate print history information for individual electronic documents, maintain associations between individual electronic documents and their corresponding accumulated print history information, and present accumulated print history information to users regarding individual electronic documents.
During the printing process of an electronic document, a print driver is configured to record print history information about the printing process into the electronic document.
In a particular embodiment, a print driver receives an electronic document from an application program executing on a client computer. The driver formats the document into a printer-friendly format and sends the document to a printer to be rendered as hardcopy output. During this process, the driver records information into the electronic document regarding the print process. Print history information for each print instance of an electronic document is made available to a user through a print history option in the electronic document's properties.
The same reference numbers are used throughout the drawings to reference like components and features.
The present disclosure relates to generating print history information regarding an electronic document and recording the information into a print history property within the electronic document. Print history information includes details of each print instance, such as the date and time a document is printed, the printer used, and the computer device providing the print job. Advantages of the disclosed system and methods for creating a document print history include an ability to determine particular users who print restricted-access documents and an ability to maintain document databases.
Exemplary System Environment for Creating a Document Print History
Input device(s) 102 can be implemented as a variety of general purpose computing devices including, for example, a personal computer (PC), a laptop computer, a Macintosh, a workstation computer, and other devices configured to communicate with printing device(s) 104. An input device 102 typically provides a user with the ability to manipulate or otherwise prepare in electronic form, an image or document to be rendered as an image that is printed or otherwise formed onto a print medium by a printer 104 after transmission over network 106. In general, input device 102 outputs data to printer 104 in a suitable PDL (page description language) driver format, such as PCL or PostScript. In addition, input device 102 is configured to record print history information into electronic documents/files as discussed more fully below with respect to particular embodiments.
This disclosure is applicable to various types of printing devices 104 capable of rendering PDL data in printed form on a print medium, such as printing pixels on paper. Therefore, printing devices 104 can include devices such as laser-based printers, ink-based printers, dot matrix printers, dry medium printers, plotters and the like. In addition, printing devices 104 might also include various multi-function peripheral (MFP) devices that combine a printing function with other functions such as facsimile transmission, scanning, copying and the like. In general, a printer 104 receives input data as a print job in a suitable PDL format transmitted by input device 102 over network 106. Printer 104 is configured to render the print job as a hard copy image document formed on various print media, such as paper or transparencies.
Exemplary System Embodiment for Creating a Document Print History
Client computer 102 typically includes a processor 200, a volatile memory 202 (i.e., RAM), and a nonvolatile memory 204 (e.g., ROM, hard disk, floppy disk, CD-ROM, etc.). Nonvolatile memory 204 generally provides storage of computer/processor-readable instructions, data structures, program modules and other data for client computer 102. Client computer 102 may implement various application programs 206 stored in memory 204 and executable on processor 200 to create or otherwise form an electronic document or image (e.g., text and/or graphics) such as electronic document 208 on a computer display screen 210. Such documents/images are transferable over network connection 106 to printer 104 for creating hard copies of the documents/images. Applications 206 typically include software programs implementing, for example, word processors, spread sheets, network browsers, multimedia players, illustrators, computer-aided design tools and the like.
Client computer 102 may also implement one or more software-based device drivers such as printer driver 212 that are stored in memory 204 and executable on processor 200. Device drivers might also be implemented on the specific devices they are “driving” such as printer 104. In general, printer driver 212 formats document information into a page description language (PDL) such as PostScript or Printer Control Language (PCL) or another appropriate format which is output to printer 104. In the current embodiment, printer driver 212 additionally includes a print history module 214 generally configured to generate print history information 216 and record it into electronic document files 208 as discussed more fully herein below.
Printer 104 of the
As mentioned above, client computer 102 implements printer driver 212, which includes print history module 214. Print history module 214 is configured to record print history information 216 into an electronic document 208 during a print process for the electronic document 208. Typically a print process is initiated from within an application program 206 by a user selecting a print command. The print command initiates a print process for an electronic document 208 that has been created or otherwise accessed by an application program 206. For example, a user working in a word-processing application such as Microsoft® Word®, may finish writing a document and select the print command from within the application, which initiates a print process through printer driver 212.
Generally, during the creation of an electronic document 208 within an application program 206, information related to the creation of the electronic document 208 is generated by the application program 206 and stored in the electronic document 208 as a property of the electronic document 208.
Print history module 214 functions in a similar manner to gather or generate information related to the process of printing an electronic document 208, and to record or save that information as print history information 216 into the electronic document 208. Thus, the document properties of
Exemplary Methods for Creating a Document Print History
Example methods for creating a print history of an electronic document will now be described with primary reference to
Referring to the method illustrated in
Referring now to the method illustrated in
Referring now to the method illustrated in
At block 604 of
Although the description above uses language that is specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the invention.
Additionally, while one or more methods have been disclosed by means of flow diagrams and text associated with the blocks of the flow diagrams, it is to be understood that the blocks do not necessarily have to be performed in the order in which they were presented, and that an alternative order may result in similar advantages.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6411970 | Aitken et al. | Jun 2002 | B1 |
| 6918082 | Gross et al. | Jul 2005 | B1 |
| 20020051166 | Tomita | May 2002 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20040021708 A1 | Feb 2004 | US |