Specifications

DescriptionProperty
The label shown in front of the fieldLabel
A hint displayed when the cursor hovers over the fieldDescription
The field’s data type: Boolean or stringData type
A script expression that evaluates to the value of the metadata field;
it is evaluated in the context of the job being viewed by the user so
that it can use metadata associated with the job
Calculated value
Client fields schema
The Submit point and Checkpoint tools pickup metadata fields entered by the SwitchClient user
when submitting or moving along a job.
Specifically, when a user submits a job and the list of field definitions in the Submit point's
“Metadata fields” property is nonempty, the Submit point:
• Creates a metadata dataset containing the contents of the metadata fields entered by the
user.
• Associates this dataset with the job ticket for the submitted job under the dataset name
specified in the “Dataset name” property.
Similarly, when a user moves along a job residing in a Checkpoint and the list of editable field
definitions in the Checkpoint's “Metadata fields” property is nonempty, the Checkpoint creates
a metadata dataset and associates it with the job’s job ticket under the specified dataset name.
Note that a Checkpoint always creates a completely new dataset, i.e. it does not update or modify
an existing dataset (even if the job was previously moved through the same or another
Checkpoint). If the job already has dataset association with the same name, the reference to the
old dataset is removed and replaced by the new one.
Data model and schema
The client fields dataset uses the XML data model with a simple schema without namespaces.
The XML document element name is “field-list”. It contains a “field” element for each item in
the list of editable metadata field definitions associated with the Submit point or Checkpoint
under consideration. The “field” elements occur in the same order as in the list of field definitions,
and a “field” element is present even if the corresponding field’s value is empty.
Each “field” element in turn contains zero or one occurrence of each element listed in the table
below. Within the contents of those child elements leading and trailing white space is removed.
Element is presentDescription of element contentsElement name
AlwaysThe field name; in the current implementation this
is equal to the human-readable field label
tag
AlwaysThe field’s data type; that is, "boolean", "string"
or "choice"
type
326
Enfocus Switch 10