[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
And Kyle's reply is valid as well. There's something that's not right, and it could either be the barcode reader or the barcode. Kyle's suggestion to scan into notepad to see what the system 'sees' is excellent.

DAS

David Lowe wrote:

But we shouldn't have to designate anything before we scan a book at checkout.

________________________________

From: David Snyder [mailto:dsnyder at bu dot edu]
Sent: Tue 2/22/2005 11:22 AM
To: David Lowe
Subject: Not an indexed field



Hi David --

Responding just to you, since I'm sure at least 10 other people will
have the answer. Yes, it's happened to us IF:

you just scanned the barcode without designating that it was a barcode
field [by typing b first]

AND

the barcode did not conform to the specs provided...usually if the
barcode is not the proper length. Note that we do NOT have checksum
implemented, but if you did, then that would also cause the barcode to
be rejected if the checkdigit was incorrect.

I'm sure that there are other reasons for it not to work, but you can
see what the system THINKS that it is seeing by typing b before scanning
the barcode. It will then 'read' whatever is there and try to place the
barcode in the index at that point.

Hope this is clear...my mind seems to be stuck in low gear this morning.

Dave Snyder
Systems Librarian
Boston University Libraries
dsnyder at bu dot edu
617 353-0601





--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies: INNOPAC at innopacusers dot org
Update your subscription options: http://innopacusers.org/mailman/listinfo/innopac