Joe
I have reworked the barcodes in Koha because the barcodes Follett spits out in
the export do not match what is actually in Follett. Will the T-Prefix remove
the 2 zeros and add a space to match the barcode labels that Follett created?
Thanks!
Ed
Edward J. Roche
Network Administrator
Solanco School District
717.786.2151 x2437
"At the End of the Day, Did You Play to Win or Not to Lose?"
From: Joe Atzberger [mailto:ohioc...@gmail.com]
Sent: Monday, April 06, 2009 5:35 PM
To: Roche III, Edward
Cc: koha-devel
Subject: Re: [Koha-devel] Barcode Not Found
2009/4/6 Roche III, Edward <edward_ro...@solanco.k12.pa.us>
Good afternoon all.
Brief History for that have not seen my other posts.
We are trying to migrate to Koha from Follett, when biblio info is
exported from Follett the barcodes have zeros add in place of a space, T 12345
comes out as T0012345. I updated my records and re-import the barcode field and
but when I try to check out a book it tells me barcode not found.
I have be trying some different thing with Mike Hafen. We have come to
find that Koha is reading the barcode correctly but just isn’t finding it in
the DB.
Do you have syspref "itemBarcodeInputFilter" set? The T-Prefix setting was
designed for migrating Follett libraries without changing their barcodes. If
you have now reworked your data and still are filtering the barcodes, then that
would predict failure.
We have found that the DB is pretty much set to latin1 as the character
set
What does that mean? The intent of the encoding_scratchpad part of Koha setup
is to get all Koha's internal DB settings to UTF-8. What makes you think
anything is latin1?
but when I created the DB I select UTF-8 and I also converted the
export data from Follett to UTF-8. Do I need to change the char set for the
whole MySQL or is that a non-issue.
It's a non-issue because none of your barcodes have characters that would be
represented any differently in UTF8 than they are in latin1 (unless you care
about the binary level, and we don't).
I really have like this product but out librarians have said they will
not re-barcode because on average they have 16k+ items that they would have to
change. I am at wits end with this issue and I would hate to be able to use
Koha because it is everything we want except for this issue.
If anyone has seen this before please let me know your thoughts.
This problem has persisted for several months. At some point you might
consider professional library data-migration service. You are currently in the
strange position of having created new data mapped from your old barcode
values, so it is really on you to figure out if they are now correct or not.
We can't see your barcodes, your new data or your old data.
--Joe
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
