- Koha - lists.katipo.co.nz

Re: [Koha] OPAC templates question
by Doug Dearden 21 Jan '09

21 Jan '09

>>> Sharon Moreland <smoreland(a)nekls.org> 1/20/2009 2:50 PM >>> Hi, Let me preface by saying that our local template wizard (Liz) is off today and I'm anxious for an answer...so I thought I'd ask the list. In Koha 3 on the template koha/opac-search.pl, is there an easy way to have the $n and $p of the 245 display on the hit list? This is an issue in both the staff client and the OPAC with graphic novels, such as Naruto. Without the $p or $n showing up in the hit list, a patron or staff member can't easily determine which of the 34 volumes of Naruto they want to request. Is this a change that can be made on our local set of templates or would others in the koha community appreciate seeing the entire 245 on the opac-search and opac-detail screens? Sharon Moreland NEKLS/NExpress shared catalog www.nexpresslibrary.org _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha Sharon, I think what you are trying to do can be accomplished using the staff client and chaning the values in the 245 n and p subfields "hidden" attribute. See this page in the documentation, and read about the different values that can be used in the "hidden" attribute. https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/a…. Make sure you make the changes to the framework that is used to catalog the items in question. Best, Doug

4 3

Koha 3 Error When Trying to Access Web Installer
by Fooled One 20 Jan '09

20 Jan '09

Hello List, I have just tried installing the latest version of Koha via git following the instructions from the INSTALL.debian file. I have installed Koha successfully in the past and the only difference this time around is that this is a separate side-by-side install of Koha on the same machine (Debian Etch) as an already existing installation of Koha. My second installation seemed to go smoothly enough until I got to the web installer portion and received this error message instead of the web installer: Koha error The following fatal error has occurred: Can't locate DBI.pm in @INC (@INC contains: /usr/share/kohawarren/lib /usr/local/lib/perl5/5.10.0/i686-linux /usr/local/lib/perl5/5.10.0 /usr/local/lib/perl5/site_perl/5.10.0/i686-linux /usr/local/lib/perl5/site_perl/5.10.0 .) at /usr/share/kohawarren/lib/C4/Context.pm line 84. BEGIN failed--compilation aborted at /usr/share/kohawarren/lib/C4/Context.pm line 84. Compilation failed in require at /usr/share/kohawarren/lib/C4/Output.pm line 30. BEGIN failed--compilation aborted at /usr/share/kohawarren/lib/C4/Output.pm line 30. Compilation failed in require at /usr/share/kohawarren/intranet/cgi-bin/mainpage.pl line 22. BEGIN failed--compilation aborted at /usr/share/kohawarren/intranet/cgi-bin/mainpage.pl line 22. I did do a search before posting to this list and did see someone else had a similar error involving mysql, but I am not sure that this is the same type of problem. Would someone mind leading me in the right direction to fix this? Thanks! (Debian Etch, MySql v. 5.0.32)

3 3

Scanner info
by Abdul Javid 20 Jan '09

20 Jan '09

Hi Am working on library setup for non profit community center library Does koha has ability to work with bard code scanner. If so can you let me know what scanner are compatible Am running Koha 2x on linux. thanks Javid

2 1

OPAC templates question
by Sharon Moreland 20 Jan '09

20 Jan '09

Hi, Let me preface by saying that our local template wizard (Liz) is off today and I'm anxious for an answer...so I thought I'd ask the list. In Koha 3 on the template koha/opac-search.pl, is there an easy way to have the $n and $p of the 245 display on the hit list? This is an issue in both the staff client and the OPAC with graphic novels, such as Naruto. Without the $p or $n showing up in the hit list, a patron or staff member can't easily determine which of the 34 volumes of Naruto they want to request. Is this a change that can be made on our local set of templates or would others in the koha community appreciate seeing the entire 245 on the opac-search and opac-detail screens? Sharon Moreland NEKLS/NExpress shared catalog www.nexpresslibrary.org

1 0

z39.50 import - mismatched fields?
by Paul Fisher 20 Jan '09

20 Jan '09

