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

[Bug 6589] New: can't add supplements
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '11

16 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6589 Bug #: 6589 Summary: can't add supplements Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When trying to add a supplement I get this error: Software error: mismatched tag at line 7, column 2, byte 273 at /usr/lib/perl5/XML/Parser.pm line 187 -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 10

[Bug 6031] New: koha-rebuild-zebra doesn't allow XML and verbose indexing
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '11

15 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6031 Bug #: 6031 Summary: koha-rebuild-zebra doesn't allow XML and verbose indexing Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org XML is often a bit more robust than regular usmarc processing, so the script should have the option to use that for biblios. Also, it should be able to make things verbose. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 9

[Bug 6915] New: koha_perl_deps.pl truncates long module names at 26 chars
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '11

15 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6915 Bug #: 6915 Summary: koha_perl_deps.pl truncates long module names at 26 chars Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Installation and upgrade (command-line installer) AssignedTo: gmcharlt(a)gmail.com ReportedBy: gbarniskis(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org koha_perl_deps.pl doesn't correctly report module names longer than 26 characters, truncating (at least) CGI::Session::Driver::memcached, CGI::Session::Serialize::yaml and MARC::Crosswalk::DublinCore. Test: perl koha_perl_deps.pl -a reports full module names? Proposed fix: modify the report's format statement and surrounding header and footer prints, which apply generally too much white space. A better fix might make the whole thing more flexible than fixed width columns. Patch coming as soon as git config stops hating on me. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 9

[Bug 4959] New: language inconsistencies in baskets
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '11

13 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4959 Summary: language inconsistencies in baskets Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When closing a basket it asks if you want to create a purchase order and then it takes you the basket grouping page. I think that to be consistent, basket grouping language needs to be changed to say purchase order anywhere that the 'basket group' language appears. A basket group can be only 1 basket - but a purchase order can contain 1 or more baskets - also this seems to be the language that the librarians I talked to use the most consistently. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 32

[Bug 5774] New: XISBN default set wrong in new installs
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '11

13 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5774 Bug #: 5774 Summary: XISBN default set wrong in new installs Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com I just did a fresh install and the default value for XISBN is still 499, but the description accurately says that the limit is 999 - so the default value should be updated on new installs. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 3

[Bug 6912] New: OPAC display crashes for analytical biblio with 008 field
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '11

13 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6912 Bug #: 6912 Summary: OPAC display crashes for analytical biblio with 008 field Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: frederic(a)tamil.fr QAContact: koha-bugs(a)lists.koha-community.org If CoinS is enabled, OPAC display crashes when displaying analytical biblio records which have not 008 field. To test: - Create a analytical biblio record (leader pos 6 = 'a'), without 008 field - In OPAC, display this biblio -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 15

[Bug 5213] New: Suffix number sequence not resetting properly in hmyymmincr barcode autogen pattern
by bugzilla-daemon＠bugs.koha-community.org 12 Oct '11

12 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5213 Summary: Suffix number sequence not resetting properly in hmyymmincr barcode autogen pattern Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: cnighswonger(a)foundations.edu QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 Two things are happening. First, the SELECT does not account for a branchcode greater than 2 chars. This is fixed by just selecting the final four digits representing the incremental suffix from the barcode field. Second, the incremental suffix (4 digits) is not rolling back over to zero when reaching 9999. This pattern probably needs help. It should allow for cataloging of 10000 items per month as is. I would not recommend doing barcode numbering this way, but need to support it since it is in use in at least one library. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 8

[Bug 5379] New: import_borrowers.pl fails with db insert/update errors
by bugzilla-daemon＠bugs.koha-community.org 12 Oct '11

12 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5379 Summary: import_borrowers.pl fails with db insert/update errors Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: cnighswonger(a)foundations.edu QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 I'm not sure what is going on here exactly; the gonenoaddress, lost, debarred, guarantorid, and flags db fields default to NULL, but for some reason when the insert/update occurs, DBD returns an error like "Incorrect integer value: '' for column 'foo'..." It appears save to default these to zero for now. This patch also adds more logging of errors and a notice to the user to check the logs for errors when they occur. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 23

[Bug 5407] New: Koha displays series entries in the order they're in the MARC
by bugzilla-daemon＠bugs.koha-community.org 11 Oct '11

11 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5407 Summary: Koha displays series entries in the order they're in the MARC Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2751 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2751 Explanatory picture For the 490 MARC field, the 'a' is the series statement and 'v' is the volume number. When displaying details on a biblio, Koha will display any fields in 490 in the order they are in the MARC file, rather than being smarter and making sure 'a' comes before 'v'. See the screenshot. This applies to the XSLT and non-XSLT views, in both the OPAC and the staff client. Note that the link creation only applies to the 'a' field, so it's not causing breakage. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 4

[Bug 6371] New: Item Types description not properly displayed if not pure ASCII
by bugzilla-daemon＠bugs.koha-community.org 11 Oct '11

11 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6371 Bug #: 6371 Summary: Item Types description not properly displayed if not pure ASCII Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: frederic(a)tamil.fr QAContact: koha-bugs(a)lists.koha-community.org In several places, C4::ItemType module is used to retrieve item types and their description. If the description text contains non-ASCII characters, those characters are not properly displayed. This bug can be seen in: - 4xx plugin of a UNIMARC DB - Home > Admin > Item circulation alerts - others?... And you need to have at least one item type description containing non ASCII characters. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 15