Structure of the mapping file

The structure of the mapping file is quite simple. Each file contains a list of mapping nodes. A mapping node exists for each ticket item in the default PRISMAdirect ticket. PRISMAdirect contains different types of ticket items: "Number", "Yes/no", "Text", "Date", "Choice" and "Lookup" items. Therefore, several types of mapping nodes are required to map the different types of ticket items successfully:

Header of the mapping file

<?xml version="1.0" encoding="utf-8"?>

<jc:Mappings SchemaVersion="1.0" AttachmentPath="/jdf:JDF/jdf:ResourcePool/jdf:LayoutElement/jdf:FileSpec/@URL" xmlns:jc="oce-com-pa-jc">

...

</jc:Mappings>

The attributes of the header are:

The three mandatory attributes

All mapping nodes contain at least three mandatory attributes. However, all nodes can contain one or more conditions. In this example, the following node only contains the three mandatory attributes.

<jc:NumberMapping Name="Copies" Optional="true">

<jc:JdfField XPath="/jdf:JDF/jdf:ResourceLinkPool/…/@Amount"/>

</jc:NumberMapping>

The result of this mapping node is:

• The ticket item Copies of PRISMAdirect receives the value of the JDF ticket item Amount.

The mandatory attributes are explained here for all mapping nodes:

NumberMapping

The NumberMapping node is a simple node. It contains only the three mandatory attributes.

<jc:NumberMapping Name="Copies" Optional="true">

<jc:JdfField XPath="/jdf:JDF/jdf:ResourceLinkPool/…/@Amount"/>

</jc:NumberMapping>

Limitation

• The retrieved value must be valid for PRISMAdirect. Else, the value is not applied to the PRISMAdirect ticket item. For example:

  The ticket item "Copies" is a number item and can therefore only receive a numeric value. Text such as “John Doe” is not allowed.

  The item can have constraints on the minimum and maximum values as defined in the "Product & order editor" workspace. If the value in the JDF ticket item is outside these boundaries, it cannot be set in the PRISMAdirect ticket item.

DateMapping

The DateMapping node is a simple node. It contains only the three mandatory attributes.

<jc:DateMapping Name="Date" Optional="true">

<jc:JdfField XPath="/jdf:JDF/jdf:ResourcePool/…/@LastEnd"/>

</jc:DateMapping>

Limitation

• PRISMAdirect tries to convert the string obtained from the JDF ticket item into a valid date. If successful, the value is assigned to a PRISMAdirect ticket item of type "Date".

TextMapping

The TextMapping node can contain a number of optional attributes in addition to the three mandatory attributes.

<jc:TextMapping Prefix="Address:" Name="Location" Optional="true" Separator=",">

<jc:JdfField XPath="/jdf:JDF/jdf:ResourcePool/…/jdf:Address/@Street"/>

<jc:JdfField XPath="/jdf:JDF/jdf:ResourcePool/…/jdf:Address/@City"/>

<jc:JdfField XPath="/jdf:JDF/jdf:ResourcePool/…/jdf:Address/@PostalCode"/>

</jc:TextMapping>

Limitation

• The retrieved value must be valid for PRISMAdirect. Else, the value is not applied to the PRISMAdirect ticket item. For example:

  The item can have constraints on the maximum number of characters as defined in the "Product & order editor" workspace. If the value in the JDF ticket item is longer than the maximum number of characters, it cannot be set in the PRISMAdirect ticket item.

EnumMapping

The EnumMapping node always contains specific attributes in addition to the three mandatory attributes.

<jc:EnumMapping Name="DocumentMediaWeight" Optional="true">

<jc:JdfField XPath="/jdf:JDF/jdf:ResourcePool/…/@Weight"/>

<jc:EnumValueMapping JdfValue="65"AccessEnumValue="65032gram047m2"/>

<jc:EnumValueMapping JdfValue="80"AccessEnumValue="80032gram047m2"/>

<jc:EnumValueMapping JdfValue="90"AccessEnumValue="90032gram047m2"/>

<jc:EnumValueMapping JdfValue="100"AccessEnumValue="100032gram047m2"/>

<jc:EnumValueMapping JdfValue="120"AccessEnumValue="120032gram047m2"/>

<jc:EnumValueMapping JdfValue="160"AccessEnumValue="160032gram047m2"/>

<jc:EnumValueMapping JdfValue="170"AccessEnumValue="170032gram047m2"/>

</jc:EnumMapping>

