WO2008104496A1 - Procédé, système d'impression et programme informatique pour le traitement automatique de données d'accompagnement d'une tâche d'impression - Google Patents

Procédé, système d'impression et programme informatique pour le traitement automatique de données d'accompagnement d'une tâche d'impression Download PDF

Info

Publication number
WO2008104496A1
WO2008104496A1 PCT/EP2008/052129 EP2008052129W WO2008104496A1 WO 2008104496 A1 WO2008104496 A1 WO 2008104496A1 EP 2008052129 W EP2008052129 W EP 2008052129W WO 2008104496 A1 WO2008104496 A1 WO 2008104496A1
Authority
WO
WIPO (PCT)
Prior art keywords
ticket
job
rule
print
print job
Prior art date
Application number
PCT/EP2008/052129
Other languages
German (de)
English (en)
Inventor
Thomas Harms
Armin Gnaedig
Original Assignee
OCé PRINTING SYSTEMS GMBH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by OCé PRINTING SYSTEMS GMBH filed Critical OCé PRINTING SYSTEMS GMBH
Publication of WO2008104496A1 publication Critical patent/WO2008104496A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
    • G06F3/1285—Remote printer device, e.g. being remote from client or server
    • G06F3/1288—Remote printer device, e.g. being remote from client or server in client-server-printer device configuration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
    • G06F3/1203—Improving or facilitating administration, e.g. print management
    • G06F3/1205—Improving or facilitating administration, e.g. print management resulting in increased flexibility in print job configuration, e.g. job settings, print requirements, job tickets
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1237—Print job management
    • G06F3/126—Job scheduling, e.g. queuing, determine appropriate device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]

