More about foreign barcodes

It is possible to have a mixed barcode environment.

When a record uses the Foreign Barcode field, Content Manager will recognise that barcode on printed labels and when scanning.

However, if the Foreign Barcode field is blank, Content Manager will recognise the Content Manager-generated barcode field on printed labels and when scanning.

  1. Is it a foreign barcode?

    If not, then

  2. Is it a Content Manager barcode?

    If not, then

  3. Does it match the ASCII value (raw) of a compressed record number?

    If not, then

  4. Does it match the ASCII value (raw) of an uncompressed expanded record number?

    If not, then

It does these checks to find out whether it is Part One of a multiple part record:

  1. Does it match the ASCII value (raw) of a compressed record number + -01 ?
  2. Does it match the ASCII value (raw) of a uncompressed expanded record number + -01 ?

    These are to allow for the fact that a label may have been printed before a later part was created and Content Manager may have renumbered the first part.

  3. Same check again for /01
  4. Same check again for v01
  5. Same check again for p01
  6. Same check again for #01
  7. Same check again for .01
  8. Same check again for :01
  9. Same check again for \\01

If Content Manager gets to this point trying to recognise a scanned label, it declares the label invalid.

NOTE: Foreign barcodes that contain non-printable characters are not supported, for example, tab etc.

See also Modifying record numbers for instructions about modifying foreign barcodes.