The EnumMapping node contains a list of EnumValueMapping nodes for each of the possible values for the option in the choice /lookup ticket item of PRISMAdirect:

PRISMAdirect retrieves the JDF ticket item using the specified XPath expression. PRISMAdirect parses the EnumValueMapping nodes to find the JdfValue attribute that is equal to the value taken from the JDF ticket. When the node is found, the value of the AccessEnumValue attribute is set in the PRISMAdirect ticket item specified by the Name attribute.

For example, the value retrieved from the JDF ticket is "100" for the JDF ticket item Weight. PRISMAdirect sets the value of the ticket item DocumentMediaWeight to "100032gram047m2".

Limitation

• The value retrieved from the JDF ticket must be available in one of the EnumValueMapping nodes. If it is not available, no value can be set in the PRISMAdirect ticket item.

ConditionalEnumMapping

The ConditionalEnumMapping node always contains specific attributes in addition to the three mandatory attributes.

<jc:ConditionalEnumMapping Name="BindingMethod" Optional="true">

<jc:ConditionalEnumValue AccessEnumValue="SaddleStitch">

<jc:StringCondition JdfField="/jdf:JDF/jdf:ResourcePool/jdf:StitchingParams/@StitchType"ExpectedValue="Saddle"/>

<jc:StringCondition JdfField="/jdf:JDF/jdf:ResourcePool/jdf:StitchingParams/@NumberOfStitches" ExpectedValue="2"/>

</jc:ConditionalEnumValue>

<jc:ConditionalEnumValue AccessEnumValue="Staples_1">

<jc:StringCondition JdfField="/jdf:JDF/jdf:ResourcePool/jdf:StitchingParams/@NumberOfStitches" ExpectedValue="1"/>

</jc:ConditionalEnumValue>

<jc:ConditionalEnumValue AccessEnumValue="Staples_2">

<jc:StringCondition JdfField="/jdf:JDF/jdf:ResourcePool/jdf:StitchingParams/@NumberOfStitches" ExpectedValue="2"/>

</jc:ConditionalEnumValue>

....

</jc:ConditionalEnumMapping

The ConditionalEnumMapping node contains one ConditionalEnumValue node for each option in the choice/lookup ticket item of PRISMAdirect specified in by the attribute Name.

PRISMAdirect parses the ConditionalEnumValue nodes. For each node it evaluates the conditions. If all conditions in one ConditionalEnumValue node are met:

• The parsing stops

• PRISMAdirect sets the value of the PRISMAdirect ticket item with the value of the corresponding AccessEnumValue attribute.

BooleanMapping

The BooleanMapping node always contains specific attributes in addition to the three mandatory attributes.

<jc:BooleanMapping Name="Collate" Optional="true" EvaluateTo="false">

<jc:StringCondition JdfField="/jdf:JDF/…/@Collate" ExpectedValue="None"/>

<jc:StringCondition JdfField="/jdf:JDF/@Types" ContainedValue="DigitalPrinting"/>

</jc:BooleanMapping>

PRISMAdirect evaluates the conditions. If all conditions are met, the PRISMAdirect ticket item specified by the Name attribute receives the value of the EvaluateTo attribute.

For example, for the above mapping node, if both string conditions are met, the Collate ticket item receives the value "false". Else, the ticket item receives the value "".

TimeSpanMapping

The TimeSpanMapping node always contains specific attributes in addition to the three mandatory attributes.

<jc:TimeSpanMapping Name="FinishingTime" Optional="true">

<jc:TimeSpan Start="/jdf:JDF/jdf:AuditPool/…/@Start"

End="/jdf:JDF/jdf:AuditPool/…/@End"/>

</jc:TimeSpanMapping>

PRISMAdirect computes the difference in time between the two values. The result is a time span which is set as the value of the PRISMAdirect ticket item specified by the Name attribute.

MediaMapping

PRISMAdirect only supports jobs using one type of media for the document and one type of media for the cover. The document media and the cover media can be different. Media is defined by four properties:

• Media color

• Media type

• Media weight

• Media size

The mapping file contains eight nodes to retrieve the media properties:

• Four nodes to retrieve the properties of the document media

• Four nodes to retrieve the properties of the cover media

Two types of mapping nodes are used to exclusively map media attributes:

• MediaEnumMapping

  Used exclusively for media ticket items when one option offers a list of values. For example, the colour of a media.

• MediaConditionalEnumMapping

  Used exclusively for media ticket items when a condition determines which options and values become available for the item. For example, when the media is A4 and booklet, then....