I'm now having some problems with z39.50 import -- it seems that the import is populating the wrong fields. If I import ISBN 0471735574 from the LOC, it puts one of the authors (Montgomery, Douglas C.) into the "General Processing Data" field and puts "Includes index." into the Uniform Title, and there's no actual title ("Engineering Statistics") anywhere. That and there's a "(*) Nom de institution à laquelle s'applique cette zone" which I have no idea what that is, but it's mandatory. The error message I get when I try to save an imported record is: > Can't save this record because the following field aren't filled : > > * tag 200 subfield 5 (*) Nom de institution in tab 2 > * tag 200 subfield a Title Proper in tab 2 > * tag 200 subfield e Other Title Informatio in tab 2 > * tag 210 subfield b Address of Publisher, in tab 2 > * tag 606 subfield a Entry Element in tab 6 > * tag 610 subfield a Subject Term in tab 6 Thanks in advance (again). Paul Fisher

1 1

tag 090
by Didac Grau 20 Jan '09

20 Jan '09

Hi, I'm using koha 2.2.9 on windows. With "bullmarcimport.pl" process i try to load records from iso2709 file. These records has an 090 tag. Is it possible to load keeping 090 tag? Thanks you very much in advance. Didac Grau Sanvisen Dpt. Desenvolupament dgrau(a)ilertec.com Ilertec Consultoria Tecnològica, sll Pl. Sant Joan 23, 4-A 25007 Lleida Tel: 973 232 051 Fax: 973 225 630 http://www.ilertec.com <http://www.ilertec.com> AVÍS LEGAL: La informació adjunta és CONFIDENCIAL, sent per a l'ús exclusiu del destinatari del missatge. Si llegiu aquest missatge i no sou el destinatari assenyalat, l'empleat o l'agent responsable d'entregar el missatge al destinatari, l'informem que és totalment prohibit qualsevol divulgació, distribució o reproducció d'aquesta comunicació. Si heu rebut aquesta comunicació per error, si us plau notifiqueu-ho de forma immediata al remitent i esborreu el missatge junt amb les seus fitxers annexos. El correu electrònic via Internet no permet assegurar la confidencialitat o correcta recepció dels missatges, i és per això que ILERTEC CONSULTORIA TECNOLÒGICA, SLL no assumeix cap tipus de responsabilitat pels danys ocasionats. Si en qualsevol moment voleu modificar la seva decisió de no rebre informació comercial d'ILERTEC CONSULTORIA TECNOLÒGICA, SLL a través del correu electrònic comuniqueu-ho a ILERTEC CONSULTORIA TECNOLÒGICA, SLL a la següent adreça: Pl. Sant Joan 23, 4-A 25007-Lleida. Si voleu expressar-nos algun dubte o pregunta sobre aquest assumpte, us demanem que us poseu en contacte amb nosaltres al telèfon 973 232 051, donant referència al assumpte "Protecció de Dades". Si voleu fer ús dels drets d'accés, rectificació o cancel·lació que us concedeix la Llei Orgànica 15/1999, comuniqueu-ho a ILERTEC CONSULTORIA TECNOLÒGICA, SLL a la següent adreça: Pl. Sant Joan 23, 4-A 25007-Lleida. AVISO LEGAL: La información adjunta es CONFIDENCIAL , siendo para el uso exclusivo del destinatario arriba mencionado. Si Ud. lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, le informamos que está totalmente prohibida cualquier divulgación, distribución o reproducción de esta comunicación. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente y borre el mensaje junto con sus ficheros anexos. El correo electrónico vía Internet no permite asegurar la confidencialidad o correcta recepción de los mensajes, por lo que ILERTEC CONSULTORIA TECNOLÒGICA, SLL. no asume responsabilidad alguna por los daños causados. Si en cualquier momento Ud. desea modificar su decisión de no recibir información comercial de ILERTEC CONSULTORIA TECNOLÒGICA, SLL. a través de correo electrónico. comuníquelo a ILERTEC CONSULTORIA TECNOLÒGICA, SLL. en la siguiente dirección: Pl. Sant Joan 23, 4-A 25007-Lleida. Si nos quiere expresar alguna duda o pregunta sobre este asunto, rogamos contacte con nosotros en el teléfono 973 232 051, refiriéndose al asunto "Protección de Datos". Si desea ejercitar los derechos de acceso, rectificación o cancelación que le concede la Ley Orgánica 15/1999, comuníquelo a ILERTEC CONSULTORIA TECNOLÒGICA, SLL. en la siguiente dirección: Pl. Sant Joan 23, 4-A 25007-Lleida. P Abans d'imprimir aquest e-mail penseu bé si és necessari fer-ho: El medi ambient es cosa de tots.

