Differences

This shows you the differences between two versions of the page.

--- barcode-processing [2018/01/15 00:14] – [Parsing Logic] Scott Cunliffe
+++ barcode-processing [2018/08/10 02:40] (current) – removed Scott Cunliffe
@@ Line 1: / Line 1: @@
-====== Barcode Processing ======
-When a barcode is scanned in TapeTrack it is sent to the Server component to be interpreted and split (or parsed) into its respective components.
-===== Barcode Syntax Rules =====
-A TapeTrack Barcode may be up to 20 characters in length and may contain a [[:master:customer|Customer-ID]] and [[:master:media|Media-ID]] component and must contain at least a [[master:volumes|Volume-ID]] component.
-==== Parsing Logic ====
-The TapeTrack Server parses barcodes as follows:
-The unparsed barcode will be looked up in the [[Barcode Translation Table]] and if it is found the translated barcode will be substituted.
-When a corresponding [[TapeMaster Barcode Interpretation Definitions | Barcode Interpretation Definition]] is found the barcode is split into [[:master:customer|Customer_ID]], [[:master:media|Media-ID]] and [[:master:volumes|Volume-ID]] components.
-If the [[:master:customer|Customer_ID]] and [[:master:media|Media-ID]] components are not resolved then the [[desktop:scan_window#Setting-the-Default-Customer-ID-and-Media-ID|Scanned Default Customer-ID]] and [[desktop:scan_window#Setting-the-Default-Customer-ID-and-Media-ID|Scanned Default Media-ID]] values (if any) are used to set the [[:master:customer|Customer_ID]] and [[:master:media|Media-ID]].
-If the [[:master:customer|Customer_ID]] and [[:master:media|Media-ID]] components are not resolved then the [[master/user#defaults| User Profile Default Customer-ID]] and [[master/user#defaults|User Profile Default Media-ID]] values (if any) are used to set the [[:master:customer|Customer_ID]] and [[:master:media|Media-ID]].
-If the [[master:media|Media-ID]] component remains unresloved and the [[TapeMaster Creating Customers | Customer Properties]] has the ''No-Duplicate Volume-ID'' attribute set then the server will attempt to find the [[master:media|Media-ID]] for the unique [[master:volume|Volume-ID]] if the [[master:volumes|Volume-ID]] exists.
-Using the [[master:customer|Customer_ID]] and [[master:media|Media-ID]] values the [[Media Properties]] are looked up.
-If the [[TapeMaster Creating Media Types | Media Properties]] has the ''Remove Volume-ID Suffix'' value set and there is a matching suffix the suffix is removed.
-If the [[TapeMaster Creating Media Types | Media Properties]] have the Modulo 43 option **AND** there is no corresponding length exclusion all except the last digit of the component [[:master:volume|Volume-ID]] are processed through the Modulo 43 algorithm.
-If the last digit of the [[:master:volumes|Volume-ID]] does not match the calculated Modulo 43 value a barcode scanning error is returned.
-If the last digit of the [[master:volumes|Volume-ID]] does match the calculated Modulo 43 value the barcode is returned with the [[master:volumes|Volume-ID]] component stripped of it's check digit.
-==== Additional Logic for Batch Programs ====
-Batch programs that parse barcodes will also check for the existence of the environment variable {{EnvVariable|TMSS10BARCODECONFIG}} when the program starts.
-This variable is used to define the path to a config file containing settings that influence how barcode is performed.
-<code>
-set TMSS10BARCODECONFIG=c:\tmss\etc\barcode.cfg
-TMSS10ValidateBarcode
-</code>
-==Example Batch Barcode Config File==
-<code>
-defaults =
-{
-    customer-id = "ACME";
-    media-id = "DL";
-};
-</code>
-=== Programs that load the Barcode Config File ===
-[[cli:tmss10sync|TMSS10Sync]] \\
-[[cli:tmss10inventory|TMSS10Inventory]] \\
-[[cli:tmss10validatebarcode|TMSS10ValidateBarcode]] \\
-== See Also ==
-*[[Modulo 43]]
-[[Category:Barcode Scanning]]