- Koha-bugs - lists.koha-community.org

[Bug 1038] searching is broken in HEAD
by bugzilla-daemon＠wilbur.katipo.co.nz 11 Dec '05

11 Dec '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1038 ------- Additional Comments From jmf(a)kados.org 2005-12-11 19:19 ------- well, add a my to $classlist just to get past it (that var doesn't appear anywhere else in the script ... anyway, now I've got another prob: QUERY : @attr 1=1016 "cryptonomicon" at /usr/local/koha/intranet/modules/C4/SearchMarc.pm line 251. Can't call method "size" on an undefined value at /usr/local/koha/intranet/modules/C4/SearchMarc.pm line 258. [Sun Dec 11 01:15:30 2005] [error] [client 70.106.173.194] Premature end of script headers: /usr/local/koha/opac/cgi-bin/opac-search.pl the Zebra log has: 01:15:30-11/12 [session] Connect from tcp:127.0.0.1 01:15:30-11/12 zebrasrv(2) [session] Starting session 2 from tcp:127.0.0.1 (pid=5584) 01:15:30-11/12 zebrasrv(2) [log] User perm for perm.anonymous: r 01:15:30-11/12 zebrasrv(2) [request] Auth none 01:15:30-11/12 zebrasrv(2) [request] Init OK - ID:Mike Taylor (id=169) Name:Net::Z3950.pm (Perl) Version:0.44 01:15:30-11/12 zebrasrv(2) [log] ResultSet 'default' 01:15:30-11/12 zebrasrv(2) [log][app2] zebra_register_open rw = 0 useshadow=0 p=0x80babe8,n=,rp=(none) 01:15:30-11/12 zebrasrv(2) [log] profilePath=.:/usr/local/share/idzebra/tab/ cwd=/build/koha/misc/zebra/usmarc 01:15:30-11/12 zebrasrv(2) [log] 0 keys, 0 sysnos, rank 01:15:30-11/12 zebrasrv(2) [log] term="cryptonomicon" nn=0 type=void count=0 01:15:30-11/12 zebrasrv(2) [log] user/system: 0/0 01:15:30-11/12 zebrasrv(2) [request] Search ERROR 109 default 1+0 RPN: @attrset Bib-1 @attr 1=1016 cryptonomicon 01:15:30-11/12 zebrasrv(2) [session] Connection closed by client 01:15:30-11/12 zebrasrv(2) [log][app2] zebra_register_close p=0x80babe8 I'm guessing a problem with the query string perhaps ... ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1038] New: searching is broken in HEAD
by bugzilla-daemon＠wilbur.katipo.co.nz 11 Dec '05

11 Dec '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1038 Summary: searching is broken in HEAD Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P2 Component: OPAC AssignedTo: chris(a)katipo.co.nz ReportedBy: jmf(a)kados.org QAContact: koha-bugs(a)nongnu.org after an OPAC search: Global symbol "$classlist" requires explicit package name at /usr/local/koha/opac/cgi-bin/opac-search.pl line 411. Execution of /usr/local/koha/opac/cgi-bin/opac-search.pl aborted due to compilation errors. [Sun Dec 11 01:06:14 2005] [error] [client 70.106.173.194] Premature end of script headers: /usr/local/koha/opac/cgi-bin/opac-search.pl ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1036] Control of MARC subfield repeatability
by bugzilla-daemon＠wilbur.katipo.co.nz 07 Dec '05

07 Dec '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1036 ------- Additional Comments From henridamien(a)koha-fr.org 2005-12-07 22:53 ------- Yes. And this is logical. If a tag is repeatable, when repeating, you will duplicate the tag structure, with subfields. 701 Author linked with Authorities... Repeatable 701$9 Not repeatable : Koha Authid 701$a SurName 701$b FirstName 701$c Titles 701$d date It is normal, when duplicating 701 to duplicate 701$9 ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1036] New: Control of MARC subfield repeatability
by bugzilla-daemon＠wilbur.katipo.co.nz 07 Dec '05

07 Dec '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1036 Summary: Control of MARC subfield repeatability Product: Koha Version: 2.2.0 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: major Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: carolcool01(a)yahoo.com QAContact: koha-bugs(a)nongnu.org When a tag is repeated, all the subfields will be duplicated even though the indicator for some subfields is set to be unrepeatable. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1035] New: MARC Subfield
by bugzilla-daemon＠wilbur.katipo.co.nz 01 Dec '05

