Frequently Asked Questions About Patron Barcode Issues
May 1997

This document is composed of two parts. Part one provides some basic conceptual information about barcodes in general. Part two presents answers to questions concerning the use of barcodes on patron ID cards and barcode numbers in patron records for both the current ILLINET Online system and the DRA system. The questions and concerns in part two have been selected for their relevance to a general ILCSO audience. New, important questions continue to come in, so this document is likely to evolve.



Part One: General Barcoding Concepts

Concept 1: A barcode represents a series of characters.

A barcode consists of a series of parallel bars and spaces that represent numbers, letters, and/or other characters like "$" and "/". A helpful analogy is Morse code-the defined series of long and short pulses used to transmit telegraph messages. In Morse code the sender and receiver both know that a certain combination of short and/or long pulses represents a particular letter. In barcodes, every character has a distinct representation in a combination of wide and narrow bars and wide and narrow spaces and the barcode scanner is able to translate this back into the characters that these bars and spaces represent. A barcode "alphabet" is called a "symbology."

Concept 2: There are several barcode symbologies.

Some of the confusion about barcodes is due to the fact that there are several different barcode symbologies. Most people frequently encounter the "UPC" (Universal Product Code) symbology, as this is what is used on the products we buy at most retail stores. There are several other symbologies including Codabar, Code 39, EAN, Code 93, Code 128, and Postnet (used by the U.S. Postal Service.) For each symbology, there is a predefined pattern of bars and spaces that represents each character it supports, but, this pattern is different across symbologies. In other words, the digit "2" is represented by a different pattern of bars and spaces in Codabar than in Code 39.

Concept 3: There are pros and cons for the various symbologies.

Not all symbologies are suitable to all tasks. Some symbologies support more characters than others. Code 128, for example, can represent any ASCII character. UPC supports digits only. Codabar and Code 39 fall between these two in degrees of support. Codabar supports 0-9, and the characters "-$:/.+". Code 39 supports all of the characters supported by Codabar and also A-Z and a space. To allow for support of these additional characters, each individual character is larger in Code 39 than in Codabar. Code 39 represents characters by using combinations of 5 bars and 4 spaces; Codabar uses 4 bars and 3 spaces. Thus, Codabar labels are generally shorter than Code 39 labels­p;this can be an advantage where space is a concern. Various industries have adopted various symbologies as either their official or de facto standard. UPC is a retail standard in the U.S., Code 39 is the Department of Defense's standard and is also used for auto parts, Codabar is the standard for blood banks and is very common in library circulation systems.

Concept 4: The symbology can be self-checking or not.

Several of the barcode symbologies are considered to be "self-checking." This means that the barcode has a particular format that helps the barcode reader determine that it has read the entire barcode. Codabar and Code 39 are both examples of self-checking symbologies. (One barcode symbology confirmed as being not self checking is called "Plessey," but there may be others.) Both Codabar and Code 39 formats include defined "start" and "stop" characters that tell the reader that it has read the entire label. This prevents, for example, a scanner misreading a label that has been partially removed from the item. If the self checking test fails, the scanner will beep or otherwise alert the operator that the label was not read. You have probably experienced this at the grocery store when there is moisture on the glass cover of the scanner. This self check is not done in the application (e.g., the library circulation system or grocery store inventory system) but in the physical scanner itself.

Concept 5: The characters represented by the barcode can include a check digit.

Another level of verification can be provided by using a pre-defined mathematical formula to calculate a "check-digit" for the data represented by the barcode. This check digit then typically becomes the last digit represented in the barcode. When the barcode is scanned or typed, the system (e.g., the library automation system) does the same calculation on the barcode and compares the check digit it just calculated against the one that was entered. If these numbers match, the system has at least proven that the string of numbers entered fits its expected barcode format. If the check digits do not match, the operator probably sees an error message from the application saying something like "invalid barcode number." The application software must be programmed to expect a check digit and must use the same mathematical formula used to calculate the check digit when verifying the check digit. If the application software is not able to perform check digit calculations, the check digit will be treated just as any other character in the barcode. In other words, an application that does not verify check digits can still read barcode labels that have check digits, but it will then simply look for a matching number in its files. If barcode labels do not include check digits, it is likely that the numbers represented by the barcodes are simply sequentially assigned and so any number of the right length could be a valid barcode number. Thus, without check digits, there is a much greater likelihood of entering a wrong barcode number (particularly when manually typing the number) that is actually in the database but assigned to a different person, item, etc. Check digits are most useful when barcode numbers are entered by hand, as it is much more likely for a person to mistype a number than for a barcode reader to misread a number. There are a variety of formulae that can be used to calculate check digits; the one ILCSO is recommending to its libraries is called "Mod 10, left to right."

Concept 6: Scanners "care about" symbology; Applications "care about" numbers.

