To understand this document a number of concepts must be understood:
Hot Folder: Directory on a file-system that is monitored by a dedicated application. The application will respond to changes in that directory.
NT Service: a programme that is running continuously in the background, even if no user is logged in.
GUID & UUID: Global Unique Identifier & Universal Unique Identifier. Large number that is guarantied unique.
Order processing workspace: a part (workspace) of the PRISMAdirect web application that allows order managers and operators to manage orders and their jobs and perform print-related tasks.
Product & order editor: a part (workspace) of the PRISMAdirect web application allowing the management of the Current Definition (see below).
JobNumber: shown in the Order processing workspace > Order and Job views as the number of the job. Note that this number is not unique.
OrderNumber: shown in the Order processing workspace > Order view as the number of the job. Note that this number is not unique.
JobID: identifier of a Job. A GUID is used to guarantee that this number is always unique.
OrderID: identifier of an Order. A GUID is used to guarantee that this number is always unique.
DefinitionID: identifier of a Definition. A GUID is used to guarantee that this number is always unique.
Job: is a combination of one or more PDF files and a set of Job attributes. The set of attributes is collectively called the job ticket. The job ticket must be interpreted as the print job description containing print/production information related to that Job (e.g. copies, binding) as specified by the creator (end-user).
Order: is a combination of one or more Jobs and a set of Order attributes. The set of attributes is collectively called the order ticket. The order ticket must be interpreted as order description containing specific details (e.g. owner, delivery information) as declared by the creator (end-user).
Product: this is the blueprint of a Job, a collection of job type, Item arrangement in Views, default values and value constraints. It is defined in Product & order editor.
Item: an attribute belonging to a Job or an Order, e.g. a field in a job ticket. An item has some related concepts in the context of the PRISMAdirect XML Schema. These are explained below.
ItemDefinition: defines the data type, default value and possible values of an item. In other words, an ItemDefinition is a type specifier for an item. The set of ItemDefinition elements is part of the Definition element.
ItemValue: the instance of an item in a job. It represents the actual value of an item in the context of that job.
ItemViewLeaf & ItemViewGroup: represent the position of an item in a graphical tree-like presentation of a job ticket. An ItemViewGroup represents an item in the "tree" which only purpose is to group several other items. Whereas an ItemViewLeaf represents a leaf of the "tree". ItemViewLeaf and ItemViewGroup elements are part of a View-element.
View: defines the presentation of the job or order. Part of a Definition element. It contains the set of ItemViewLeaf and ItemViewGroup elements used.
Definition: Structured description of the job ticket / order ticket used in the system and views on the ticket. It contains the "declaration" of all ItemDefinition elements that belong to a Job or Order and View declarations. Attachment elements describe files that belong to a Job (source documents).
Current Definition: identifies the Definition that is "current", i.e. the Definition that is used to create Orders and their contained Jobs and to present them in the Order processing workspace. The Current Definition may be set to a different Definition over time. This may lead to a mismatch between new Jobs and Jobs that were created using an earlier
Media: a media is a physical substrate that can be processed by a printing system. It is something you can hold or lay down somewhere. This means a media is a sheet or a roll of a certain material and shape and should not be confused with just the size of a sheet, a side of a sheet or the size of an image to be printed.
Media attributes: Main attributes that define a media. These are the attributes that together uniquely identify a media inside the system and allow a user to select that media instead of another one. Examples: media size, media type, etc
Media catalogue: A media catalogue is an ordered administration of media descriptions to be used in an Océ product. The order of the media in the catalogue may be used by these Océ products as a default ranking mechanism when multiple media from the catalog match a media request.
This document assumes that the reader is familiar with XML.