Definitions

  • the invention relates to a method, a computer program and a printing system for automatically processing order-related data of a print job.
  • OCS order distribution system
  • the Order Distribution System is also responsible for the central administration of the production variants. This includes the printing service for intranet and internet users. The Order Distribution System informs users about approved production variants
  • Print jobs together with a digital job bag causes automatic processing until printing.
  • the Order Distribution System also monitors the correct execution of the selected printing and finishing options.
  • the Order Distribution System processes so-called job tickets.
  • a job ticket is a file, in a specific data format, that contains control parameters for controlling the printout of print data of a print job.
  • the job ticket can be used by the user when creating the
  • Print jobs or automatically created in a printing system Print jobs or automatically created in a printing system.
  • Job Definition Format JDF
  • JDF Job message format (Job Messaging Formats or JMF) specified accordingly.
  • JDF Job Messaging Formats or JMF
  • the specification of JDF can be downloaded from the website www.cip4.org, which is currently the current specification JDF Specification Release 1.3.
  • JDF is an XML-based format in which the instructions for the printing process are arranged in a tree structure. Each node of the tree structure includes an instruction or set of instructions. The top one
  • Node is called root.
  • the end nodes at branches are called leaf nodes.
  • JDF JDF
  • intent nodes which contain a very general instruction for a printing process that needs to be specified in order to be executed on a device.
  • US 2002/0080400 A1 discloses a method for a document processing system in which a document processing job can be processed several times in different ways. How the document processing job is processed in detail is controlled by different job tickets.
  • the special feature of this known method is that the different job tickets can be controlled by means of a master job ticket, which is also referred to as a super job ticket, all at once, so that the multiple document processing jobs by means of Master job tickets can be posted at once in the document processing system.
  • US Pat. No. 5,718,520 discloses a method for editing job tickets in which, when a particular control parameter is edited, a window is generated on a display device in which all possible values that can be used for the control parameter are displayed.
  • Oce PRISMAproduction server system includes a print manager PJM (see chapters 15.2.4 and 18.2) with which print jobs can be created on any customer client and edited and managed in this server system.
  • Printj obmanagers is also referred to as a print job manager.
  • server refers to software modules that perform a central task: “Clients” are software modules that are connected to a server and receive data from or transmit data to the server. One server can have several clients in contact at the same time.
  • print jobs are generated by the clients.
  • a print job includes the print data to be printed and a job ticket that includes control parameters for controlling the print data printout.
  • the print jobs can come from different sources.
  • the incoming print jobs are checked and, if necessary, adjusted on the clients upstream of the print job manager.
  • This adaptation may include data or information accompanying the print job, with the content of the job ticket being adapted to the print environment.
  • a job ticket is created on the print order manager from the data accompanying the print job and a default ticket available at the print manager.
  • the format of any incoming job tickets is usually okay, but often contains parameters that are not usable or even lead to contradictions.
  • job tickets often contain printer names that are not present in the existing printing system.
  • computer programs are provided on the clients, which automatically control the job tickets and correct if necessary.
  • These computer programs are programmed as scripts individually for the individual clients and their applications. It is also customary for a number of such scripts to be provided on a client in order, for example, to revise different sources or job tickets with print data in different data formats.
  • These scripts have proven to be very effective, as they automatically check and correct the incoming print jobs so that the entire printing process can run without delay.
  • Print job manager has been fed, and then it must be determined with which script the job ticket has been edited. Even if this is established, it is often difficult to parse the script as to whether it caused the error, or if it caused the error when creating the print job at the customer or when transferring the print job to the client.
  • DE 102 35 124 A1 discloses a method in which already used and screened print jobs can be reused and modified.
  • the "old" print jobs are located on a control device of a printing device. They can be retrieved from a client, with the client requesting the appropriate job ticket from the printing device. This job ticket is then reworked by the client, with instructions inserted to insert the changed pages, so that the unaltered pages from the old print job can be accepted at the printing device and only the pages to be replaced are rasterized.
  • the invention is therefore an object of the invention to provide a method, a printing system and a computer program for automatically processing order-related data for a printing process that allows automatic control of the job tickets without delay of the printing process and yet easy to understand and handle.
  • the inventive method for automatically processing order-related data of a print job comprising control parameters for controlling the print job, in a printing system having a print job manager, one or more clients on which print jobs are generated, and a print server for feeding the print jobs to a print device, comprises the following steps:
  • Order-related data from one of the clients by the print job manager - checking the job-related data according to predetermined, freely programmable ticket rules and outputting a press-specific job ticket, and
  • the method according to the invention is characterized in that the checking of the order-related data according to the predetermined ticket rules is carried out centrally on the print job manager.
  • the ticket rules used for a specific print job are easy to understand, because the ticket rules are only in one place, namely the print job manager, not the print job manager State of the art, the case is available to a variety of clients and there to investigate each. Furthermore, the central execution of the check of the job-related data at the print job manager ensures that all incoming job-related data are checked or checked according to the same ticket rules and, if appropriate, modified and corrected accordingly. Furthermore, by centrally executing the checking of the order-related data, the ticket rules are to be centrally managed, whereby they are also centrally controllable and it is avoided that similar order-related data or similar errors in
  • a further advantage of checking the order-related data centrally at the print job manager is that the checking of the job-related data in the process chain takes place very close to the concrete printing device, so that this check can be carried out very specifically for the respective printing device. This can significantly increase the quality of the review. In the execution of the review of
  • Job-related data to the clients is the problem that the clients with different
  • Print job managers can communicate, so that carried out a check of the job-related data to the printing devices, with the different
  • Print job managers can be reached, which must be adapted, which in turn is very difficult.
  • the central administration of the ticket rules also makes it possible to provide the operator with tools that facilitate the creation and administration of the ticket rules.
  • GUI graphical user interface
  • the central checking of the order-related data enables a uniform check of
  • Job-related data from print jobs coming from different sources Job-related data from print jobs coming from different sources. To explain the present invention, some terms are defined below:
  • a complete order contains at least one
  • Document processing job especially a print job.
  • a print job contains at least one print file to be printed.
  • a total order ticket contains information about an overall order, such as Delivery address, order date, desired delivery date, etc.
  • a job ticket contains all the data required to process a print job. These data include control parameters that are relevant in a workflow for the print job (j ob-workflow).
  • the job ticket is coded in a corresponding ticket format.
  • a default job ticket contains standard data that is suitable for outputting a print job that contains no further processing information in an existing printing system or in an existing printing environment.
  • data are control parameters and may be e.g. Names or addresses of printing devices connected to the respective print server.
  • a data ticket is understood to mean information that is generated by a print job-generating system, for example, a MFS mainframe computer system, together with the print data.
  • the scope of such data is very limited due to the system and its format is not standardized, which is why they are not considered job tickets in the above sense.
  • the order-related data can include both a total order ticket, a job ticket and / or a data ticket or control parameters that are attached to a print job in a different form.
  • Control parameters are often inserted in the file name of the print job.
  • a print system-specific job ticket is generated on the print job manager by means of the default job ticket and possibly further control parameters and the ticket rules. However, if a job ticket is attached to the print job, the job ticket is checked using the ticket rules to determine whether it is suitable as a printing system-specific job ticket and, if necessary, changed - which is the rule - and supplemented in particular by pressure-system-specific parameters from the default ticket.
  • Figure 1 essential parts of a printing system for carrying out the method according to the invention schematically simplified in a block diagram;
  • FIG. 2 shows a screen copy of the graphical user interface of the system according to the invention
  • FIGS. 3 to 7 parts of the screen copy of the graphical user interface of FIGS. 2, and
  • Figures 8 to 17 Copies of windows of the graphical user interface for displaying and editing TicketreggeIn.
  • Print job manager 1 ( Figure 1) automatically processed.
  • Print job manager 1 is connected to several clients 2 (CL).
  • CL Print job manager 1
  • input modules 2/1 input modules 2/1
  • print job client 2/2 print job client 2/2
  • ticket rule client 2/3 ticket rule client
  • a plurality of input modules 2/1 are provided, which are each connected to one or more computers 3 (RE) for generating a print job via data lines 46.
  • the print job manager 1 and the input modules 2/1 are located at an operator of a printing center and the computers 3 for generating the print jobs are at the customers of the operator of the printing system and transmit their print jobs to the input via a network, such as the Internet - Modules.
  • the clients 2 and the print job manager 1 are each computer program units. They can be installed and run on a common computer. However, it is equally possible, and also preferred, to install and execute at least print job manager 1 and clients 2 on at least two separate computers. Interfaces 47 are provided between the clients 2 and the print job manager 1, via which data, in particular print jobs, can be exchanged.
  • the print job manager is also referred to as the PJM server (printjob manager server).
  • the to Print Job Manager 1 Corresponding Print Job Client 2/2 allows the operator of the print system to execute existing print jobs. Such print jobs are, for example, print jobs that could not or could not be printed correctly. With the help of the print job client 2/2, the operator can change the print job and in particular the job ticket of such a print job and transmit the respective print job to the print job manager 1 in order to have it printed on a printing device.
  • the job-related data of the incoming print jobs are supplemented with data, in particular control parameters, from a default job ticket.
  • data in particular control parameters, from a default job ticket.
  • missing, but necessary in the existing printing environment control parameters are added to the job-related data.
  • the data, in particular control parameters of the total order ticket in the print job manager 1 are added to the pressure system-specific job ticket.
  • the so-supplemented pressure system-specific job ticket is taken into account.
  • job ticket is thus understood to mean a printing-system-specific job ticket which is supplemented by data from an overall order ticket or a default job ticket, if such exists.
  • the print job manager 1 has a ticket rule module 4 (TRM) in which ticket rules are stored. The ticket rules are managed by the ticket rule module and executed on the print job manager.
  • TRM ticket rule module 4
  • the ticket rule module 4 has an interface 48 to the ticket rule client 2/3, via which bidirectional communication is possible.
  • Ticket rule client 2/3 includes a rule editor module that Rule module stored ticket rules can be edited.
  • the rule editor module is provided with a graphical user interface (GUI), which will be explained in more detail below.
  • GUI graphical user interface
  • the ticket rule module and / or the rule editor module are designed such that edited ticket rules are automatically checked for a correct syntax. Corresponding errors are displayed on the graphical user interface and, if necessary, a correction proposal is displayed.
  • the ticket rule module 4 may also be connected to multiple ticket rule clients 2/3. However, all ticket rules are stored exclusively in the ticket rule module 4 on the print job manager 1. With the ticket rule clients 2/3, only the ticket rules stored in the ticket rule module 4 can be accessed and these can be changed there.
  • the job ticket contains a list of control parameters for controlling the respective print job.
  • Control parameter list is divided into sections each provided with a name. There is a section called “files.” This section may occur multiple times in a job ticket, but the other sections are provided only once, and within each section are the control parameters with a designation called "key” and a specific one For example, in the section “files” there is a control parameter with the key “File_Copies", where the value of the control parameter is an integer that defines the number of copies to be printed.
  • the ticket rules comprise a sequence of actions that are based on incoming order-related data of the received
  • - message The action message generates a message depending on a specific control parameter of the job-related data.
  • rule With the action rule, another ticket rule is called within a predetermined ticket rule, which is referred to below as a sub-ticket rule. This sub-ticket rule is called in dependence of one or more control parameters of the order-related data.
  • - break The break action immediately stops the execution of the ticket rule, and if the ticket rule that terminates should be a sub-ticket rule, the parent ticket rule continues.
  • - exit The exit action immediately stops the execution of the ticket rule. This will not continue with a parent ticket rule.
  • - exit and stopjob This action immediately stops the execution of the ticket rule. It does not continue with a higher-level ticket rule and the processing of the print job is also terminated.
  • switch / case This action compares a value of an order-tracking data control parameter with each value specified in a first column of a table. If there is a match with one of the values, the values of the row of this table are automatically entered into corresponding data fields, in particular into a corresponding table in the ticket rule. This allows the automatic transfer of records from tables, whereby the tables outside the ticket rules can be edited with a conventional spreadsheet program.
  • the sequence of actions of a ticket rule can be branched as in a tree, whereby the branches are respectively executed by the conditions "condition” or “else” and the leaves of the tree are represented by actions which then occur when the respective condition occurs ( en).
  • the ticket rules can be freely programmed, analogous to the client-specific scripts mentioned at the beginning.
  • job-related data can be corrected (e.g., with setting), i.e., parameters in the job-accompanying data that are inappropriate for the existing print environment can be replaced or deleted.
  • These actions are therefore very powerful, as they can fundamentally change the parameters in order-related data. It is even possible to cancel print jobs (exit, stopjob).
  • the ticket rules make it possible to check the order-related data for correctness, ie to check whether the print job can be printed correctly with the job-related data on the respective printer or printing system. This check is carried out, for example, with the action condition.
  • the ticket rules can be used to output a message which, for example, informs the operator of an error in the order-related data or requires a specific action of the operator on the system which is necessary for the further execution of the print job, such as insertion special paper or the supply of special toner.
  • the ticket rules can be programmed on different clients, since they are stored centrally, the operator or another person who can influence the ticket rules always has access to the entire set of ticket rules. This avoids errors that occur in conventional systems in which the corresponding instructions for influencing the order-related data are stored distributed on different computers and the operator often has no overview of all rules.
  • order-related data from different sources can be checked centrally at a single point and, if necessary, corrected.
  • the ticket rules thus serve the central and uniform review of
  • Job-related data of different print jobs are Job-related data of different print jobs.
  • the print job manager 1 is arranged with its ticket rule module 4, in which the ticket rules are stored as close as possible to the printer or to the printers, so that the ticket rules are specifically defined for the respective printing environment.
  • the print job manager 1 is directly connected to one or more printers or there is only one print server each between the print job manager 1 and one of the printers. It is also within the scope of the invention possible to integrate the print job manager into the printer.
  • Print job manager 1 forwarded, in which case forwarding or transmission of the print job from the client 2 to the print job manager 1, a function is called, which carries out the processing of the respective print job.
  • a function is called, which carries out the processing of the respective print job.
  • a parameter is passed from the client 2 to this function, which contains a reference to a corresponding ticket rule with which the order-related data of the print job are checked.
  • This function therefore calls the ticket rule on print job manager 1, depending on the parameter passed
  • FIG. 1 A screen print of the graphical user interface of the ticket rule client 2/3 is shown in FIG.
  • the graphical user interface comprises a Main Toolbar 5, a Ticket Rules drop down menu 6, a Rule Definition window 7, a Rule definition tool bar 8, and Rule definition bar 8 a rule activation list 9 (RuIe activation list).
  • the main strip 5 is shown in Figure 3 in an enlarged view again. It has seven pictograms 10, 11, 12, 13, 14, 15, 16. By clicking on one of the pictograms with a computer mouse, a specific function can be triggered.
  • the pictogram 10 stores the current configuration of the ticket rules. These changes are stored in ticket module 4. Should be on the graphic User interface changes have been made to ticket rules, they are only applied to incoming order-related data when the icon 10 has been pressed, that is, when they are stored in the ticket control module 4.
  • a new rule is generated. The user is first asked for the name of the new rule. The new rule is then appended to the rule activation list 9 and is activated. It does not contain any actions yet.
  • an existing ticket rule can be copied to a new ticket rule. Again, the user is first asked for the name of the new ticket rule. All actions of the copied ticket rule are copied to the new ticket rule.
  • the icon 14 is used to delete a ticket rule.
  • the ticket rules listed in the rule activation list 9 can be moved up or down by one step at a time.
  • FIG. 4 shows the pop-up menu 6 in the unfolded state, in which the functions explained above with reference to the pictograms 10 to 16 can be called up.
  • rule activation list 9 (FIG. 5) all ticket rules are listed in tabular form.
  • the activation state is indicated, in a second column the rule name and in a third column a rule description.
  • This rule description can either be generated automatically from the existing sequence of actions or can be entered manually via a separate window.
  • the generated description or the self-generated description can be displayed. The manually created description is saved together with a corresponding rule.
  • a user can specify whether a particular rule should be in the "active" or “inactive” mode.
  • the "inactive” mode is used when a particular rule is not to be applied to incoming job tickets, which is appropriate for old rules that are not going to be used temporarily or for new rules that have not yet been sufficiently tested to define a ticket rule for later use.
  • a rule can be set if it is executable and not a sub-ticket rule.
  • the individual rules are automatically checked by the rule module 4 for their executability, that is, for the correctness of their syntax If the rule is executable, it will be displayed in black in the rule activation list, but if it is not executable, it will be displayed in red in this list.
  • a ticket rule with sub-ticket rule mode can only be used as a sub-ticket rule, which means that it must be called by another parent rule Rule Activation List 9 shown in italics in black for executable and in red for rules not executable. Double-clicking an element in the third column (rule description) opens a window ( Figure 8) for editing the rule description. If the pictogram "Ok" is clicked in this window, the corresponding rule description is adopted.
  • the rules definition bar 8 (FIG. 6) includes icons 17, 18, 19, 20, 21, 22, 23, 24, 25, and 14 that correspond to the
  • a condition definition window 26 (FIG. 10) is called, with which conditions can be edited. This will be explained below.
  • Each setting definition includes a name, a control parameter, a value, and an override flag.
  • a set definition serves to set a control parameter in the job ticket to a specific value. This is explained in more detail below.
  • the icon 19 is used to add and edit variables. Upon actuation of this icon, a variable editor window 28 is opened (FIG. 12).
  • the icon 20 is used to open a
  • sub-ticket rules can be added. From a list of all defined sub-ticket rules one can be selected.
  • the icon 22 is used to add the condition "eise" into a sequence of actions.
  • the icon 23 is used to add the action "break" into a sequence of actions.
  • the icon 24 is used to add the action "exit" in a series of actions.
  • the icon 25 is for adding the action "exit and stopJob" to a sequence of actions.
  • a selected action can be deleted from a sequence of actions.
  • Action definition window provided. These windows each display a list of all the present actions of a type and allow editing, adding new actions, removing actions and copying actions. Each action has a specific status. Only correctly defined actions receive the status "true”, which is represented by a black font, and with a status "false” the color of the font is red. An example of an action with a "false” status would be a condition without a defined control parameter.
  • Control definition window 7 a suitable icon for adding an action (icon 17 to icon 25) in the rule definition bar 8 is clicked.
  • the action definition window can be left by clicking on a "Cancel” or "OK” icon.
  • the "OK” pictogram can only be selected if a valid entry of an action is selected
  • Action definition window has been called from the rule definition window 7 by means of a suitable add icon, the new action is added to the existing sequence of actions after the selected action. If the action definition window is called by clicking on a specific action in the rule definition window 7, the action selected in the rule definition window 7 is replaced by the new action defined.
  • Actions that are currently not used by any rule can be deleted.
  • a window pops up listing the names of all ticket rules that use this action and the
  • Every action can have a specific name. This name is unique to all ticket rules and allows the actions to be called globally in all ticket rules. This means that if an action is changed with a global name, all ticket rules will be the use this action, be changed. However, an action can also be provided without a name. But then it can only be called in a single ticket rule.
  • the action definition windows have a column for control parameters.
  • This control parameter column provides a special combo box for entering a ticket section and a control parameter (key). If the control parameter column is empty and the combo box is selected, a list of all known sections will be displayed. Thereafter, the user can recall the combo box and a list of all keys of the selected section is displayed. This allows the control parameter to be selected by clicking twice without having to call up an extensive list of all control parameters. If one
  • Section and a control parameter have been selected, a field "..” is also offered to go back to the first mode of the combo box, which displays only the list of known sections.Also, an empty field is offered in which a new section or a new key can be entered Control parameters can be deleted from the list of known control parameters.
  • the action definition window for conditions includes a condition definition menu bar 31 and a condition definition table 32.
  • Condition definition menu bar 31 includes the above-explained icons 13, 14 and 17 with the respective functions of adding, deleting and copying conditions.
  • Each condition contains a parameter, an operator and a value and can be given a name.
  • the respective section and key can be from one
  • Each pop-up window can be selected.
  • the offered list of keys depends on the selected section.
  • the operator can be selected from a pop-up window.
  • - is a hexadecimal digit (0-9, A-F, a-f)
  • a value can refer to a variable. Variabein are represented by "$ ⁇ variable-name ⁇ " For example, it is possible to check if the printer name is the same as the job name The definition of variables is described below.
  • the parameter Combo-Box also allows a special variable selection. If this is selected, a list of all defined variable names will be displayed.
  • the section "Files” needs a special treatment because it can occur multiple times, a condition in the "Files” section is true if it applies to at least one section. If a setting action follows this condition, then this set action will be executed only in the file sections that satisfy these conditions. If a set action is defined in a file section that does not follow a condition using the file section, then the set action will be performed in all file sections.
  • condition definition table 33 The definition of a condition is always automatically checked for correctness. If there should be errors, such as a reference to an undefined variable or to a control parameter containing only one key, then the condition action defined in red in the condition definition table 33 is displayed. If the condition is correct, it will be displayed in black.
  • Set actions are defined in the set definition window 27 (FIG. 11), which includes a setting definition menu bar 33 and a setting definition table 34.
  • the set definition menu bar 34 includes pictograms 18, 13 and 14 already explained above for adding, deleting and copying set actions. Furthermore, it includes a pictogram 35, with which job tickets can be imported.
  • a window displays all available job tickets. After selecting such a job ticket, it will be imported with all its actions, keys and values and can now be edited. This feature is primarily intended to generate default job tickets from the Print Order Manager 1 with the job-in-order data of the incoming print jobs and supplement missing control parameters in incoming order-related data.
  • Each set action includes at least one parameter, a value, and an override flag, and may be named.
  • a value can refer to a variable.
  • a value may also be set to "[delete]" meaning that the entire entry of the control parameter up to the keys in the job ticket is to be deleted, unlike the entry "" with which nothing is entered in the key becomes.
  • Override flag to be set The default status is a set overwrite flag.
  • the section "files" needs a special treatment as this section can occur multiple times, so if a set action follows a condition in a file section that is true when applied to such a file section, then that set becomes If a set action is defined in a file section and does not depend on a condition that uses the file section, then the set action applies to all file sections. sections.
  • variable editor window 28 For editing variables, the variable editor window 28 (FIG. 12) is provided.
  • the variable editor window 28 includes a variable definition menu bar 36 and a variable definition table 37.
  • Each variable has at least one unique variable name and parameter.
  • the name is necessary to call a variable.
  • All variables represent global entries. Variables are called in the following form $ ⁇ variable name ⁇ .
  • variable definition table 38 includes other columns "Alteration Type" and "Alteration Code".
  • a statement can be defined with which the content of the variable is changed when a control parameter for the variable is incoming
  • variable definition table 37 the corresponding variable is clicked in the variable definition table 37.
  • clicking on the corresponding fields in the columns "Alteration Type” and "Alteration Code” respective drop-down menus open from which suitable entries can be selected.
  • a field definition window 38 opens with which data fields are defined individual field entries are separated in a string. If no field delimiter is specified, then this character is a separate data field. As a field delimiter, only a single character can be entered.
  • the input fields "From Field” and "To Field” can be used to enter the range of data fields to be extracted from a predefined string.
  • the data fields are numbered twice, namely with positive integers, whereby the data field arranged at the left edge is assigned the value 1 and these values are increased from one field to the other by 1 in each case.
  • the numbering on the right arranged data field ends with the value -1 and decreases from data field to data field by 1 in the direction to the left.
  • This numbering for the string "Testring” is an example of this numbering for the string "Testring":
  • This field definition is primarily used to cut out strings. However, it can also be used to cut certain numeric records.
  • variable definition table 37 the entry "Replacement” can be entered in the "Alteration Type” column, with which predetermined character strings are replaced by other character strings.
  • a replacement definition window 39 opens in which a searched string is entered in the data field row "Find” and the string used to replace the searched string is entered in the data field line "Replace".
  • the number of replacements to be performed can be entered in the data field line "Occurances", where either a whole positive number or "all” is entered, which means that all found character strings are replaced. Setting a flag will replace the string regardless of the case. Also in this replacement definition window 39 there is again an example line “Example” in which a string is indicated, which in the line arranged thereunder corresponds to the defined one
  • a calculation definition window 40 opens (FIG. 15).
  • an operator of one of the four basic operations "+”, “-", “*”, or “/” can be entered in a field 41, and in a field 42 the calculation value, which with the corresponding operator is set to a variable for integers or floating-point numbers are applied.
  • the system according to the invention allows the output of messages when the ticket rules on
  • Print Job Manager 1 can be selected. This is particularly advantageous in connection with the central execution of all ticket rules, since these messages, which are primarily warnings and error messages, are output centrally at one point in the print job manager and so a reliable monitoring of the same is possible.
  • This window comprises a message definition menu bar 43 and a message definition table 44.
  • icons 20, 14, 13 for adding, deleting and copying a message are listed.
  • Each message includes a message identifier ("Message-ID”), a message type ("Type”), a short message text (“Short Text”), a long message text (“Long Text”) and an optional text ("Optional Text At least one short and one long message text must be entered for the message to be valid.
  • Message-ID message identifier
  • Type message type
  • Short Text short message text
  • Long Text long message text
  • Optional Text At least one short and one long message text must be entered for the message to be valid.
  • ⁇ br /> ⁇ br /> Variables can also be used in the message text whose contents are displayed when they are called up.
  • the message After creating a message, the message is always checked for correctness. If the message is incorrect, it will be displayed in red, otherwise in black.
  • a sub-rule window 45 ( Figure 17) is opened, in which all sub-ticket rules are listed. Adding new sub-ticket rules is done in Rule Activation List 9 by changing the corresponding entry for a particular rule to Sub-Rule in the Activation column, so the sub-rule Window 45 for information only and not for editing the sub-ticket rules.
  • the print jobs processed with the associated order-related data automatically to the print job manager 1, wherein after a predetermined ticket rule a printing system-specific job ticket is generated.
  • a ticket rule it is also possible for a ticket rule to be called explicitly in the order-related data, so that control parameters of the job ticket or data ticket are not accidentally changed. To do this, enter the following command in the order-related data:
  • the entry of the ticket rule in the order accompanying data can be done on the client 2 or at an upstream processing stage and / or when creating the job-accompanying data.
  • a SuperTicket rule which basically checks all incoming order-related data according to predetermined criteria and parameters and, depending on the check, invokes a respectively suitable ticket rule, if one exists, or an incoming job - Forwards ticket without further verification by a ticket rule.
  • no corresponding references to ticket rules are to be entered in the order-related data or no corresponding parameter must be entered when the request is made.
  • the invention relates to a method, a printing system and a computer program for automatically processing order-related data of a print job.
  • incoming order-related data of a print job to a print job manager are checked centrally by means of predetermined ticket rules and optionally supplemented or changed by further printing parameters, so that from the order accompanying data a printing system-specific job ticket is formed, with which the print job can be printed correctly in the respective printing system.
  • the central check of the order-related data at the print job manager allows an easy administration of the ticket rules and due to the proximity to the print server and the connected printing devices a very printing system-specific processing of the job tickets is possible.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Economics (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Computer Hardware Design (AREA)
  • Data Mining & Analysis (AREA)
  • Accessory Devices And Overall Control Thereof (AREA)

Abstract

L'invention concerne un procédé, un système d'impression et un programme informatique pour le traitement automatique de données d'accompagnement d'une tâche d'impression. Selon l'invention, les données d'accompagnement entrantes d'une tâche d'impression sont vérifiées de manière centralisée au niveau d'un gestionnaire de tâches d'impression au moyen de règles de fiche prédéfinies, et sont éventuellement complétées par d'autres paramètres d'impression, de sorte qu'on forme à partir des données d'accompagnement une fiche de travail spécifique du système d'impression, avec laquelle la tâche d'impression peut être correctement exécutée dans le système d'impression respectif. La vérification centralisée des données d'accompagnement au niveau du gestionnaire de tâches d'impression permet une gestion simple des règles de fiche, et la proximité du serveur d'impression et des appareils d'impression raccordés à ce dernier permet un traitement des fiches de travail très spécifique du système d'impression.
PCT/EP2008/052129 2007-02-28 2008-02-21 Procédé, système d'impression et programme informatique pour le traitement automatique de données d'accompagnement d'une tâche d'impression WO2008104496A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102007009737.0 2007-02-28
DE102007009737A DE102007009737B4 (de) 2007-02-28 2007-02-28 Verfahren, Drucksystem und Computerprogramm zum automatischen Bearbeiten von Auftragsbegleitdaten eines Druckauftrages

Publications (1)

Publication Number Publication Date
WO2008104496A1 true WO2008104496A1 (fr) 2008-09-04

Family

ID=39469531

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2008/052129 WO2008104496A1 (fr) 2007-02-28 2008-02-21 Procédé, système d'impression et programme informatique pour le traitement automatique de données d'accompagnement d'une tâche d'impression

Country Status (2)

Country Link
DE (1) DE102007009737B4 (fr)
WO (1) WO2008104496A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8488189B2 (en) 2007-08-06 2013-07-16 OCé PRINTING SYSTEMS GMBH Method for the creation of a template
CN110084567A (zh) * 2019-04-26 2019-08-02 深圳前海微众银行股份有限公司 电子印章使用方法、装置、设备及计算机可读存储介质
CN111756799A (zh) * 2020-05-20 2020-10-09 拉扎斯网络科技（上海）有限公司 一种打印信息的处理方法及装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4861480B2 (ja) 2006-09-22 2012-01-25 オーセ プリンティング システムズ ゲゼルシャフト ミット ベシュレンクテル ハフツング 印刷データの自動的な伝送、特に印刷ジョブのミラーリングのための方法及びシステム
DE102007036986B4 (de) 2007-08-06 2011-06-16 OCé PRINTING SYSTEMS GMBH Verfahren zum automatischen Aufbereiten und Trennen von in einem Dokumentendatenstrom enthaltenen Dokumentenbearbeitungsdaten
DE102007036985B4 (de) 2007-08-06 2010-12-16 OCé PRINTING SYSTEMS GMBH Verfahren, System und Computerprogrammprodukt zum automatischen Aufbereiten von Dokumentenbearbeitungsdaten

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040111430A1 (en) * 2002-12-10 2004-06-10 William Hertling System and method for dynamic sequencing of a requirements-based workflow
US20050004893A1 (en) * 2003-07-02 2005-01-06 Sangroniz James M. Workflow management devices and systems, and workflow assignment and management methods
US20050043845A1 (en) * 2003-08-07 2005-02-24 Hewlett-Packard Development Company, L.P. Managing workflow in a commercial printing environment with high performance prepress rework at print service provider location

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5718520A (en) 1995-05-22 1998-02-17 Xerox Corporation Apparatus and method for modifying a print job ticket
US7242490B1 (en) 2000-10-10 2007-07-10 Hewlett-Packard Development Company, L.P. Internet print managing system and method with print job distribution
US7405836B2 (en) 2000-12-26 2008-07-29 Xerox Corporation Job submission system and method for controlling multiple job renderings with a single master or “super” ticket
JP3947062B2 (ja) * 2002-08-21 2007-07-18 大日本スクリーン製造株式会社 印刷システム、印刷データ作成装置、印刷装置、印刷物の一部変更印刷方法、およびプログラム
DE102004047327A1 (de) * 2004-09-29 2006-04-06 OCé PRINTING SYSTEMS GMBH Verfahren und System zum automatischen Bearbeiten eines Jobtickets für einen Druckprozess

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040111430A1 (en) * 2002-12-10 2004-06-10 William Hertling System and method for dynamic sequencing of a requirements-based workflow
US20050004893A1 (en) * 2003-07-02 2005-01-06 Sangroniz James M. Workflow management devices and systems, and workflow assignment and management methods
US20050043845A1 (en) * 2003-08-07 2005-02-24 Hewlett-Packard Development Company, L.P. Managing workflow in a commercial printing environment with high performance prepress rework at print service provider location

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8488189B2 (en) 2007-08-06 2013-07-16 OCé PRINTING SYSTEMS GMBH Method for the creation of a template
CN110084567A (zh) * 2019-04-26 2019-08-02 深圳前海微众银行股份有限公司 电子印章使用方法、装置、设备及计算机可读存储介质
CN111756799A (zh) * 2020-05-20 2020-10-09 拉扎斯网络科技（上海）有限公司 一种打印信息的处理方法及装置
CN111756799B (zh) * 2020-05-20 2023-04-07 拉扎斯网络科技（上海）有限公司 一种打印信息的处理方法及装置

Also Published As

Publication number Publication date
DE102007009737A1 (de) 2008-09-04
DE102007009737B4 (de) 2010-09-16

Similar Documents

Publication Publication Date Title
EP1155850B1 (fr) Dispositif et procédé pour afficher et contrôler le flux de travaux de la production d'impression dans la production d'impression à haute performance
DE69614034T2 (de) Rechnersystem
DE69820413T2 (de) Gebraucherschnittstelle für einen drucker/kopierer, an einer entfernten stelle eines internet/intranetzes
DE69725451T2 (de) Drucken in offenen systemen
EP1156437A2 (fr) Interface et méthode de manipulation de documents composés
DE10122880A1 (de) Automatische Erzeugung von Druckanweisungen
EP1156412A2 (fr) Utilisation efficace de moyens de traitement de supports d'impression dans un flux de données de tâche d'impression
EP1859340A2 (fr) Procede pour generer des ordres d'impression dans un systeme d'impression, procede pour trier des travaux d'impression dans un systeme d'impression, programme informatique et systeme d'impression pour realiser ces procedes
DE102007009737B4 (de) Verfahren, Drucksystem und Computerprogramm zum automatischen Bearbeiten von Auftragsbegleitdaten eines Druckauftrages
EP1565810B1 (fr) Systeme et procede de production automatique de fichiers de donnees imprimables
DE10252797A1 (de) Verfahren und System zum Erstellen von Dokumentenvorlagen mit Ressourcenverwaltung
DE102007037032A1 (de) Verfahren zum Erzeugen eines Templates
EP2199908A1 (fr) Procédé d'accès à un support de transmission
DE102006006060A1 (de) Verfahren und Anordnung zum Archivieren von Dokumentendaten sowie zum Ausgeben von in einem Archiv gespeicherten Dokumentendaten
DE19849962A1 (de) Vorrichtung und Verfahren zum Aufteilen eines Druckauftrags unter mehreren Druckern
DE102004047327A1 (de) Verfahren und System zum automatischen Bearbeiten eines Jobtickets für einen Druckprozess
EP1156411A2 (fr) Distribution flexible de tâches d'impression à des stations de traitement
DE102007036985B4 (de) Verfahren, System und Computerprogrammprodukt zum automatischen Aufbereiten von Dokumentenbearbeitungsdaten
EP1282883A2 (fr) Procede et systeme de transformation de flux de donnees d'impression numeriques, imprimante et serveur d'imprimante correspondants
EP3244298B1 (fr) Producteur de tâches comprenant une détection de tâches centralisée
DE10203868A1 (de) Verfahren, Empfangsserver und Computerprogramm-Modul zur automatisierten Annahme und Weiterleitung von Dokumentenbearbeitungsaufträgen
EP1470473A2 (fr) Procede, systeme informatique et module de programme d'ordinateur pour l'etablissement d'instructions de traitement de documents a partir de donnees variables, individuelles par page et a partir de donnees de ressources
DE102007036986A1 (de) Verfahren zum automatischen Aufbereiten und Trennen von in einem Dokumentendatenstrom enthaltenen Dokumentenbearbeitungsdaten
DE10337837B4 (de) Computergesteuertes Drucksystem, Verfahren zum Ansteuern eines solchen Systems und entsprechendes Computerprogrammprodukt
WO2001088748A2 (fr) Procede pour etablir un document de sortie dans un systeme informatique

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08709163

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08709163

Country of ref document: EP

Kind code of ref document: A1