Example of the MediaEnumMapping node to retrieve the media colour:

<jc:MediaEnumMapping Name="CoverMediaColor" Optional="true">

<jc:JdfField XPath="/jdf:JDF/…/jdf:Media[@ID='${MediaID}']/@MediaColorName"/>

<jc:EnumValueMapping JdfValue="White" AccessEnumValue="White"/>

<jc:EnumValueMapping JdfValue="Blue" AccessEnumValue="Blue"/>

<jc:EnumValueMapping JdfValue="Black" AccessEnumValue="Black"/>

</jc:MediaEnumMapping>

Example of the MediaConditionalEnumMapping node to retrieve the media size:

<jc:MediaConditionalEnumMapping Name="DocumentMediaSize" Optional="true">

<jc:ConditionalEnumValue AccessEnumValue="A0">

<jc:NumericCondition ExpectedValue="2383.9344" JdfField="/jdf:JDF/…/jdf:Media[@ID='${MediaID}']/@Dimension[0]"/>

<jc:NumericCondition ExpectedValue="3370.392" JdfField="/jdf:JDF/…/jdf:Media[@ID='${MediaID}']/@Dimension[1]"/>

</jc:ConditionalEnumValue>

<jc:ConditionalEnumValue AccessEnumValue="A0">

<jc:NumericCondition ExpectedValue="2383.9344" JdfField="/jdf:JDF/…/jdf:Media[@ID='${MediaID}']/@Dimension[1]"/>

<jc:NumericCondition ExpectedValue="3370.392" JdfField="/jdf:JDF/…/jdf:Media[@ID='${MediaID}']/@Dimension[0]"/>

</jc:ConditionalEnumValue>

</jc:MediaConditionalEnumMapping>

The XPath in the JdfField retrieves the ID of the media using [@ID='${MediaID}'].

NOTE

The mapping file can contain the Type attribute and the MediaPartitioner for the MediaEnumMapping node and the MediaConditionalEnumMapping node. However, these attributes are obsolete and are not used by PRISMAdirect.

Conditions

All nodes can contain one or more conditions. PRISMAdirect accepts the following conditions:

• StringCondition

  For example:

  <jc:StringCondition JdfField="/jdf:JDF/jdf:ResourcePool/jdf:StitchingParams/@StitchType" ExpectedValue="Saddle"/>

  or

  <jc:StringCondition JdfField="/jdf:JDF/jdf:ResourcePool/jdf:StitchingParams/@StitchType" ContainedValue="Saddle"/>

• NumericCondition

  For example:

  <jc:NumericCondition JdfField="/jdf:JDF/jdf:ResourcePool/jdf:StitchingParams/@NumberOfStitches" ExpectedValue="2"/>

  or

  <jc:NumericCondition JdfField="/jdf:JDF/jdf:ResourcePool/jdf:StitchingParams/@NumberOfStitches" ContainedValue="2"/>

• NumericComparisonCondition

  For example:

  <jc:NumericComparisonCondition Value_1="/jdf:JDF/jdf:ResourcePool/jdf:Media/@Dimension[0]" Value_2="/jdf:JDF/jdf:ResourcePool/jdf:Media/@Dimension[1]" Comparison="LessThan"/>

The attributes for the StringCondition and NumericCondition are:

Attribute	Description
JdfField	The XPath expression points to an item in the JDF ticket. The value of the item is used in the condition. NOTE Both the StringCondition and the NumericCondition can be used without an ExpectedValue or a ContainedValue attribute. In this case, the condition is met when the JdfField exists in the JDF ticket.
ExpectedValue	The value of JdfField is compared to the value of ExpectedValue. StringCondition The condition is met when both values are equal. For example: <jc:StringCondition JdfField="/jdf:JDF/@Types" ExpectedValue="Layout"/>. The condition is met when JdfField = ExpectedValue. In this example, only the value "Layout" is accepted. NumericCondition The condition is met if the compared value is +1 or -1 from the expected value. For example: "2 = 3", "2.5 = 3" and "2.5 = 2.34" are all accepted.
ContainedValue	The value of JdfField is compared to the value of ContainedValue. The condition is met when the value of ContainedValue is part of the value of JdfField. For example: <jc:StringCondition JdfField="/jdf:JDF/@Types" ContainedValue="Layout"/>. The condition is met when JdfField contains at least the string value as defined by ContainedValue. In this example, all string values that contain "Layout" are accepted, e.g. "Layout", "LayoutPreparation", etc.

The attributes for the NumericComparisonCondition are: