Read and report barcode values

There are workflows where the contents of barcodes are required, without making changes to the underlying document structure.    Examples include:

 

• Many barcodes on each page,
• pharmacy refill orders with multiple prescriptions per page pasted on
• class registrations where the course has one barcode, and the student IDs labels are barcodes and pasted
• test scoring sheets - where one barcode identifies the test and the other identifies the student
• Multiple kinds of barcodes on various pages of the document
• A variety of waybills are barcoded by different shippers
• Farm produce boxes - packing receipts produced by different farms, with separate barcodes for the product, the box, the packer and each lot number
• Simple barcoded documents
• test results from labs
• invoices
• shipment receipts
• product authentication barcodes

 

In all of these circumstances, the requirement is to know what is in the barcodes, on which image page.   Barcode Director will only organize this data and present it.   Another application will use the data to run a workflow process or to archive the images.   

 

Barcode director offers several different ways to present the data, and they are all called Reports:

• Per Barcode reports - a separate file is created for each barcode encountered.   The file name identifies the file, page and sequence number of this barcode.   Inside the file is the data from the barcode.   We call this the Barcode Value File
• Tabular reports - Text files containing a row of data for each found barcode.  The user selected columns are CSV or TAB separated.
• XML Files - An XML structure, whose elements are user selectable, for each found barcode.

Every conceivable barcode and document attribute is available in these reports, making them very informative and useful for workflow integration

 

---