- Koha-devel - lists.koha-community.org

‡biblios.net now available for free to all
by Nicole Engard 20 Jan '09

20 Jan '09

Fellow catalogers and Koha community members, I have been spending a lot of time these last few months working on getting a new web-based cataloging tool ready for you all. It's finally time! I'd like to invite you to sign up for free and try out ‡biblios.net (www.biblios.net) a community cataloging tool from LibLime. So, what the heck is it? ‡biblios.net is a web-based original and copy cataloging tool with built in federated search of any Z39.50 target (via an integrated search registry with over 2000 targets - or by adding your own) and a large (30 million strong) shared database of catalog records. This means that you can visit ‡biblios.net and benefit from the work of other catalogers who have gone before you. You can also edit and contribute to the database without any restrictions. I have also worked on creating some macros (others can be written by users) to help streamline some of our cataloging processes and templates for common item types to make original cataloging a little bit easier :) Best of all, you can set ‡biblios.net to automatically add records to your Koha system with the click of a button! I'm looking for both novice and professional catalogers to give me their opinions of the tools, services and overall user friendliness of ‡biblios.net. I am of course also looking for people to join the community so that this tool and grow and help us all with our cataloging work. I have worked very closely with the development crew on this new tool and believe very strongly both in it and the ideas behind it. The fact that we all work so very hard on our cataloging makes the fact that the records in ‡biblios.net are freely-licensed under the Open Data Commons (www.opendatacommons.org) all that more appealing. If you want to learn more you can read through the documentation on the site (www.biblios.net) and/or take a peek at this great write up by Jonathan Rochkind: http://bibwild.wordpress.com/2009/01/07/bibliosnet-and-the-future-of-catalo… Thank you so much! I can't wait to hear what you all think!! Nicole C. Engard Open Source Evangelist, LibLime --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 nce(a)liblime.com AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/ _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

1 0

authorities question again
by Rafael Antonio 20 Jan '09

20 Jan '09

Dear all I have seen several KOHA 3.0 demos where the page Authority search results allways show 0 biblio records. I have tested and did some links between biblio and authority but it never never changes. Does we need to run any script? Thanks, Rafael Antonio

3 2

About Mail::Sendmail
by Nahuel ANGELINETTI 16 Jan '09

16 Jan '09

Hi people, I'm adding the ability to send shelves by mail. During my addition I find a problem sending by mail: Wide character in subroutine entry This means the data encode_base64() received is too big. I was copying the script from sendbasket, so I tested with sendbasket and a large basket, the same happen. What is the good fix? Use another library that manage this problems? Still using this complicated library and find a solution, like pre-saving the iso2709 in a temporary file and encode as base64? Maybe someone have the solution to my problem? bests, -- Nahuel ANGELINETTI

4 5

how to handle the link back to amazon?
by Nicolas Morin 16 Jan '09

16 Jan '09

Hi there, I want to gather opinions about a possible small change in the way the Amazon covers are handled in the opac on the detailed view of a record. Currently we show the Amazon cover and link back to the product's page on Amazon's web site from the cover itself. Some librarians I talk to are uncomfortable with the idea that their public library will show a link to a (monopolistic (online-only (us-owned (insert-yr-own-fears-here)))) bookseller in such a prominent way : using the whole cover image as a link. At least some of them would be assuaged, I think, by a more discreet link between their opac and Amazon : removing the link from the image itself and providing it through a tiny text just below the image, saying "source : Amazon", might be a solution. See example at http://www.libfly.com/je-suis-une-legende-livre-25918.html What do you think? Nicolas -- Nicolas Morin Mobile: +33(0)633 19 11 36 http://www.biblibre.com

5 6

virtual hosting of Koha
by Han, Yan 16 Jan '09

16 Jan '09

Hello, All, I have been running Koha on a local server, but am testing to virtual host Koha on a commercial server (for example. Bluehost.com) In local server implementation, you need to "make install" to install Koha. In a commercial server, "make install" is not allowed. So does anyone have any luck to run koha in a commercial host? If so, please let me know the configuration changes, and the company's name. It seems that <virtualhost> configuration is not allowed in this commercial server. If Apache env is not allowed to change in this case, how can we setEnv for "perl5lib" and "Koha_conf"? # KOHA's OPAC Configuration <VirtualHost 150.135.239.44:80> ServerAdmin DocumentRoot /data1/koha/opac/htdocs ServerName kobol ScriptAlias /cgi-bin/koha/ "/data1/koha/opac/cgi-bin/" Redirect permanent index.html http://150.135.239.44:80/cgi-bin/koha/opac-main.pl ErrorLog /data1/koha/log/opac-error_log TransferLog /data1/koha/log/opac-access_log SetEnv PERL5LIB "/data1/koha/intranet/modules" SetEnv KOHA_CONF "/etc/koha.conf" </VirtualHost> Thanks, Yan