The ILCSO Office has heard several people mistakenly say that the DRA system is "requiring" Codabar labels on items and patron IDs. This is not true. The DRA system is only aware of the number that the barcode represents, not the symbology in which it is printed. Only the scanners used to read the barcodes "care about" what symbology is used to print the barcode. Most scanners are able to read a variety of symbologies without being reconfigured between reads. The DRA system is really only concerned about the number that the barcode represents. The ILCSO Office has told DRA that our barcodes will represent 14 digit numbers, that barcodes for items will include a 4 digit number that identifies the ILCSO library that owns the item, that barcodes for patrons may include this 4 digit identifier for the library that has granted the ID to the person, and that some of our barcodes will include check digits. As not all of our libraries have used check digits as part of the 14-digit number, the DRA system will look up the 4 digit institution code to see if it does or does not include a check digit.


Concept 7: Barcodes can be "dumb" or "smart." This is independent of their symbology or check-digit configuration.

It probably goes without saying, but a barcode can be self checked by the scanner and have its check digit validated by the application, but it also must be on file in the correct record in the database to be useful. There are two basic approaches to barcoding library collections. In one approach the library buys labels in bulk and, as they apply the labels to the items, library staff create a record in the database that associates the barcode number on the label with the item. These labels are often called "dumb" labels as they do not represent any specific item or person until this information is entered into the database. The other approach is to perform a computerized "sweep" through the online catalog and automatically assign a barcode number to each item. The new barcode number, and other information about the item such as its title and call number, are then written to a file that is sent to a barcode vendor. The vendor then produces labels which include the title (and other information, if desired) as well as the barcode number that has been assigned to the item. Library staff then match these labels up to the correct items. The labeling process chosen by the library does not imply either the symbology of the barcode, or the format of the barcode number.

Other Resources for Information

Here are some other sources on the Web found to be useful in learning more about barcodes:
http://www.faxon.com/Standards/barcode/barcoderg1.html
http://www.adams1.com/pub/russadam/barcode1.html
http://www.techexpo.com/WWW/visionshape/toolkit.html#intro
http://www.mgfx.com/


Part Two: Frequently Asked Questions


Q: Where do we ask questions?
A:



Q: Do I have to use patron barcodes in either current IO or for the new DRA system?
A:



Q: What is the ILCSO standard format for patron barcodes?
A:



Q: Do all ILCSO libraries have to use the same barcode symbology?
A:



Q: What is the difference between barcodes for patrons and barcodes for items?
A:



Q: What are some pro's and con's to the two types of patron barcode formats recommended for ILCSO libraries?
A: There are several factors that libraries should take into consideration when deciding which of the two patron barcode formats to use:

Advantages to using Patron type 1 barcodes:

Disadvantages to using Patron type 1 barcodes:

Advantages to using Patron type 2 barcodes:

Disadvantages to using Patron type 2 barcodes:



Q: My institution's barcode number on the patron ID is just the Social Security Number, with no number "1" prefix or any other digits. Is this a problem?
A:



Q: Does my circulation desk scanner need to be programmed differently for patron type 1 versus type 2 barcode numbers?
A:



Q: How do I include barcode numbers with my patron tapes?
A:


Q: If my campus computing center can't create and maintain barcode numbers for our batch loaded patron records, what can we do if we want to use barcodes on our patron IDs?
A:



Q: So the concept of "smart" vs. "dumb" barcodes is valid when discussing patron barcodes?
A:



Q: What happens to existing barcode data when new patron data are batch loaded in the current system?
A:



Q: Where can I purchase patron barcode labels?
A:



Q: Is there a standard layout for ID cards for ILCSO library patrons?
A:



Q: My campus wants to institute a "universal" ID card, so that the same card can be used anywhere on campus. What should I do?
A:



Q: Can we use a magnetic stripe for our patron ID numbers instead of barcodes?
A:



Q: When my campus starts printing barcodes on our patron ID cards, do we have to start using MILO's barcode circulation module at the same time?
A:



Q: When my library starts using patron barcodes, can we stop including the patron's Social Security Number in the patron record itself?
A:
No.


Q: Do I need to worry about check digits for my patron barcodes?
A:



Q: My campus has issued barcode numbers on our patron IDs that do not represent the Social Security Number nor that follow either of the ILCSO recommended formats. Will this be a problem?
A:



Q: My campus has issued barcode numbers on our patron IDs that do represent the Social Security Number, but there are also hyphens inserted between the portions of the SSN. Will this be a problem?
A:



Q: My library is planning to wait to begin using barcodes on our patron IDs until the new DRA system's enhanced patron record is available. When will we receive the specifications for the creation of these patron records?
A: The ILCSO Office and AITS have been working with DRA staff on specifications for patron records and patron batch loader programs, but the specs are still in draft stage at this time. We recognize that libraries and their computing centers will need as much lead time as possible to adopt the new DRA patron record format. We will distribute the final specifications to the ILCSO community as soon as they are available.




ILCSO Home Page
What's New | Consortium Business | Services | Search
Calendar | Governance | Committees | Forums
Documentation | Networking | Training

Problems or comments?  Please send e-mail to ILCSO Office.