1 0

‡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/

1 0

failed file
by Carmel Young 20 Jan '09

20 Jan '09

Koha 3.0.0 on debian Have tried to recover this file using Arnand's advice, but to no result. Hi, Anand, Tried what you said, i.e removing the koha symlink from /etc/apache2/sites-available/ & /etc/apache2/sites-enabled/ but this did not achieve anything. I got the following message: koha:~# rm /etc/apache2/sites-available/koha rm: cannot remove `/etc/apache2/sites-available/koha': No such file or directory koha:~# rm /etc/apache2/sites-enabled/koha rm: cannot remove `/etc/apache2/sites-enabled/koha': No such file or directory koha:~# You said to tell you how we went; sorry we weren't successful. The problem is that when we try to start up the system we get the message that says we have a failed file. "Syntax error on > line 668 of etc/apache2/sites-enabled/ > koha-httpd.conf: No such file or directory". Jesse asked us what is on line 668. How do we find this out??? Carmel Young Catholic Universtiy of Malawi. Carmel

2 1

Re: [Koha] Label Printing
by Jeffrey LePage 19 Jan '09

19 Jan '09

I don't think you have to panic yet. As for your decision to use Koha, I think it was the right decision. All software has bugs, but at least with open source you have the opportunity to fix what's broken. Koha also seems to have a very lively and helpful community. Back to the bug: As I understand it, this feature was in an earlier version and was taken out for 3.x. I believe they intend to put it back, just as soon as they figure out how to get it to work with 3.x. If you have luck with the patch, please let us all know. In the meantime, you can tell your librarians what I tell mine: It's broken now, but it will be fixed. In the meantime I'll create batches of labels for you. Because it's open source I'm able to access the database, apply patches quickly, etc. Others on the list may be more helpful. I'm just a newbie myself, so you should wait for other voices before you decide on a course of action. -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html --- On Mon, 1/19/09, Bill Graham <grahamcw(a)hurleybulldogs.com> wrote: > From: Bill Graham <grahamcw(a)hurleybulldogs.com> > Subject: Re: [Koha] Label Printing > To: "Jeffrey LePage" <jeffrey_lepage(a)yahoo.com> > Date: Monday, January 19, 2009, 2:55 PM > Thanks for the reply > > This is a major problem for me then. > My Koha machine is running in aDMZ and doesn't have a > keyboard or mouse let alone KDE or a user interface. I > suppose I could build a KDE environment but my users will > struggle with that - and I will still have to do the export. > I don't get it - this seems like a pretty important of > a library system - at least my two librarians sure think so. > I hope I haven't led them down the wrong path with Koha > - I am just a computer backroom guy - and know little about > library systems. > > Thanks for the input > > Bill > > > > Quoting Jeffrey LePage <jeffrey_lepage(a)yahoo.com>: > > > There is a patch for this feature > (http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=commit;h=990e315471c8c79959…) > but I was unable to get this to work. Maybe someone else > had better luck? > > > > I was able to create a batch on the backend, via > mysql. The relevant table is 'labels'. However, I > hardly think that this is a solution, and I certainly > wouldn't recommend it unless you know what you're > doing. > > > > Another solution I'm looking into is to ignore > Koha's label facility and instead use kbarcode. > Kbarcode is a KDE application that can connect to a mysql > database and create a variety of labels. Beware: there > seems to be some sort of bug that causes kbarcode to crash > when libpostscriptbarcode is installed. I havn't had a > chance to attempt this fix yet, so I can't guarantee > results. The solution is supposedly to de-install > libpostscriptbarcode. The basic problem is that there are > two xml files: > > 1) /usr/share/libpostscriptbarcode/rules.xml > > 2) /usr/share/apps/kbarcode/rules.xml > > ... and you must have only the 2nd file > (/usr/share/apps/kbarcode/rules.xml). > > > > > > > > > > > > -- > > Please avoid sending me Word or PowerPoint > attachments. > > See > http://www.gnu.org/philosophy/no-word-attachments.html > > > > > > --- On Mon, 1/19/09, Bill Graham > <grahamcw(a)hurleybulldogs.com> wrote: > > > >> From: Bill Graham > <grahamcw(a)hurleybulldogs.com> > >> Subject: [Koha] Label Printing > >> To: "list, koha" > <koha(a)lists.katipo.co.nz> > >> Date: Monday, January 19, 2009, 12:50 PM > >> Hello > >> > >> We are starting to use Koha to replace a very old > DOS based > >> catalog. We are entering all inventory as we weed > the > >> library. We are to the point that we would like to > start > >> printing labels - both spine and barcode. > >> The problem is there doesn't seem to be a way > to select > >> large groups of items. The 3.01 Documentation > shows > >> selection criterea that would allow large batches > to be > >> built. But the current version does not have this > >> implemented. Is that correct ? > >> If that is the case - what are you users doing to > produce > >> these labels ? > >> > >> thanks > >> --Bill Graham > >> Systems Administrator > >> Viborg Public Library > >> Viborg,SD 57070 > >> > >> > >> > >> > ---------------------------------------------------------------- > >> This electronic mail sent from Hurley Public > Schools - > >> Hurley, South Dakota http://www.hurleybulldogs.com > >> > >> NOTICE: This E-mail (including attachments) is > confidential > >> and may be legally privileged. If you are not the > intended > >> recipient, you are hereby notified that any > retention, > >> dissemination, distribution, or copying of this > >> communication is strictly prohibited. Please reply > to the > >> sender that you have received the message in > error, then > >> delete it. Thank you. > >> > >> _______________________________________________ > >> Koha mailing list > >> Koha(a)lists.katipo.co.nz > >> http://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > > > > > ---------------------------------------------------------------- > This electronic mail sent from Hurley Public Schools - > Hurley, South Dakota http://www.hurleybulldogs.com > > NOTICE: This E-mail (including attachments) is confidential > and may be legally privileged. If you are not the intended > recipient, you are hereby notified that any retention, > dissemination, distribution, or copying of this > communication is strictly prohibited. Please reply to the > sender that you have received the message in error, then > delete it. Thank you.