3 2

Database size with InnoDB
by Nahuel ANGELINETTI 16 Jan '09

16 Jan '09

Hi people, I don't know if some people have a big experience from InnoDB and MySQL. We just see in mysql documentation innoDB does not reallow the disk space of deleted datas. An example : the disk used by one of our clients, who have only 50 000 notices, is 4GB and is still growing. The explication is innodb don't delete data from disk after a "drop" or a "delete". http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html "Currently, you cannot remove a data file from the tablespace. To decrease the size of your tablespace, use this procedure: " The solution to decrease the size of data file, is to dump, and restore the database... A really bad solution for production installations. Does someone have experimented the same problem? What are your solution about this problem ? bests, -- Nahuel ANGELINETTI

3 3

Another UTF-8 encoding question
by Chadwick, John, DCA 14 Jan '09

14 Jan '09

Play time is over and I am now building a couple of servers using Ubuntu 8.04 and the latest git version of Koha. So far the installations have been clean and easy. I have just one more UTF-8 encoding question. Being in the southwestern U.S. we are trying to deal with some titles that have Spanish character sets to go along with our primarily English character sets. In looking over Koha Wiki entry for encoding and character sets, http://wiki.koha.org/doku.php?id=encodingscratchpad., I have a question about the section on combining characters and collations. The search entry may not necessarily have the special character, but we need to return records with special characters. For those who have had to deal with this, which would you recommend, utf8_unicode_ci or utf8_general_ci for the collation collection? The word Univerzalitás is a unicode combining form. When you copy/paste it into a text editor or use a keyboard to type it, it is most likely going to be the non-combining form: Univerzalitás. (in the non-combining form, the hex for the accented a is: Hex 0301; for the non-combining form it’s: Hex 61, Hex 00e1). Non-combining form: http://www.fileformat.info/info/unicode/char/00e1/index.htm Combining form: http://www.fileformat.info/info/unicode/char/61/index.htm http://www.fileformat.info/info/unicode/char/0301/index.htm Univerzalitás Univerzalitás It seems that the utf8_general_ci collation doesn’t support equality for those two forms. However, utf8_unicode_ci seems to work. If you have combining characters in your data, you may want to go with statements like: ALTER TABLE marc_word MODIFY word VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci; and be sure to add init-connect = ‘SET collation_connection = utf8_unicode_ci’ to your my.cnf Thanks, John +----------------------------------------------------------------------------+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick(a)state.nm.us http://www.nmstatelibrary.org Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System.

1 0

Fixing holding info after an import
by Jason Macki 13 Jan '09

13 Jan '09

Hello, I'm doing an import from another library system to Koha version 3 on Linux. I used the bulkmarcimport.pl script to import the bibliographic information, populating the "biblio" and "biblioitems" tables. Then I ran a program to fill in the holding information by directly inserting rows into the "items" table. That worked, except that the "biblioitems" table has a field called "marcxml", which includes the holding information for that book. Now, if I use the Koha management application to edit and save a holding item, it fills in the holding information in the "marcxml" field of the corresponding "biblioitems" record, and the Koha features which depend on the holding information in the "marcxml" field work properly. My question is, is there a script in Koha 3 that will automatically put the holding information contained in the "items" table into the "marcxml" field of the "biblioitems" table? Thanks very much, Jason

3 2

strange recent indexing problems on koha 3.0.x branch, anyone?
by Mason James 13 Jan '09

13 Jan '09

