---- Reported by martin.brenner@whitfieldschool.org 2009-10-21 16:34:23 ---- When importing cataloging and item records from a Follett system, the barcode record is in the form T0003452 where the 0's are filler to make a total of seven digits. The barcodes on the books, at least in our library, are of the form T 3452 (Tspacenumber). The T prefix setting on itemBarcodeInputFilter is supposed to allow for this. It was not working for me, so I looked at the code. By changing the \d to a \s in the in the if statement in the section: elsif ($filter eq 'T-prefix') { if ($barcode =~ /^[Tt](\d)/) { (defined($1) and $1 eq '0') and return $barcode; $barcode = substr($barcode, 2) + 0; # FIXME: probably should be substr($barcode, 1) from /usr/share/koha/lib/C4/Circulation.pm, this fixes the problem for our library. I do not know perl, but I imagine there should be a way to add both options if the /d is needed (though, I noticed when it was set that way, if you entered T3452 manually it would return T0000452 and cut off the 3. So, I'm not sure the \d is even correct) --- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:14 UTC --- This bug was previously known as _bug_ 3724 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3724 Unknown operating system Linux - Debian. Setting to default OS "All". Actual time not defined. Setting to 0.0
I'm working with another Follett library. They have bar codes that have mixed case prefixes (sometimes upper and sometimes lower) but they want them to always be interpreted as upper case (or maybe it doesn't matter once they've converted to Koha?) Anyway, they have barcodes that look like this: p 000123 and they want them to be interpreted like this: P123 Is this the same problem?
(In reply to Lori Ayre from comment #1) > I'm working with another Follett library. They have bar codes that have > mixed case prefixes (sometimes upper and sometimes lower) but they want them > to always be interpreted as upper case (or maybe it doesn't matter once > they've converted to Koha?) > > Anyway, they have barcodes that look like this: p 000123 > and they want them to be interpreted like this: P123 > > Is this the same problem? Koha doesn't care about case sensitivity, so I think it's a similar problem. Strange is that it's using P instead of T?