- Koha - lists.katipo.co.nz

TLC - collection management software
by jeff haskell 22 Oct '18

22 Oct '18

Hi All, Are there any librarians or techies on this list using TLC as their collection management software? Thank you. J.

1 0

Unable to enter Data in 100$a
by takan bhatt 22 Oct '18

22 Oct '18

Sir/Madam Currently I am using Koha 18.05 in Ubuntu 16.04. I have imported data and successfully running. Now, I got new books for that I have to enter data. But field no 100$a is locked, it went to authority. How to solve this problem? Kindly Guide me. Rajesh Bhatt GRIMS, MBA College, VAPI India +919824925609 (whatsapp)

3 2

software error when user not superlibrarian tries to find a patron
by Carolina Andreu 22 Oct '18

22 Oct '18

Hello Koha community, We've found that when a librarian has some permissions (catalog + borrowers) but not superlibrarian and syspref IndependenBranches is turned on, we get a software error when this user not superlibrarian tries to find a patron within the patrons module: Can't call method "branchcode" on an undefined value at /home/www/our_koha/intranet/cgi-bin/members/member.pl line 56. Still, this user is able to find the same patron searched before if cardnumber or borrowernumber is used instead of name. We're working on Koha 17.11 + Debian 8. Has someone experienced this behavior and could give any clue? Should we report this as a bug? Thanks in advance!

1 0

Regarding the error in KOHA server migration
by Rejeesh K.Nair 22 Oct '18

22 Oct '18

Hi All, I am trying to migrate our KOHA version 16.05.04.000 to another server with KOHA environment from our live server. In order to, I have moved files into second server and create a database and import the data. But when load the website shows the below error. *Software error:Access denied for user 'root'@'localhost' (using password: YES) at /usr/share/koha/lib/C4/Context.pm line 785.BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 92.Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl <http://opac-main.pl> line 23.BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl <http://opac-main.pl> line 23.* To solve this issue, I have execute the following query for getting the privileges for database permissions *GRANT ALL PRIVILEGES ON <db_name>.* TO <db_user>; FLUSH PRIVILEGES;* But the same error occurred. Can someone help me to solve this? Thanks & Regards, Rejeesh K.Nair Mob: +91 (0) 9495316906 Web: www.rejeeshknair.com Facebook <https://www.facebook.com/rejeeshnairk>|LinkedIn <http://in.linkedin.com/in/rejeeshknair>|Twitter <http://www.twitter.com/rejeeshknair>

2 3

Re: [Koha] Customizing Koha facets
by Indranil Das Gupta 22 Oct '18

22 Oct '18

Thanks Bharat! Perhaps my question was not clear enough to you. It is not about adding authors to marc21 framework. Rather it is about changing how the facets loop code work in Koha at present. Regards -idg On Mon 22 Oct, 2018, 6:59 AM Bharat Chaudhari, <openbharat(a)gmail.com> wrote: > The details for adding other corporate body author is given in marc21 form > your just refer and configure. That would be proper > > Bharat > > On 22-Oct-2018 4:22 AM, "Indranil Das Gupta" <indradg(a)l2c2.co.in> wrote: > >> Dear colleagues, >> >> Recently I've been playing around with movie related metadata. One of the >> challenges I now face is that of search facets. For MARC21, Koha combines >> 100a, 110a, 700a as the "Author" facet. In my data, I've defined their >> role >> / relator term (700$e) as "Film producer" / "Art director" / >> "Cinematographer"/ "Actor" etc. >> >> Is there a way to segment the data into similar facets based on their >> relator code / term? Short of re-writing the getFacets sub-routine in >> lib/C4/Koha.pm after creating custom idx in Zebra? >> >> Does that even sound feasible? I could sure use some clue here :-) >> >> TIA >> >> indranil >> >> >> Indranil Das Gupta >> L2C2 Technologies >> >> Phone : +91-98300-20971 >> WWW : http://www.l2c2.co.in >> Blog : http://blog.l2c2.co.in >> IRC : indradg on irc://irc.freenode.net >> Twitter : indradg >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha >> >

1 0

Customizing Koha facets
by Indranil Das Gupta 22 Oct '18

22 Oct '18

Dear colleagues, Recently I've been playing around with movie related metadata. One of the challenges I now face is that of search facets. For MARC21, Koha combines 100a, 110a, 700a as the "Author" facet. In my data, I've defined their role / relator term (700$e) as "Film producer" / "Art director" / "Cinematographer"/ "Actor" etc. Is there a way to segment the data into similar facets based on their relator code / term? Short of re-writing the getFacets sub-routine in lib/C4/Koha.pm after creating custom idx in Zebra? Does that even sound feasible? I could sure use some clue here :-) TIA indranil Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

