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

[Bug 185] Barcode not auto-calculated when autobarcode is on
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Mar '03

18 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=185 paul.poulain(a)free.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From paul.poulain(a)free.fr 2003-03-18 21:39 ------- should be solvable with a specific plugin. I'll do it asap (after 1.9.1 anyway) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 181] Changing the branch code (in Edit) creates a new branch
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Mar '03

18 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=181 paul.poulain(a)free.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From paul.poulain(a)free.fr 2003-03-18 21:31 ------- fixed in cvs : was more a template problem than a perl one ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 180] Literal <br> appears in branch address
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Mar '03

18 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=180 ------- Additional Comments From paul.poulain(a)free.fr 2003-03-18 21:23 ------- seems fixed in en and fr languages. Maybe we can mark it fixed ? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 177] showmessage free does not accept empty string
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Mar '03

18 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=177 paul.poulain(a)free.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 161] buildrelease gives error messages during normal operation
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Mar '03

18 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=161 paul.poulain(a)free.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From paul.poulain(a)free.fr 2003-03-18 20:50 ------- fixed in cvs (for 1.9.1) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

MARC scheme for item data
by Larry Currie 17 Mar '03

17 Mar '03

We're getting ready to load item data from a file into our MARC records, and I proposed that the following fields be added to each MARC record: 945 b biblio.biblionumber c biblioitems.biblioitemnumber 946 a biblioitems.biblioitemnumber b biblioitems.itemtype c biblioitems.dewey and for each copy or, in the case of multivolume works, each volume, a 949 field with the following subfields: 949 a items.itemnumber b items.biblionumber c items.multivolumepart d items.biblioitemnumber e items.barcode f items.dateaccessioned g items.homebranch h items.price i items.datelast seen j items.issues k items.itemsnotes l items.holdingbranch .... .... My question is, I came upon this scheme only because it seemed to pass the Check MARC test within the MARC Related section of version 1.9.0, but is this the optimal scheme to use? I noticed that Paul Poulain has proposed that the 995 tag be used for the item data in conjunction with Biblio.pm and I can certainly make this change. Am I correct in assuming that there will be one such field for each volume and copy of a work (i.e., that the 949s or 995s will be repeatable)? What about the information I have chosen to go into 945 and 946 fields? Is this appropriate? We have also tried to get some guidance from the Library of Congress MARC specifications pages as to whether we should either 1) be creating separate MARC holdings records and/or 2) modifying the leaders of our MARC records to indicate that they contain holdings tags. I personally don't think that we have to concern ourselves with either of these specifications, but I just want to be sure. Larry Currie -- Lawrence W. Currie User Services Librarian California Academy of Sciences Golden Gate Park San Francisco, CA 94118 lcurrie(a)calacademy.org (415) 750-7108 (415) 750-7106 fax http://www.calacademy.org/research/library/

2 1

[Bug 190] No member details in reading list
by bugzilla-daemon＠wilbur.katipo.co.nz 16 Mar '03

16 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=190 mwhansen(a)hmc.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 189] Can't return to member record from reading list or pay fines
by bugzilla-daemon＠wilbur.katipo.co.nz 16 Mar '03

16 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=189 mwhansen(a)hmc.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From mwhansen(a)hmc.edu 2003-03-17 10:46 ------- Added the links back to the member record. They look like <a>Return</a> to Member Record at the bottom of the page. If anyone wants something different, feel free to change it. ;-] ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 176] showmessage yn does not accept uppercase Y or N
by bugzilla-daemon＠wilbur.katipo.co.nz 16 Mar '03

16 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=176 mwhansen(a)hmc.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From mwhansen(a)hmc.edu 2003-03-17 10:28 ------- If the caller specifies a yn response type, it is now coverted to a restrictchar ynYN . This should fix the problem with case (in)sensitivity. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 178] showmessage would not allow a default response of "0"
by bugzilla-daemon＠wilbur.katipo.co.nz 16 Mar '03

16 Mar '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=178 mwhansen(a)hmc.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From mwhansen(a)hmc.edu 2003-03-17 10:18 ------- Fixed by testing (defined($defaultresponse)) instead of ($defaultresponse). ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0