LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
October 2004
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2004.10.01 12:00 "Re: private tags:", by Rob Tillaart
Joris wrote:
>
> > 4 tags for your collection:
>
> Rob,
>
> Great! This is absolutely fabulous.
>
> However, sofar, I've not included eg the Pixar tags on which I have little more
> then number and name, because of a lacking 'long' descriptions.
OK,
You asked for a long description :)
First I need to tell the story of how the Oce scan concept works. The
meaning of the tags will become clear.
The Oce scanning Concept
-------------------------
Oce MFP's e.g. Oce 3165 have a scan function (BW 60ppm) but they do not have a
TWAIN or ISIS interface. Instead the user has to upload a scan-ticket to the
device to be able to scan. They also must be removed explicitely, so in
essence it is a one time action.
At the device the user selects his/her scanticket, puts the originals in the
Document Feeder and presses the green button to start. Scanning will start and
the generated TIFF file will be FTP'ed to a predefined server. On this server
the file will be redirected to the right processing application('s) or
workflow('s) e.g. scan2email, scan2archive, scan2desktop, scan2OCR,
scan2you_name_it :)
What happens under the hood:
-----------------------------
1) To let the user select the right scan-ticket, the scanticket has an
identification string which are displayed on the console of the Oce device.
This same string will be embedded in the TIFF file as the ScanJob Description
tag 50215 (in every page).
2) In the Scanticket an identification of the Application to process the TIFF
file is embedded as the Application Selector Tag 50216 (in every page). Note
it is not the name of the executable but an identifier which is mapped upon
the application or workflow. By simply change the mapping one can redirect a
workflow without changing anything in the tickets or at the devices (user
won't notice).
3) A Scanticket can include a question to be presented to the user before he
makes the scan. The answer to this question is embedded as the Identification
Number, tag 50217. This number might act as a parameter to the processing
application or workflow e.g. one can have a generic scanticket and asks for
the employee number, and the application maps this (by means of LDAP) to an
email-adres. Or one fills in the dossier number and the scanned document is
stored in the archive in the right dossier.
4) A Scanticket contains the processing parameters so the user does not have
to worry about them. An internal module, marketed as ImageLogic, provides
optimal quality for every scan/workflow. As there are different purposes,
archiving, viewing or printing these parameters can differ. This is coded in
the ImageLogic Characteristics as tag 50218. [Long, values are for Oce
internal use only]
So far the concept and the tags; if there are questions shoot!, if you want to
buy the device see www.oce.com for the nearest dealer :)
regards,
rob