Re: Patron Barcodes - Possible problems with change in scheme
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Fri, 10 Aug 2001 15:59:01 -0400
- From: Daniel Phelan <dphelan@xxxxxxxxxx>
- Subject: Re: Patron Barcodes - Possible problems with change in scheme
Do these barcodes scan ? If they do and are legitimate bcodes you have
only 2 problems : 1) duplication and 2) the chance that one that does
not scan because of the lack of check digit. Our admin. did the same
but checked with us first and we quality-controlled the codes. If the
code is not good, will they redo the card or can you paste another label
over top ?
"Fry, Carrie" wrote:
> Since we came up on III, we have been using code 39 barcodes with 13 digits
> including a check digit, for example: 1000010039997
> I just discovered that University Services has recently been making up their
> own barcode numbers using 1000 + Social Security Number and printing the
> barcode on the student ID cards. This still adds up to the 13 digits,
> however there is no longer a check digit.
> The barcode on the student ID card is only used by the library, but no one
> felt it necessary to let us know about this change. Besides the FERPA
> implications and the possibility of duplicate barcode numbers (since the
> library does give out some library cards that are not student IDs) are there
> other problems that could be caused by the use of this scheme? Apparently,
> they have been doing this for awhile and I have not noticed anything, but I
> am worried about possible effects down the road.
> Thanks for any advice,
> Carrie Fry
> Electronic Services/Systems Librarian
> Seattle Pacific University Library
> (206) 281-2124
> This message was distributed through the Innovative Users Group INNOPAC list.
> Private replies: "Fry, Carrie" <cfry@xxxxxxxxxx>
> Public replies: INNOPAC@xxxxxxxxxx
> Archives: http://innopacusers.org/list/archives/
This message was distributed through the Innovative Users Group INNOPAC list.
Private replies: Daniel Phelan <dphelan@xxxxxxxxxx>
Public replies: INNOPAC@xxxxxxxxxx