1 0

Install goes fine, but I can only access maintenance mode
by Ronald Vyhmeister 20 Oct '18

20 Oct '18

I completed the install of Koha (followed https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages) In order to get to Koha I had to also run this: sudo a2dissite 000-default or I would get the apache page… But now, with or without the –intra suffix, it send me straight to the maintenance page… Any ideas? Thanks in advance! Ron ----------------------------------------------------------------------------------------- Ronald Vyhmeister, PhD Academic Dean IT Manager Middle East University Beirut, Lebanon ronald.vyhmeister(a)meu.edu.lb Mobile:+961-81767015 Technology is dominated by two kinds of people: Those who manage what they do not understand and those who understand that which they do not manage.

2 5

TMP directory configuration
by Przemek Kosiński 19 Oct '18

19 Oct '18

Hi, In Koha 18.05.04.000 in menu About Koha - tab System Information I hava a message: XML configuration file Warning You are missing the <tmp_path> entry in your koha-conf.xml file. Please add it, pointing to the configured temporary directory for your Koha instance. The effective temporary directory is '/tmp'. But I already set this entry in koha xml file <template_cache_dir>/tmp/biblio-mian</template_cache_dir> Memcached also running Memcached: Servers: 127.0.0.1:11211 | Namespace: koha_biblio-main | Status: running. | Config read from: koha-conf.xml Koha version: 18.05.04.000 OS version ('uname -a'): Linux bandicoot 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 Perl interpreter: /usr/bin/perl Perl version: 5.026001 Perl @INC: /usr/share/koha/lib /usr/share/koha/installer /usr/share/koha/lib/installer /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base /var/lib/koha/biblio-main/plugins MySQL version: mysql Ver 15.1 Distrib 10.1.34-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 Apache version: Server version: Apache/2.4.29 (Ubuntu) PSGI: Plack (deployment) Memcached: Servers: 127.0.0.1:11211 | Namespace: koha_biblio-main | Status: running. | Config read from: koha-conf.xml Zebra version: Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. SHA1 ID: c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU Date and time: 19/10/2018 09:47 Time zone: Used: Europe/Warsaw | Config: Undefined | Environment (TZ): Undefined Regards, Przemek Kosiński -- ************************************************* Powiatowa i Miejska Biblioteka Publiczna w Skarżysku-Kamiennej www: www.biblioteka24.eu mail: p.kosinski(a)biblioteka24.eu *************************************************

2 1

Server biblios z39.50 show record with see from autrority
by kamil 18 Oct '18

18 Oct '18

Helo, server z39.50 (biblios) strangely works, when downloading record also shows me information from the "see form" authority with ind1 = z. I have set IncludeSeeFromInSearches to ON but I thought it works only in search OPAC and STAFF. It is bug or I have a wrong config (public server z39.50)? Koha ver. 16.0503000 Thanks a lot Regards Kamil -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html

3 5

Authorities tag 000 (leader) position 9
by João Pinto 18 Oct '18

18 Oct '18

Hi everyone, Does anyone using UNIMARC, have some problem with postition 9 of the tag 000 (leader) The position 9, it's the field that defines the type of authority, for example if it is a subject the letter changes to "j", if it a name chages to "a" etc. According the ifla manual for UNIMARC. I think that in MARC21 this definition is in tag 008. Thank's -- João Pinto [joao.pinto(a)ua.pt] _____________________________________ STIC - Serviços de Tecnologias de Informação e Comunicação [http://www.ua.pt/stic] aSGI-APA – Área de Sistemas de Informação - Área de Plataformas Abertas Universidade de Aveiro Campus Universitário Santiago 3810-193 AVEIRO Suporte Técnico: stic-helpdesk(a)ua.pt / Telf: +351 234 370099 / Ext: 22299 Geral/Administrativo: stic(a)ua.pt / Telf: +351 234 372469 / FAX: +351 234 370214 / Ext: 22250 Linked in - pt.linkedin.com/in/jacfp/ _____________________________________ Aviso de Confidencialidade/ Confidentiality Notice Esta mensagem, e os ficheiros eventualmente anexos, é confidencial e reservada apenas ao conhecimento da(s) pessoa(s) nela indicada(s) como destinatária(s). Se não é o seu destinatário, ou se lhe foi enviada por erro, não faça qualquer uso do respectivo conteúdo e proceda à sua destruição, notificando o remetente. This message, and the existing attached files, is confidential and intended exclusively for the individual(s) named as addressees. If you are not the intended recipient, or if it was sent to you by error, you are kindly requested not to make any use of its contents and to proceed to the destruction of the message, thereby notifying the sender.

1 0