01 Dec '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1035 Summary: MARC Subfield Product: Koha Version: 2.2.0 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: MARC AssignedTo: paul.poulain(a)free.fr ReportedBy: carolcool01(a)yahoo.com QAContact: koha-bugs(a)nongnu.org Windows version of Koha 2.2.4 does not allow for edit of subfield under MARC structure. When I click on edit, a error message pops up that says Web server error. Hope this will be fixed in the next release. Thanks. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From acquisitions module, i can give book barre code i want. When i use catalog module i find my book but with another number (notice#) so i can loan it with the barre code i have entered from the acquisitions level. regards Serge ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From Stephen >>>> Paul, you are correct, most of these problems (I now get 88) are duplicate barcodes from the old system. (A few are new staff errors that have resulted in duplicate barcodes.) These all seem to have two entries in the marc_subfield_table, with two separate bibid numbers, and only one entry in the items table. My first thought is to delete all of these from the catalog and start over. (We'll still need to delete from the MARC tables manually in mysql, but in this case that would be a good idea.) Here's the question -- will that fix the problem? Remember that we first noticed this when trying to edit new items, and our edits were attached to records in the items table that had completely different barcode numbers. (Most of these duplicate barcodes are only off by a digit or two.) And the barcodes we had the problem with are not in the list of duplicates. So are we looking at two separate problems? How would these duplicate barcodes affect editing a newly entered barcode that is not a duplicate? Can you come up with a logical explanation? (Good luck!) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From Stephen again >>> Owen and I did some testing of the item editing problem I reported (bug 599) using the default templates, with inconsistent results. We were able to reproduce the error sometimes, but not every time. So now, I think it would be valuable to take a closer look at what actually happened when we first noticed the error to see if this is a database problem or a code problem. First, remember that the problem started when staff had added an item to an existing biblio record without a barcode, and then edited that item to add the barcode. The barcode was 31000000109284. After the edit, this barcode appeared correctly when searching the MARC database (bibid 130229), but was attached to the wrong biblio (number 37717) in the old Koha DB. (At this point in the database, the bibid and the biblionumber are the same.) So here's the bibid/biblionumber 37717 from the MARC database: mysql> select * from marc_subfield_table where bibid=37717; 29 rows in set (0.02 sec) And here's bibid/biblionumber 37717 from the items table: mysql> select * from items where biblionumber=37717; 3 rows in set (0.00 sec) Notice that it look like the edited barcode (31000000109284) replaced barcode 37000000025523 that appears in the MARC record. But also notice that the MARC record has an accession date (tag 952v) attached to barcode 37000000025523 that is actually the date when the edit to barcode 31000000109284 was done! It should actually have no accession date, because no date was in the imported MARC record loaded on September 1. So what happened to barcode 37000000025523 in the old Koha DB?: mysql> select * from items where barcode='37000000025523'; Empty set (0.00 sec) It's gone, been replaced by the edited barcode number. Here's the edited barcode number in the MARC table: mysql> select * from marc_subfield_table where subfieldvalue='31000000109284'; 1 row in set (0.02 sec) mysql> select * from marc_subfield_table where bibid=130229; 31 rows in set (0.03 sec) So what happened here? It looks like the editing process saved the barcode to the correct item ('A') in the MARC table, but also saved the accession date to an item ('B') attached to a completely different bibid in the MARC table. And it also looks like the barcode and date for item A overwrote the information for item B stored in the old Koha DB. So if that is what happened, why did it happen? (Does the tag and subfield order in bibid 130229 look odd to you?) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From Roger Horne by email: I suggest a very simple change to the installer: put the MySQL Password into a loop. Does anyone remember all their passwords? Entering the wrong one in this field and finding the installer dies is a bit annoying (since many files will have been installed, which tends to cause difficulties with the next attempt). Adding "Wrong, try again" would make things much easier. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From an email to koha-devel by Chris Michalak: the bug is in OLDnewbiblio in Biblio.pm at line 1459 (version 2.0.0pre5) To fix, replace : $sth->execute($bibnum,$biblio->{'title'},$biblio->{'author'},$biblio->{'copyright'},$series,$biblio->{'seriestitle'},$biblio->{'notes'},$biblio->{'abstract'}); with : $sth->execute($bibnum,$biblio->{'title'},$biblio->{'author'},$biblio->{'copyrightdate'},$series,$biblio->{'seriestitle'},$biblio->{'notes'},$biblio->{'abstract'}); ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From koha-devel on 12 Dec: > Have I set something up wrong, or does the breeding farm only match on > the first given ISBN? Is that fixable? yes, you're right. Should be fixable by duplicating an entry when we have more than 1 ISBN. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From Ph. Revault: 2- I confirm that all datas from the biblio and bibliotitem tables are not exported (in test with my personal datas at least) . As i said in my previous message, datas like additional authors, subject, subtitle, date, etc. are not. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From the add biblio link in the middle of the homepage. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1034] New: The loan status of an item should be shown on MARCdetail.pl as it is on detail.pl
by bugzilla-daemon＠wilbur.katipo.co.nz 30 Nov '05

30 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1034 Summary: The loan status of an item should be shown on MARCdetail.pl as it is on detail.pl Product: Koha Version: 2.2.0 Platform: PC OS/Version: Linux - Redhat Status: NEW Severity: normal Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: smachefert(a)laposte.net QAContact: koha-bugs(a)nongnu.org When an item is on loan and you look at its biblio, in normal view, it is shown that item is on loan but in Marc view, it is just written "Empruntable". ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1033] New: Please update koha.org with new Mailing list info
by bugzilla-daemon＠wilbur.katipo.co.nz 30 Nov '05

30 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1033 Summary: Please update koha.org with new Mailing list info Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P2 Component: www.koha.org AssignedTo: mike(a)dragon-is.co.nz ReportedBy: jferraro(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)nongnu.org Please update koha.org with new mailing list info that reflects our move to savannah. This info can be found here: https://savannah.nongnu.org/mail/?group=koha Thanks ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

Your PayPal Account Could Be Suspended
by PayPal 29 Nov '05

29 Nov '05

1 0

[Bug 1032] New: Please Ignore ... Testing New List Again
by bugzilla-daemon＠wilbur.katipo.co.nz 23 Nov '05

23 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1032 Summary: Please Ignore ... Testing New List Again Product: Koha Version: CVS Platform: Macintosh OS/Version: Mac System 8.5 Status: NEW Severity: normal Priority: P2 Component: bugs.koha.org AssignedTo: chris(a)katipo.co.nz ReportedBy: jferraro(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)nongnu.org Please Ignore ... Testing New List ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1031] New: Please Ignore ... Testing New List
by bugzilla-daemon＠wilbur.katipo.co.nz 23 Nov '05

23 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1031 Summary: Please Ignore ... Testing New List Product: Koha Version: CVS Platform: Macintosh OS/Version: Mac System 8.5 Status: NEW Severity: normal Priority: P2 Component: bugs.koha.org AssignedTo: chris(a)katipo.co.nz ReportedBy: jferraro(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)nongnu.org Please Ignore ... Testing New List ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0