Hi All The basic issue seems to be that the latest koha 3.0.x branch has some strange indexing (and encoding?) errors (for me at least) i have spotted these 'Invalid XML encoding name' errors when running the zebraqueue_daemon.pl / koha-zebraqueue-ctl.sh scripts - after adding a new bib via... * a z39-pull * web-gui batch-import * cmdline bulkmarcimport.pl script i can replicate this on 2 separate debian-etch boxes rolling my repo back from the latest 3.0.x commit, to the 'v3.00.00' tag fixes the issue (which is good, but i havent clicked to what the issue actually is yet ;/ ) the best way to replicate the indexing error for me, was this... fetch, and rewind the repo $ git-fetch $ git-fetch --tags #needed too ?? $ git rebase origin/3.0.x $ git reset --hard v3.00.00 $ ./misc/migration_tools/bulkmarcimport.pl -d -v -fk -n 10 -file / tmp/sample.mrc deleting biblios .......... 10 MARC records done in 0.157172918319702 seconds $ ./misc/bin/zebraqueue_daemon.pl -f ~/etc/koha-conf.xml 22:52:52-05/01 zebrasrv(17) [session] Session - OK 17 unix:/home/ mason/koha/ashs/var/run/zebradb/bibliosocket 26837 22:52:52-05/01 zebrasrv(17) [request] Auth idPass kohauser - 22:52:52-05/01 zebrasrv(17) [request] Init OK - ID:81/81 Name:ZOOM-C/ YAZ Version:1.116/2.1.54 22:52:52-05/01 zebrasrv(17) [log] function: 1 22:52:52-05/01 zebrasrv(17) [log] Waitaction: 2 22:52:52-05/01 zebrasrv(17) [log] Received DB Update 22:52:52-05/01 zebrasrv(17) [log] action 22:52:52-05/01 zebrasrv(17) [log] specialUpdate 22:52:52-05/01 zebrasrv(17) [log] database: biblios 22:52:52-05/01 zebrasrv(17) [log] enabling shadow spec=/home/mason/ koha/ashs/var/lib/zebradb/biblios/shadow:4G 22:52:52-05/01 zebrasrv(17) [log] cache_fname = /home/mason/koha/ashs/ var/lib/zebradb/biblios/shadow/cache 22:52:52-05/01 zebrasrv(17) [log] record 0 type XML 22:52:52-05/01 zebrasrv(17) [log] 2095 bytes: <?xml version="1.0" encoding="UTF-8"?> <record xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://w ... 22:52:52-05/01 zebrasrv(17) [log] update grs.xml <no file> 0 22:52:52-05/01 zebrasrv(17) [log] Iterations: isam/dict 8/2 22:52:52-05/01 zebrasrv(17) [log] Dict: inserts/updates/deletions: 1/0/1 22:52:52-05/01 zebrasrv(17) [log] Records: 1 i/u/d 0/1/0 22:52:52-05/01 zebrasrv(17) [request] Extended Service: Update (done) 22:52:52-05/01 zebrasrv(17) [log] function: 1 22:52:52-05/01 zebrasrv(17) [log] Waitaction: 2 22:52:52-05/01 zebrasrv(17) [log] adm request database biblios 22:52:52-05/01 zebrasrv(17) [log] adm-commit ... SUCCESS!!!!!!!!!!!!!!!!!!!! ---------------------------------------------------- roll the branch forward... $ git rebase origin/3.0.x $ ~/git/stable/misc/migration_tools/bulkmarcimport.pl -d -v -fk -n 10 -file /tmp/sample.mrc deleting biblios .......... 10 MARC records done in 0.157172918319702 seconds $ ./misc/bin/zebraqueue_daemon.pl -f ~/koha/ashs/etc/koha-conf.xml & $ sudo tail /var/log/syslog Jan 5 23:58:35 fugu Koha Zebraqueue [27085]: Starting Zebraqueue log at Mon Jan 5 23:58:35 2009 Jan 5 23:58:35 fugu Koha Zebraqueue [27085]: Mon Jan 5 23:58:35 2009 POE Session Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: 10 operations waiting to be run Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: Executing zebra operations Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 10 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 9 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 8 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 7 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 6 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 5 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 4 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 3 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 2 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 1 is malformed: Entity: line 1: parser error : Invalid XML encoding name FAIL !!!!!!!!!!!!!!!!!!!! any ideas, can anyone else replicate this, or confirm otherwise? Cheers, Mason

3 3

Re: [Koha-devel] [Koha] Issues while installig Koha 3.00 on redhat 5.0 linux
by Rick Welykochy 13 Jan '09

13 Jan '09

Mason James wrote: > On 2009/01/13, at 6:24 PM, Uma Mukkamala wrote: > >> I am not able to install CPAN also. Basically i run my internet on >> proxy i am giving the proxy details while installing the CPAN, but >> i have been structed at the following point >> >> Select your continent (or several nearby continents) [] 4 >> invalid items entered, try again >> >> i have entered both values like 'Asia' and 1 but i am not going >> forward from this point. Please suggest. > > > try this > > http://sial.org/howto/perl/life-with-cpan/ This quote from the above article is mainly for Koha developers: "Perl modules used in production must be saved locally, either under version control, a package system, or software depot. Doing so ensures the modules can be installed on new systems, or rebuilt on new platforms. This supports reproducible module installs over time, as CPAN modules may change or be removed without warning." i.e. CPAN is a network of perl modules, subject to change at any time. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services All truth passes through three stages. First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident. -- Arthur Schopenhauer

2 1