Actually, #6 is the root of #1 and #2 and probably #4. The problem with is your system and mysql recognizing your timezone, I believe. Test this on the command line with the following commands: unset TZ date export TZ="US/Central" date See what timezone your system *is* configured for (with TZ unset) and see if the system can handle your TZ. I'm guessing the system itself can, but mysql doesn't like it. So the next thing to look at are the TZ's in mysql, and updating them with * mysql_tzinfo_to_sql*<http://dev.mysql.com/doc/refman/5.1/en/mysql-tzinfo-to-sql.html> : http://dev.mysql.com/doc/refman/5.1/en/mysql-tzinfo-to-sql.html Note, your sysadmin can run (and even schedule) rebuild_zebra.pl without setting TZ, just to get you started. As for #5, the normalized call number for sorting is the call number... normalized for sorting. That is, certain classes of characters that are to be treated as equivalents are mapped to a common character. In your example, it looks like whitespace is mapped to "_". Basically, don't worry about it unless call number order elsewhere seems not to be accurate. That leaves really only #3, for which you should check that you have the best version of your barcode font installed, or try to characterize which data "blocks out" and which prints OK. --Joe Atzberger On Tue, Jan 27, 2009 at 3:56 AM, Zeno Tajoli <tajoli@cilea.it> wrote:
Hi,
1) When we catalog new items (whether it be a record we have imported in, an item we have added to an existing record or a new record we have done original cataloging for) we are unable to get it to show up in the results screen when we search for it in the catalog. I can enter the barcode at check in and it comes up and I can enter the barcode in at checkout and check it out to a patron and it comes up fine. It just doesn't come up when I search for it in the catalog.
2) Because the book is not coming up when I search for it I'm also not able to search for it when I want to print the barcode. I can print the barcode using a barcode generator but it should work in the program.
And finally, 6) Our It person found this today:
Cron job to update Zebra indexes every 15 minutes returning the following via email: X-Cron-Env: <HOME=/home/koha> X-Cron-Env: <PERL5LIB=/home/koha/kohaclone> X-Cron-Env: <KOHA_CONF=/home/koha/koha-dev/etc/koha-conf.xml> X-Cron-Env: <TZ=US/Central> X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=koha> X-Cron-Env: <USER=koha>
DBD::mysql::db do failed: Unknown or incorrect time zone: 'US/Central' at /home/ koha/kohaclone/C4/Context.pm line 675.
problems 1), 2), 6) are the same: you use Zebra as indexer and Zebra doesn't work well
So tell ro your IT support to read CAREFULLY the install.* files in the koha package and try to start Zebra and indexing of the bibliographic/holding data.
Bye
Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha