TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace:
technote:long_barcodes

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
technote:long_barcodes [2018/06/20 00:32] – [Hashing] Scott Cunliffetechnote:long_barcodes [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Dealing With Barcodes Longer Than 10 Characters In Length ======+======Barcodes Longer Than 10 Characters In Length ======
  
-TapeTrack has a Volume-ID limit of 10 characters in length.  Any volumes with an ID longer than 10 characters must be modified to fit within this criteria.+TapeTrack has a [[concepts:unqualified_barcode|Volume-ID]] limit of 10 characters in length.   
 + 
 +Any volumes with an ID longer than 10 characters must be modified to fit within this criteria.
  
 There are several ways in which can be achieved, such as truncation, translation or hashing. There are several ways in which can be achieved, such as truncation, translation or hashing.
 +
 +{{:desktop:desktop_scan_window_remove_suffix.png?maxwidth=700}}
  
 ===== Truncation ===== ===== Truncation =====
  
-Truncating a barcode, or volume-ID, involves trimming off the start or end down to 10 or fewer characters.+Truncating a barcode, or [[concepts:unqualified_barcode|Volume-ID]], involves trimming off the start or end down to 10 or fewer characters, or removing characters from the center via masking.
  
 Truncating a barcode can be achieved by several different methods. Truncating a barcode can be achieved by several different methods.
Line 15: Line 19:
 Barcodes can be truncated via the TapeTrack Scan window in TapeMaster, Lite and Checkpoint. Barcodes can be truncated via the TapeTrack Scan window in TapeMaster, Lite and Checkpoint.
  
-<note tip>This method only truncates volume-ID's through the scan window </note>+<note >This method only truncates volume-ID's through the scan window </note>
  
-Information on truncating a barcode via the scan window can be found [[desktop:scan_window#truncating-a-scanned-Barcode|here]].+For detailed information please see [[desktop:scan_window#truncating-a-scanned-Barcode|Truncating a barcode via the scan window]].
  
 ==== Truncation Via Media Properties In TapeMaster ==== ==== Truncation Via Media Properties In TapeMaster ====
  
-Truncation of a barcode by removing the suffix (eg removing L6 from 1234567890L6) can be achieved by setting the ''Remove Suffix'' option in the media properties via TapeMaster.+Truncation of a barcode by removing the suffix (eg. removing L6 from 1234567890L6) can be achieved by setting the ''Remove Suffix'' option in the media properties via TapeMaster.
  
-<note tip>This method will truncate all matching volume-ID's regardless of length and will only act on the suffix</note>+<note >This method will truncate all matching volume-ID's regardless of length and will only act on the suffix</note>
  
-Truncating a barcode via the [[object:media#options|media properties]] tab. Adding L6 in the ''Remove Suffix'' field will remove L6 from any matching volume-ID (eg removing L6 from 1234567890L6) regardless of barcode length.+Truncating a barcode via the [[object:media#options|media properties]] tab. Adding L6 in the ''Remove Suffix'' field will remove L6 from any matching volume-ID (eg removing L6 from 1234567890L6 to input as 1234567890 or 123456L6 as 123456) regardless of barcode length.
  
-Adding L* will remove any 2 digit suffix from the volume-ID that starts with L (eg 123456L6 will truncate to 123456, 1000000001L3 will truncate to 1000000001)+Adding ''L*'' will remove any 2 digit suffix from the volume-ID that starts with L (eg. 123456L6 will truncate to 123456, 1000000001L3 will truncate to 1000000001)
  
  
Line 35: Line 39:
 ===== Translation ===== ===== Translation =====
  
-Translating a barcode, or volume-ID, involves swapping a recognisable pattern for an alternate value within the 10 character limit via translation statements in a ttidef file.+Translating a barcode, or volume-ID, involves swapping a recognizable pattern for an alternate value within the 10 character limit via translation statements in a ttidef file.
  
-<note tip>This method works with command line programs, such as [[cli:tmss10sync|TMSS10Sync]], via ttidef file statements as well as through configuration files in TapeMaster, Lite and Checkpoint.</note>+<note >This method works with command line programs, such as [[cli:tmss10sync|TMSS10Sync]], via ttidef file statements as well as through configuration files in TapeMaster, Lite and Checkpoint.</note>
  
-Using a translation statement **AddTranslation(VOLUME, "A6??????????", "^^~~~~~~~~~~");** in the ttidef file, any 12 character volume-ID starting with A6, such as A61234567890, will drop the first two characters and keep the next 10, inputting as 1234567890.  +Using a translation statement **AddTranslation(VOLUME, "A6??????????", "^^~~~~~~~~~~");** in the ttidef file, any 12 character volume-ID starting with A6, such as A61234567890, will drop the first two characters and keep the next 10, inputting as 1234567890.  
 + 
 + 
 ===== Hashing ===== ===== Hashing =====
  
-Hashing a barcode, or volume-ID, involves replacing the barcode with its 8 character hashed value, preceded by the value ''#-'' to allow identification that the volume-ID has been hashed.  It is a good practice to put the true, or un-hashed, barcode in the attribute field to enable a human readable value as well as the hashed volume-ID.+Hashing a barcode, or volume-ID, involves replacing the barcode with its 8 character hashed value, preceded by the value ''#-'' to allow identification that the volume-ID has been hashed.  
  
-<note tip>Barcodes can be hashed via ttidef files for command line programs as well as through configuration files in TapeMaster, Lite and Checkpoint.</note>+Reasons for hashing a barcode include extended length barcodes (11 characters or more) and barcodes that have spaces or other illegal characters.
  
-Using a translation statement AddTranslation(VOLUME, “???????????*”, “#”); in the ttidef file, any 11 character or longer volume-ID will be hashed, so 111111222222 would be hashed to X-2E8CA12F+It is a good practice to put the true, or un-hashed, barcode in the Attribute field to enable a human readable value as well as the hashed volume-ID. 
  
-Using the translation code block below in the configuration files will achieve the same result as the translation statement in the ttidef file above.+Adding the un-hashed barcode to an extended attribute field can be manually added using the [[cookbook:long_barcodes_paste|Paste Long Barcode function]] or automated by setting the field ''Long Barcode Attribute'' in the Customer Properties ''Options'' tab to the required Attribute field. 
  
-<sxh>+<note>Barcodes can be hashed via ttidef files for command line programs as well as through configuration files in TapeMaster, Lite and Checkpoint.</note> 
 + 
 +==== Hashing via Scanning  ==== 
 + 
 +Long [[object:volume|Volume-ID's]] can be Scanned-In to [[desktop:master|TapeTrack TapeMaster]] 
 + and hashed simultaneously by placing a ''#'' in the **Edit** field of the [[desktop/scan_window|Scan]] window. 
 + 
 +Once the Volumes have been added, the long barcode can be added to the Description (or other Attribute) field using the [[cookbook:long_barcodes_paste|Paste Long Barcode function]] or added to an extended attribute field automatically by setting the field ''Long Barcode Attribute'' in the Customer Properties ''Options'' tab to the required Attribute field.  
 + 
 +====Hashing via ttidef file ==== 
 + 
 +Using a translation statement **AddTranslation(VOLUME, “???????????*”, “#”)**; in the ttidef file, any 11 character or longer volume-ID will be hashed, for example ''111111222222'' would be hashed to ''X-2E8CA12F'' 
 + 
 +Using a translation statement **AddTranslation(VOLUME, “*? ?*”, “#”);** in the ttidef file, any barcode with a space (the space can be replaced with any other illegal character) will be hashed, for example ''Monday 01'' would be hashed to ''X-DCD72719''. 
 + 
 +====Hashing via configuration files==== 
 + 
 +Using the translation code block below in the configuration files will hash any 11 character or longer volume-ID's. 
 + 
 +<code>
 barcodes= barcodes=
 { {
Line 58: Line 83:
    );    );
 }; };
-</sxh>+</code> 
 + 
 +Using the translation code block below in the configuration files will any barcode with spaces. 
 + 
 +<code> 
 +barcodes= 
 +{ 
 +   translations= 
 +   ( 
 +      { filter="*? ?*"; value="#"; } 
 +   ); 
 +}; 
 +</code> 
 + 
 +<note tip>Barcode hashing can also be achieved using [[subsystem:barcode|Barcode Administration]].</note>
  
-<note tip>Hashing barcodes that have spaces in the middle, such as **Monday 1**, is the simplest method (spaces are not permitted in volume-ID's) for translation to an acceptable value. The code for handling spaces be **AddTranslation(VOLUME, “???????????*”, “#”);** for the ttidef file and **{ filter="*? ?*"; value="#"; }** for the configuration files.</note>  +{{tag>technote barcode long-barcode hash config-file}}
technote/long_barcodes.1529454767.txt.gz · Last modified: 2025/01/21 22:07 (external edit)