Job Ticket Generator: JDF

Note: This node works with PDF files (version 1.3 or later).

Use the Job Ticket Generator: JDF Node to create or update a JDF file with the corresponding metadata values of Dispatcher by using a Mapping Table file. If the JDF file path exists, the existing JDF file is updated with the corresponding metadata. If the JDF file path does not exist, the Job Ticket Generator: JDF Node loads the JDF file (IDP) and updates it with the corresponding metadata values.

If the submitted job ticket is either a ResourcePool or ResourceLinkPool item, the node will create the corresponding ResourceLinkPool or ResourcePool item (if it does not already exist). Both are then linked with a unique reference ID. If the value of JDF/@Type is Combined (IDP), the node will update the CombinedProcessIndex attribute of the ResourceLinkPool element based upon the suitable process type located in JDF/@Types. If a suitable process does not exist in JDF/@Types, the node will append a suitable process to JDF/@Types and update the corresponding CombinedProcessIndex.

The default Usage attribute value updated for any ResourceLinkPool item is Input, unless explicitly mentioned in the mapping table or when the element is already present in the input JDF file.

Using the Job Ticket Generator: JDF Node

Add the Job Ticket Generator: JDF Node to the workflow by dragging the node’s icon onto the Workflow Builder canvas, and then double-clicking on the icon to open the Job Ticket Generator: JDF Node:

Use this window to create or import a mapping table by using a dependent UI component mapping table editor.

• Select the Enabled checkbox so that the process will run. When unchecked, this process is ignored. Documents pass through as if the node were not present (i.e., continue along the default or positive path). Note that a disabled node will not check for logic or error conditions.

• In the Node Name field, enter a meaningful name for the Job Ticket Generator: JDF Node.

• In the Description field, enter a description for the Job Ticket Generator: JDF Node. This is not required, but can be helpful with multiple collection points. If the description is long, hover the mouse over the field to read its entire contents.

• Click the Save button to save the changes. If Cancel is selected and the window is closed, the changes are not saved.

• Click the Help button to access online help.

Output Data Format

In the Output Data Format area, select the node output format:

The following options are supported:

• JDF (with File URL to PDF): A local PDF’s URL is included in the generated job ticket’s JDF file.

• JDF (with Local File to PDF): A local PDF file path is included in the generated job ticket’s JDF file.

• ZIP (JDF+PDF): The node generates a JDF and a PDF file.

• Mime (JMF+JDF+PDF): The node generates a Mime (MJM) file.

• JDF (with Network share to PDF): Network shared PDF file path is included in the generated job ticket’s JDF file.

  Note: The MJM file contains the job ticket information and PDF content. The extracted job ticket file and PDF file are processed. The job ticket information in the MJM file contains JMF, JDF, and PDF content in the form of base 64.

Category Panel

There are eleven job ticket parameter Categories (all noted in the image below). To display the setting values of a Category, click one of the eleven options:

• Job Settings: Select this option to edit the job ticket parameters of the following values: Job Ticket Number, Job Ticket Name, Job Priority, Due Date, Color Mode, High Quality Color, or Job Description.

• Basic Settings: Select Basic Settings to edit the job ticket parameter of Copies, Collate, Offset, Offset Copies, Offset Pages, Paper Catalog ID, Paper Name, Paper Source, Paper Weight, Paper Type, Paper Color, Paper User Color, Use Perforated Paper, Paper Size, or Orientation.

• Layout Settings: Select this option to edit the job ticket parameters of the following values: Imposition, or Printing Type.

• Cover Sheet Settings: Select this option to edit the job ticket parameters of the following values: Front Cover, Front Cover Paper Name, Back Cover, or Back Cover Paper Name.

• Finishing Settings: Select Finishing Settings to edit the job ticket parameter of Binding Position, Saddle Stitch, Trim, Staple, Punch, Folding, Perfect Binding, Perfect Binding Mode, Perfect Binding Tray, Perfect Binding Duplex, Perfect Binding Spine, Perfect Binding Cover Size, Perfect Binding Cover Weight, Ring Binding, Ring Binding Front Cover, or Ring Binding Back Cover.

• Inter Sheet Settings: Select Inter Sheet Settings to edit the job ticket parameter of PPS Print Type, PPS Binding, PPS Paper Catalog ID, PPS Paper Name, PPS Paper Source, PPS Paper Type, PPS, PPS Paper Size, PPS Paper Weight, PPS Paper Color, PPS Paper User Color, PPS Use Perforated Paper, PPS Paper Tab Type, PPS Number of Inserts, PPS Staple, PPS Punch Setting, PPS Punch, or PPS Finish Stapling.

