Scan job type specification
Introduction
In PRISMAsync it is possible to make a scan-to-file or scan-to-email with the scanner of the
connected printer. In the user interface of the scanner, a suitable scan profile can be selected
from a list of possible scan profiles. The scan profiles are gathered together in a small database
called the scan job type file.
Before making a scan, a scan job type must be choosen from the user interface. Scan job types
are shortcuts to scan settings. The scan job types are shown on the user interface as a pick list. To
configure PRISMAsync with a new set of scan job types, you must download a comma separated
value (CSV) file via the Settings Editor.
Definition of scan job type records
A scan job type record:
• Is identified by a unique filename, which combines the scan output settings. The unique name
explains the kind of scan job or the post processing application.
• Is used to load the correct scan output settings for a specific type of scan job.
The unique filename and Tiff-tags can be used by an application to automatically execute actions
on a received Tiff-file. This supports productivity with bulk scans.
You can define part of the unique filename by using scan job types. You cannot manually change
the filename on the PRISMAsync.
The scan job type record consists of a mandatory headerline and at least one Scan Job Type.
There is a maximum of 99 Scan Job Types. The headerline and all subsequent Scan Job Types
are separated by the record separator <CR><LF>.
The syntax of the headerline is in plain text and shows which fields can be identified in the Scan
Job Type lines. The fields are separated by a selectable field separator <fseparator>. <fseparator>
can be a comma "," or a semi-colon ";".
<fseparator> ::= "," | ";". <fseparator> must use the same seperator for the entire file.
The following fields are available:
<headerline> ::= "dispname"
<fseparator> "format"
<fseparator> "ilc"
<fseparator> "prefix"
<fseparator> "minnr"
<fseparator> "maxnr"
<fseparator> "name_nr_title"
<fseparator> "cfname"
{ <fseparator> "subfolder" } optional
{ <fseparator> "postfix" } optional
{ <fseparator> "OrigOrientation"} optional
{ <fseparator> "OrigDuplex" } optional
{ <fseparator> "OrigKind" } optional
Scan job type specification
308
Chapter 13 - Scan-to-file and scan-to-email
imagePRESS C7010VPS series v2.2
Summary of Contents for imagePRESS C7010VPS series
Page 8: ...Contents 8 imagePRESS C7010VPS series v2 2...
Page 9: ...Chapter 1 Introduction...
Page 14: ...Supported media 14 Chapter 1 Introduction imagePRESS C7010VPS series v2 2...
Page 15: ...Chapter 2 PRISMAsync...
Page 29: ...Chapter 3 The LPD connection...
Page 45: ...Chapter 4 The socket connection...
Page 51: ...Chapter 5 Adobe PostScript 3...
Page 64: ...Bind 64 Chapter 5 Adobe PostScript 3 imagePRESS C7010VPS series v2 2...
Page 86: ...Staple 86 Chapter 5 Adobe PostScript 3 imagePRESS C7010VPS series v2 2...
Page 89: ...Trim Chapter 5 Adobe PostScript 3 89 imagePRESS C7010VPS series v2 2...
Page 99: ...Chapter 6 PDF...
Page 117: ...Chapter 7 Colour management...
Page 133: ...Chapter 8 Accounting...
Page 150: ...Implementation aspects 150 Chapter 8 Accounting imagePRESS C7010VPS series v2 2...
Page 151: ...Chapter 9 SNMP...
Page 159: ...Example in pseudo code Chapter 9 SNMP 159 imagePRESS C7010VPS series v2 2...
Page 222: ...ppmPortGroup 222 Chapter 9 SNMP imagePRESS C7010VPS series v2 2...
Page 223: ...Chapter 10 JDF interface specification...
Page 291: ...Basic JDF ticket Chapter 10 JDF interface specification 291 imagePRESS C7010VPS series v2 2...
Page 297: ...Chapter 11 SMB printing...
Page 303: ...Chapter 12 Hot folder printing...
Page 306: ...Hot folder 306 Chapter 12 Hot folder printing imagePRESS C7010VPS series v2 2...
Page 307: ...Chapter 13 Scan to file and scan to email...
Page 313: ...Chapter 14 SRA IPDS...
Page 361: ......