Specifications

DescriptionProperty
A script expression that evaluates to the file or folder path referring to
the asset to be copied (*)
Asset path
Determines whether the original copy of the asset is deleted after it has
been copied into the flow; this can be an explicit value or a script
expression (*)
Delete asset
(*) Usually script expressions are evaluated in the context of an incoming job before the tool acts
on the job. As an exception to this rule, here the script expressions are evaluated AFTER the
incoming metadata has been picked up (but before the asset has been located) so that the script
expression can access the metadata to calculate its return value.
Metadata embedded in asset
The asset (which is always a single file) is placed in one of the pickup tool’s input folders and
the metadata source is embedded in the asset file according to some format (which depends on
the pickup tool).
When the pickup tool detects an incoming file, it expects is to be an asset and it performs the
following steps:
• Extract the metadata source from the asset and store it into a standalone file; if the asset
does not contain embedded metadata of the appropriate type, the next two steps are skipped.
• Create a new metadata dataset with this standalone file as its backing file.
• Associate this dataset with the asset’s internal job ticket under the dataset name specified
through a flow element property for the pickup tool (replacing any existing association with
the same name).
• Move the asset file to the output folder.
DescriptionProperty
If set to "Yes", for supported file formats the values of binary EXIF and
IPTC tags are merged with the embedded XMP packet before it is picked
up (the packet embedded in the asset remains unchanged)
Synchronize EXIF/IPTC
fields
If set to "No", the embedded XMP packet is picked up without change -
if present
Metadata is asset
The pickup tool with a fourth pickup mode: "Metadata is asset" is used to implement for JDF,
XML and XMP pickup.
When a job (example: JDF) file is sent to a pickup tool using this feature, the resulting file is the
JDF file with its own content as JDF metadataset. So tools have only three properties: Name,
Dataset name and Pickupmode. There is no need for additional properties when this pickup
mode is selected.
Email message schema
In PowerSwitch the mail receive tool automatically picks up the contents of incoming email
messages as metadata. Specifically, for each incoming message the mail receive tool creates a
metadata dataset that contains the relevant components of the message, such as the sender,
319
Enfocus Switch 10