• Tab Settings: Select Tab Paper Size, Tab Paper Weight, Tab Text, Tab Sheet Page Number, File Order, or Number of Tabs.

• Image Quality Settings: Select this option to edit the job ticket parameters of the following value: Resolution.

• Customer Information: Select this option to edit the job ticket parameters of the following values: Comment URL, Customer’s First Name, Customer’s Last Name, Customer’s Address 1, Customer’s Address 2, Customer’s City, Customer’s State, Customer’s Zip Code, Customer’s Country, Customer’s Company, Customer’s Phone, Customer’s Fax, Customer’s Email, or Job Created By.

• Job Download: Select this option to specify which Print File Option will be used to retrieve a print file: Retrieve from Local Path, Download from URL or Retrieve from Network share.

• Others: Select this option to if a job contains a custom job ticket parameter that cannot be found in any of categories. Add a new field for this option using the Others Category.

Tool Bar

The Tool Bar only appears when the Inter Sheet Settings and the Others Category options are selected. The example below displays when the Others Category option is selected. The Inter Sheet Settings Tool Bar varies from this example. All available Tool Bar options are noted below:

• Add New: Use this option to add a new entry parameter and define its conversion rule. This is only available in the Others category.

• Delete: Use this option to delete a parameter entry. This is only available in the Others category.

• Add New Per Page Settings: Use this option to add another set of Per Page Settings. This is only available in the Inter Sheet Settings category.

• Delete Per Page Settings: Use this option to delete a Per Page settings entry. This is only available in the Inter Sheet Settings category.

• Import Mapping Table: Click to open a file dialog then select a mapping table xml file to import.

• Export Mapping Table: Use this function to save any configuration changes applied to the external mapping table’s xml file.

• Show/Hide JT Reference: Use this option to show or hide the Job Ticket Reference Panel.

Mapping Table Panel

Use this panel to define the mapping values between the job ticket parameters and the Dispatcher Metadata. Click each category option to open the Parameter Name/Metadata Key values in the main panel.

• Parameter Name: This column notes user-friendly names for the job ticket parameters.

• Metadata Key: This column notes the Dispatcher Metadata Keys for each parameter name.

• Job Ticket Paths: This column is initially blank. In it, enter the JDF Path that corresponds to each job ticket parameter.

Value Map Panel

Click on the table above to display the Metadata Key panel. Use this panel to define the conversion rules between the Metadata and Job Ticket values. Enter the values into the table. Metadata Key(s) and Job Ticket Path(s) are listed in a header. Entries may be added or deleted, as required.

• Add New Metadata Key: Click this button to add a new Metadata Key.

• Add New Job Ticket Path: Click this button to add a new Job Ticket Path.

• Add New Row: Click this button to add a new value map Row.

• Use default Job Ticket Value: If this is enabled, values in the Job Ticket remain with their corresponding Metadata Keys and are saved without any conversion being applied.

  Note: The check box is only available in the case of 1-to-1 mapping. In all other conditions, this option is grayed out and cannot be enabled.

Job Ticket Reference Panel

To open a sample job ticket file, click the Open button (). Once a job ticket is selected, all possible XML Paths are listed in the table. Drag-and-drop items in the list to the desired Job Ticket Paths column in the Mapping Table Panel.

Click the Clear button () to clean up the list.

Basic Operations of the Mapping Table

Job Ticket File

The Job Ticket Generator: JDF Node converts metadata to a JDF job ticket file.

Note: Once the Job Ticket Generator: JDF Node has been added to Dispatcher Phoenix via the add-in manager, sample job ticket files are available for viewing. Use the path below to locate them:

\Program Files\Common Files\KonicaMinolta\Phoenix\Resources\JobTicketGeneratorJDFNode

The sample job ticket noted above contains all possible job ticket parameters. The sample job ticket can be modified so it contains the parameters required to support a file. A job ticket file can also be generated using an external, third-party application. This job ticket file may then be used as a sample file.

The Job Ticket Generator: JDF Node defines job ticket parameters using Document- and Per Page Set-tings-level values. For the discussion that follows, a sample job ticket is modified with simple Document-and Per Page Settings-level values. This sample job ticket is used for the discussion that follows:

<?xml version="1.0" encoding="UTF-8"?>
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1"
  xmlns:kmbs="http://www.konicaminolta.com/KMBS_JDFExtension_1_1"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Combined">
  <ResourcePool>
    <Media Class="Consumable"
      ID="r170711_024318593_005119" MediaColorName="Yellow" Status="Available">
      <Location LocationName="AutoSelect"/>
    </Media>
    <LayoutPreparationParams Class="Parameter"
      ID="r170711_023611281_005743"
      Sides="TwoSidedFlipY" Status="Available">
      <LayoutPreparationParams RunIndex="0~4"
        kmbs:BindingEdge="Auto" kmbs:PerPageSet="Yes">
        <Media Class="Consumable" DescriptiveName="test">
          <Location LocationName="Auto"/>
        </Media>
      </LayoutPreparationParams>
    </LayoutPreparationParams>
        <RunList Class="Parameter" ID="r170707_053618136_000949" NPage="4" Status="Available">
      <LayoutElement>
        <FileSpec File="file" URL=" C:\Temp\Testfile.pdf "/>
      </LayoutElement>
    </RunList>
    <Component Class="Quantity" ComponentType="FinalProduct"
      ID="r170711_024318596_005125" Status="Unavailable"/>
  </ResourcePool>
  <ResourceLinkPool>    
    <MediaLink CombinedProcessIndex="0" Usage="Input" rRef="r170711_024318593_005119"/>
    <LayoutPreparationParamsLink CombinedProcessIndex="0" Usage="Input" rRef="r170711_023611281_005743"/>
    <RunListLink CombinedProcessIndex="0 1" ProcessUsage="Document"
  Usage="Input" rRef="r170707_053618136_000949"/>
    <ComponentLink Amount="10" CombinedProcessIndex="4" Usage="Output" rRef="r170711_024318596_005125"/>
  </ResourceLinkPool>
  <CustomerInfo BillingCode="" CustomerID="" CustomerJobName="JDF job"/>
</JDF>

Configure the Mapping Table Using the Job Ticket File

1. Using a text editor, copy the sample JDF file above.

2. The URL Path noted in the Layout Element (explained in the example above), needs to be changed so that the path is valid.

3. Save the sample locally as jdf_sample_jobticket_file.jdf.

4. Double-click on the Job Ticket Generator: JDF Node. The settings screen opens:

   

5. In the left panel, set the following values:

   • Enabled checkbox: Select the checkbox so that the process will run.
   • Node Name: Assign a name value to the node in the text field.
   • Output Data format: Select the JDF (with Local File to PDF) radio button.

   

6. In the Job Ticket Reference panel (far-right), locate the Open icon:

   

7. Click the icon and on the screen that opens, navigate to and select the file saved in Step 3 above (jdf_sample_jobticket_file.jdf).

   

8. When the file opens, its contents (or XPaths) display in the Job Ticket Reference panel, as noted in the following image:

   

   Note: When the JDF job ticket is loaded, some values are automatically mapped in the main panel. Remaining unmapped XPaths need to be manually mapped using drag-and-drop. The Inter Sheet Settings and Others’ Path Range Paths and the must always be mapped manually.

   Note: If a value is not automatically mapped or if a required option DOES NOT appear in the Job Ticket Reference panel, manually enter the value noted in the instructions in this Help file.

Mapping XPaths

Once the XPath values are available, they need to be mapped to the Parameter Name/Metadata Key values in the main panel. Do this by clicking on a value in the Job Ticket Reference panel, and then dragging the value to the corresponding Job Ticket Paths cell in the main panel.

The Category panel is available to the left and contains several options. Click a category option. The Parameter Name/Metadata Key values it contains display in the main panel.

Mapping Basic Parameter Name/Metadata Keys Values

1. In the Category panel, click the Basic Settings option. The Parameter Name, Metadata Keys, and Job Ticket Paths columns display in the main panel:

   

2. The following values from the Job Ticket Reference panel are automatically moved to their Job Tickets Paths cells:

   • /JDF/ResourceLinkPool/ComponentLink/@Amount -> Copies

   • /JDF/ResourcePool/Media/Location/@LocationName -> Paper Source

   • /JDF/ResourcePool/Media/@MediaColorName -> Paper Color

3. If they are not automatically mapped:

   • Drag-and-drop /JDF/ResourceLinkPool/ComponentLink/@Amount to the Job Ticket Paths cell of the Copies row.

   • Drag-and-drop /JDF/ResourcePool/Media/Location/@LocationName to the Job Ticket Paths cell of the Paper Source row.

   • Drag-and-drop /JDF/ResourcePool/Media/@MediaColorName to the Job Ticket Paths cell of the Paper Color row.

4. The values that were either automatically moved or manually dragged-and-dropped are removed from the Job Ticket Reference panel.

5. In the Category panel, click the Layout Settings option. The Parameter Name, Metadata Keys, and Job Ticket Paths columns display in the main panel:

   

6. The following value from the Job Ticket Reference panel is automatically moved to its Job Tickets Paths cell:

   • /JDF/ResourcePool/LayoutPreparationParams/@Sides -> Printing Type

7. If they are not automatically mapped:

   • Drag-and-drop /JDF/ResourcePool/LayoutPreparationParams/@Sides to the Job Ticket Paths cell of the Printing Type row.

8. All values that were dragged-and-dropped from the Job Ticket Reference panel are removed from the panel.

9. Repeat the same procedure for other Category options, as required.

Mapping Inter Sheet Settings Parameter Name/Metadata Keys Values

The Inter Sheet Settings Category is used to configure Per Page Settings. Enable and then map the XPath values to activate these settings. These Inter Sheet Settings generate page-level metadata.

1. In the Category panel, click the Inter Sheet Settings option. The Page Range Path 1 field and the Parameter Name, Metadata Keys, and Job Ticket Paths columns display in the main panel:

   

2. From the Job Ticket Reference panel, drag-and-drop /JDF/ResourcePool/LayoutPreparationParams/LayoutPreparationParams/@RunIndex to the Page Range Path 1 text box.

   Note: Page Range Path value should start with “/JDF/” pattern.

3. From the Job Ticket Reference panel, drag-and-drop /JDF/ResourcePool/LayoutPreparationParams/LayoutPreparationParams/Media/@DescriptiveName to the Job Ticket Paths field for PPS Paper Name.

4. Once these actions are completed, the screen will appear as shown in the following image:

   

5. All values that were dragged-and-dropped from the Job Ticket Reference panel are removed from the panel.

6. Repeat the same procedure for other Category options, as required.

Mapping Job Download Parameter Name/Metadata Keys Values

Use the Job Download Category to enable the input source from which a job’s PDF file can be received. Three values are supported: Retrieve from Local Path, Download from URL and Retrieve from Network share.

Enable and then map the XPath values to activate these settings.

Sample JDF Job Ticket Files

The following examples show how the code will display the PDF file for each of the job download options:

Retrieve from Local Path

 • “File”: “file”

 • “URL”: “C:\Temp\Testfile.pdf”

Note: The file type keyword “file” and the file type keyword written in the input job ticket file must match.

Download from URL

 • “File”: “http”

 • “URL”: “http://10.146.171.98/testapp8/Testfile.pdf”

Note: The file type keyword “http” and the file type keyword written in the input job ticket file must match.

Retrieve from Network share

 • “File”: “share”

 • “Src”: “\\11.12.13.14\Temp\Testfile.pdf

Note: The file type keyword “share” and the file type keyword written in the input job ticket file must match.

1. In the Category panel, click the Job Download option. The Documentation Source and Job Ticket Path: File Type fields and the Retrieve Print File Option checkboxes display in the main panel:

   

2. In the Retrieve from File Option column, select the checkboxes of 3 options: Retrieve from Local Path, Download from URL and Retrieve from Network share.

3. From the Job Ticket Reference panel, drag-and-drop /JDF/ResourcePool/RunList/LayoutElement/FileSpec/@URL to the Documentation Source field.

4. From the Job Ticket Reference panel, drag-and-drop /JDF/ResourcePool/RunList/LayoutElement/FileSpec/@File to the Job Ticket Path: File Type field.

5. Once these actions are completed, the screen will appear as shown in the following image:

   

6. All values that were dragged-and-dropped from the Job Ticket Reference panel are removed from the panel.

7. Repeat the same procedure for other Category options, as required.

Value Map Configuration

Use this feature to configure one or more values for job ticket paths. In the example that follows, Printing Type’s XPath value is mapped. Once that is completed, the setting is then edited to specify the value map for /JDF/ResourcePool/LayoutPreparationParams/@Sides.

1. In the Category panel, click the Layout Settings option.

2. Click on the Printing Type row to open the Value Map panel:

   

3. By default, a single value map row displays. Since there are two values that need to be mapped, click Add New Row to add a second value map row:

   

4. In the first row, select Double-Sided from the Metadata Key drop-down menu and enter TwoSidedFlipY for the Job Ticket Path.

5. If the metadata’s value is Double-Sided, the job ticket will write the value as TwoSidedFlipY.

6. In the second row, select One-Sided from the Metadata Key drop-down menu and enter OneSidedFront for the Job ticket path.

7. If the metadata’s value is One-Sided, the job ticket will write the value as @Sides as OneSidedFront.

8. When finished, click Save. To undo the changes, click Cancel.

Sample of a Job Ticket Generator: JDF Node Workflow

In the workflow above a job ticket file (e.g., jdf_sample_jobticket_file.jdf) is moved to the Input Folder. This is sent to the Job Ticket Parser: JDF Node where the JDF job ticket is converted to job ticket metadata using the mapped values that have been created using the Job Ticket Parser: JDF Node’s settings. When this is completed, the data is transferred to the Job Ticket Editor Node where the Copies value is changed to 100. From there, the job moves to the Job Ticket Generator: JDF Node where a JDF job ticket file is generated from the metadata. Depending upon the Output Format specified, the converted file is then sent to an Output folder.

Input Folder Node: Configure the Input Folder to collect files and forward them to the Job Ticket Parser: JDF Node.

Job Ticket Parser: JDF Node: The Job Ticket Parser: JDF Node is used to parse the information in a JDF file then write the parsed information as metadata. The JDF file should contain a job ticket field and a job ticket value. The node reads the job ticket field and its corresponding job ticket values then updates the metadata. A mapping table is used to map the job ticket data to the metadata values.

The input will be a JDF, Zip (JDF+PDF), or MIME (MJM) file. The JDF and ZIP (JDF+PDF) contain the job ticket information in form of job ticket field and job ticket value. The MJM file contains the JMF, JDF content (job ticket), and PDF content and it will process the extracted JDF (job ticket) and PDF file.

For complete details, see the Job Ticket Parser: JDF Node topic in this Help file.

Job Ticket Editor Node: Use this node to modify the Copy count of the job:

1. Double-click the Job Ticket Editor node to view the settings:

   

2. From the left panel, select Basic Settings.

3. Click on Copies and drag it to the right-side panel:

   

4. Change the Metadata Values to 100.

5. From the If metadata already exists drop-down, select Replace.

   

6. Click Save to apply the change.

Job Ticket Generator: JDF Node: The purpose and instructions for setting up this node are provided in the discussion that precedes this section.

Output Folder Node: Once all workflow processes have been successfully applied, a job is routed to the folder path configured in the Output Folder Node.

The output metadata that follows is based upon the settings noted in the previous sections of this document:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" xmlns:kmbs="http://www.konicaminolta.com/KMBS_JDFExtension_1_1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Combined">
    <ResourcePool>
        <Media Class="Consumable" ID="r170711_024318593_005119" MediaColorName="Yellow" Status="Available">
            <Location LocationName="AutoSelect"/>
        </Media>
        <LayoutPreparationParams Class="Parameter" ID="r170711_023611281_005743" PartIDKeys="RunIndex" Sides="TwoSidedFlipY" Status="Available">
            <LayoutPreparationParams RunIndex="0~4" kmbs:PerPageSet="Yes">
                <Media DescriptiveName="test"/>
            </LayoutPreparationParams>
        </LayoutPreparationParams>
        <RunList Class="Parameter" ID="r170707_053618136_000949" NPage="4" Status="Available">
            <LayoutElement>
                <FileSpec File="file" URL="C:\ProgramData\Konica Minolta\conopsd\var\blox\node_4\tmp.d\Testfile.pdf"/>
            </LayoutElement>
        </RunList>
        <Component Class="Quantity" ComponentType="FinalProduct" ID="r170711_024318596_005125" Status="Unavailable"/>
    </ResourcePool>
    <ResourceLinkPool>
        <MediaLink CombinedProcessIndex="0" Usage="Input" rRef="r170711_024318593_005119"/>
        <LayoutPreparationParamsLink CombinedProcessIndex="0" Usage="Input" rRef="r170711_023611281_005743"/>
        <RunListLink CombinedProcessIndex="0 1" ProcessUsage="Document" Usage="Input" rRef="r170707_053618136_000949"/>
        <ComponentLink Amount="100" CombinedProcessIndex="4" Usage="Output" rRef="r170711_024318596_005125"/>
    </ResourceLinkPool>
    <CustomerInfo BillingCode="" CustomerID="" CustomerJobName="JDF job"/>
</JDF>