Difference between revisions of "Barcode Processing"

From LogicalDOC Community Wiki
Jump to navigationJump to search
Line 8: Line 8:
 
==Features we want to implement ==
 
==Features we want to implement ==
 
We want to extract barcodes from documents asynchronously through the scheduled task '''BarCode Reader''', which will check for barcode inside image or pdf file. This files must comply with the configuration parameters set in a specific page in the Administration section. In this page the user can specify:
 
We want to extract barcodes from documents asynchronously through the scheduled task '''BarCode Reader''', which will check for barcode inside image or pdf file. This files must comply with the configuration parameters set in a specific page in the Administration section. In this page the user can specify:
    * inclusions and exclusions of documents that contain specific characters into their titles
+
* inclusions and exclusions of documents that contain specific characters into their titles
    * the templates to which are associated the documents that must be parsed
+
* the templates to which are associated the documents that must be parsed
  
 
The barcodes will be associated to the attributes of templates according to the specifications set by the user in another configuration page. On this page, for each template, the user indicates, for each barcode found into the document, which property or attribute of the document will be filled with that barcode.  
 
The barcodes will be associated to the attributes of templates according to the specifications set by the user in another configuration page. On this page, for each template, the user indicates, for each barcode found into the document, which property or attribute of the document will be filled with that barcode.  

Revision as of 14:43, 22 December 2010


The Aim: Barcodes and DMS LogicalDOC

The extraction of barcodes is sometimes needed when the Document-Management-System has to handle structured documents as records. The presence of barcodes in such kind of documents can be used to surecly extract informations that can automatically stored as document metadata. In LogicalDOC we have the opportunity to use the most commonly used barcodes to capture more informations about documents without having the user to enter these informations by hand.

Features we want to implement

We want to extract barcodes from documents asynchronously through the scheduled task BarCode Reader, which will check for barcode inside image or pdf file. This files must comply with the configuration parameters set in a specific page in the Administration section. In this page the user can specify:

  • inclusions and exclusions of documents that contain specific characters into their titles
  • the templates to which are associated the documents that must be parsed

The barcodes will be associated to the attributes of templates according to the specifications set by the user in another configuration page. On this page, for each template, the user indicates, for each barcode found into the document, which property or attribute of the document will be filled with that barcode. The barcode types that are supported are:

   * UPC-A and UPC-E
   * EAN-8 and EAN-13
   * Code 39
   * Code 93
   * Code 128
   * QR Code
   * ITF
   * Codabar
   * RSS-14 (all variants)
   * Data Matrix
   * PDF 417 ('alpha' quality)
   * Aztec ('alpha' quality) 

Technique on how to implement JBPM

These settings will be defined by the token similarly to what happens for the settings of the template schema.