1 0

item call number woes
by Huck 19 Jan '09

19 Jan '09

itemcallnumber: I've set the appropriate Cataloguing -> System Pref to map to 924k where they were stored on the 2.xx system that these MARC records were imported from... do I need to run the 'rebuild_nozebra.pl' script again? I read on the wiki(pasted below)...the changes to Koha 3...but while it points out the changes..it doesn't really suggest a fix...unless the 'plugin marc21_callnumber.pl' is the fix..and if so..there is no link to it..and it is not found in the build directory for koha or the installation directories.. Please advise? Thanks, --Huck from the wiki: Call Numbers in Koha 3 How Call Numbers are Handled in Koha 3 What has changed Koha 3 adds the following fields to the database (cn stands for Call Number): * biblioitems.cn_source ( auth value, CN_SOURCE, stores the source of the call number: DDC, LCC, NLM, etc.) * biblioitems.cn_class ( plugin, marc21_callnumber.pl, helps fill in the rest of the biblio-level fields) * biblioitems.cn_item * biblioitems.cn_suffix * biblioitems.cn_sort ( for zebra sorting, stored as a decimal number) * items.cn_source ( auth value, CN_SOURCE, stores DDC, LCC, NLM, etc.) * items.itemcallnumber ( plugin, marc21_itemcallnumber.pl, helps fill in the itemcallnumber based on the record data ) * items.cn_sort ( for zebra sorting, stored as a decimal number) * items.ccode ( auth value, CCODE, stores the Collection Code of the item, can be used as call number prefix by some libraries ) This scheme gives us the ability to sort by both record-level and item-level call numbers; it gives us the ability to define sources of call numbers at both record and item levels. With the new scheme, we have removed the following from the database: * items.cutterextra * biblioitems.classification * biblioitems.subclass * biblioitems.dewey * biblioitems.lcsort * biblioitems.lccn

1 1