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

duplicate items showing
by Zico 14 Jul '09

14 Jul '09

---------- Forwarded message ---------- From: Zico <mailzico(a)gmail.com> Date: Tue, Jul 14, 2009 at 8:32 PM Subject: Re: [Koha-devel] duplicate items showing To: Michael Hafen <mdhafen(a)tech.washk12.org> Now, the thing is if my team edit any bibliographic data there in koha, it shows duplicate entry and both are in edited form. If they delete one item from those duplicate, both of them are deleted. As for example: anyone wants of edit the *edition* of any book from "4th edition to 5th edition". They edited it...and after that when they searches for that book. Two copies comes in the screen. And, both of them are showing that, "the edition is 5th edition". Though, at first, there was just one entry. Now, if they wants to delete one item in order to get rid of duplication, both of them gone away!!! -- Best, Zico

2 1

Marc framework test error
by Sivasankari 14 Jul '09

14 Jul '09

hi, THis is the error while running marc framework test, how should i resolve this Thanks Sivasankari

1 0

KOHA - cataloging doubts
by Sivasankari 14 Jul '09

14 Jul '09

Hi, I have installed koha with (Unimarc). But in Admin - system preference - I have changed to MARC21 format. Will it work out. Hope the koha system is changed to adapt the MARC21 format or will it retain the unimarc format, which i gave in koha installation - perl makefile.pl in linux. I have set no zebra. since I'm not using millions of records. I'm doing a sample. How to do cataloging. How to add the books to the library. IS there any sample file provided. I'm a techie ,totally ignorant of library systems, isbn etc. I would like to add some 50 books to the library . How should i do it? Thanks in advance Sivasankari M

1 0

implementation of authorised values
by Sébastien Hinderer 13 Jul '09

13 Jul '09

Dear all, I'm wondering how occurrences of authorised values are represented in Koha's database. I'm aware of the authorised_values table, but that's not my concern here. Assume one decides to bind a Koha field to an authorised value. My question is: what will finally be stored in that field ? Will it be the primary key associated to the authorised value (id), or will it be the content of the authorised_value column ? In the latter case, if this value changes, how is it updated ? Thanks a lot for any help, Sébastien.

3 2

duplicate items showing
by Zico 13 Jul '09

13 Jul '09

Hi, if any member of my team enters one item twice... my koha accept those and when i searches for that item... it shows twice or thrice or something like these. I want to close this duplication. I want two things. 1. If anyone adds same item second time, koha will show that, "it has been already added" 2. By mistake, if it occurs.... the searching will never show one item twice. How can i do that? -- Best, Zico

2 2

Changing/Removing Default Login Username & Password in Koha3.0
by Sai bhalaji Dhinakaran 13 Jul '09

13 Jul '09

Hi, I would like to change/remove the default login user name and password in Koha3.0. I tried changing the XML file but end up in error on the page. Can someone please let me know the way it can be done. Thanks and Regards, Sai Bhalaji This email and any attachment(s) transmitted may contain confidential, proprietary or legally privileged information relating to D&B TransUnion Analytic and Decision Services Private Limited. The information is intended solely for the recipient. No part of this information may be disclosed, copied, reproduced, distributed or made available in any form whatsoever without prior authorization. If you have received this email in error please notify the sender electronically and delete all copies immediately. This email may contain viruses. D&B TransUnion Analytic and Decision Services Private Limited has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this email. We strongly advise you to ensure that the email and any attachment(s) are free of any virus.

3 4

Error in koha installation
by Sivasankari Muthuraja 11 Jul '09

11 Jul '09

Hi, I'm a newbie to koha. I tried to install koha in fedora10 linux. and had installed the koha with pre-requisites of essential perl modules,UTF-8 charset in mysql. I haven't installed Zebra, Yaz, since i'm not going to test with huge data contents. i followed INSTALL.fedora7 available in the koha-3.00.03 version tar file extracted. I couldnot understand sec 4.4 loading data for tests. Installer document says to add Listen 8080 in the etc/httpd/conf/httpd.conf file. Since Apache tomcat server is configured for 8080, i haven't added the line in the httpd.conf file. When i launch the http::<ipadress of my intranet>:80/ - I get the error mentioned below. - ==== Screen output ==== Koha error The following fatal error has occurred: Can't locate ZOOM.pm in @INC (@INC contains: /usr/share/koha/lib /usr/local/lib/perl5/site_perl/5.10.0/i386-linux-thread-multi /usr/local/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.10.0/i386-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl .) at /usr/share/koha/lib/C4/Context.pm line 85. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Context.pm line 85. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 25. Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 22. BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 22. ==== Screen output ==== Kindly help me out , what may be reason for this. Thanks in advance Sivasankari M _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

2 1

OT: Web archiver for the Koha-Patches list has "eaten" part of a post of mine
by Ricardo Dias Marques 10 Jul '09

10 Jul '09

Hi, I just noticed that the Web archiver (Pipermail) for the "Koha-Patches" mailing list has "eaten" (deleted, cropped...) part (the second "half") of a post of mine. The post has been sent through Gmail. Other web archives that also archive the "koha patches" mailing list, like Markmail - http://www.markmail.org/ - have the full post available. Compare: [Koha-patches] [PATCH] 3040 : seriestitle mistaken as collection title http://lists.koha.org/pipermail/koha-patches/2009-July/003905.html ... with: Re: [Koha-patches] [PATCH] 3040 : seriestitle mistaken as collection title - Ricardo Dias Marques - org.koha.lists.koha-patches - MarkMail http://markmail.org/message/6lfwvzmcmbqsmoz3 Any ideas for why this has happened? Thanks in advance! Cheers, Ricardo Dias Marques lists AT ricmarques DOT net Installation Guide for Installing Koha 3 on openSUSE 11 http://wiki.koha.org/doku.php?id=opensuse_11.0

2 2

information about Koha tables
by Zeno Tajoli 10 Jul '09

10 Jul '09

Hi to all, as you know I and Matteo Romanello we are working on a documentation about Mysql tables of Koha. We have problems and dubts about 3 tables: account_offsets service_throttle roadtype Could you send to the list a brief description of those three tables ? Thank you very much Bye Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

6 7

$query vs $query
by Marc Chantreux 10 Jul '09

10 Jul '09

hello koha coders, Koha naming convention drove us to a stupid bug: $query is used both for the CGI object and the SQL statements. So at the end of an hard week, we write : my $query = CGI->new; # lines of code $query = "delete * from my_brain"; # lines of code print $query->header; and try to understand why header is not a function available in the weird "delete * from my_brain" package ... so we would like to change at least one of these convention to prevent this easy error. As we are for a stronger coding style in koha, we feel that this decision must be debated with all of you. proposals: 1. Change the sql statement name a) to $statement b) to $sql c) to $smt d) to an explicit name (as $select_old_borrowers or $update_items ...) e) to your own idea 2. Change the CGI object a) to $cgi (i have no idea why ...) b) to $r (as there is a lot of perl code still using this convention) c) to $input (because a part of koha already use it) d) to your own idea 3. I don't want to change because *you* did errors ... $query is ok for me! for myself, i'm fan of 1d *and* 2a ($query is too generic and $input has no sense when i write print $input->header). regards -- Marc Chantreux BibLibre, expert en logiciels libres pour l'info-doc http://biblibre.com

7 9