#2 and the system way to overcome barcode ambiguity would be to IN VERSION UPDATE take up the notion that in some environments barcodes are not machine-read barcodes but rather typed-in numeric information. For these Manual Barcode users a new variable ManualBarcodeLength and small codebit to add the "front-zeroes" could be useful, wouldn't it?
Something like ... -- System barcode length BCCharlength = 5 BCInput BCInput.charcount The adding (BCCharlength - BCInput.charcount) long string of "front-zeroes" to the input before it is fed to the database. In this way the input feed "1" would be processed as "00001". ---- But I do not actually know how wide is the habit of typing the barcodes! Do you use machine-reading to feed the item barcodes, Sunil my friend? ----- (Mr.) Kari Blomster, librarian Hailuoto Public Library, Finland | http://www.hailuoto.fi/sivu/fi/kuntapalvelut/perus/Sivistyspalvelut/kirjasto/ Profiles | http://www.hailuoto.fi/sivu/fi/kuntapalvelut/perus/Sivistyspalvelut/kirjasto/verkkopalvelut/ -- View this message in context: http://koha.1045719.n5.nabble.com/Re-Searching-by-the-exact-barcode-in-cataloguing-tp5721250p5721366.html Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
