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

[Bug 4955] New: adding to basket with no item throws error
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '11

27 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4955 Summary: adding to basket with no item throws error Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: cgi-bin/koha/acqui/addorder.pl 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 Estimated Hours: 0.0 When I am adding items to the basket and ignore the 'add item' form (filling in no values) I get the following error when I click 'save' -------------- Software error: :7: parser error : Opening and ending tag mismatch: record line 6 and datafield </datafield> ^ :8: parser error : Opening and ending tag mismatch: collection line 2 and record </record> ^ :9: parser error : Extra content at the end of the document </collection> ^ at /usr/lib/perl5/XML/LibXML/SAX/Parser.pm line 31 For help, please send mail to the webmaster (staff(a)bywatersolutions.com) giving this error message and the time and date of the error. -------------- The item is added to my basket despite this error though. -- 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 7

[Bug 7072] New: Use MARCAuthorityControlField008 to generate default 008 fields in AddAuthority
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '11

27 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7072 Bug #: 7072 Summary: Use MARCAuthorityControlField008 to generate default 008 fields in AddAuthority Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: fcapovilla(a)live.ca QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Created attachment 6012 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=6012 Use MARCAuthorityControlField008 in AddAuthority for empty 008s The old default value for field 008 in AddAuthority didn't have the correct length, which could potentially cause data corruptions. Since the MARCAuthorityControlField008 preference was recently added in BUG4839, I think it would be a good idea to also use it in AddAuthority for authorities without 008 MARC fields. Patch attached. -- 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 7

[Bug 6880] New: Reason for suggestions do not save
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '11

27 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6880 Bug #: 6880 Summary: Reason for suggestions do not save 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: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org On master you can add a reason for suggestion in OPAC and in acquisitions when creating a suggestion. This value is not saved into the database. -- 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 6198] New: Use 001 (not biblionumber) as record identifier for OAI-PMH
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '11

27 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6198 Bug #: 6198 Summary: Use 001 (not biblionumber) as record identifier for OAI-PMH Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Z39.50 / SRU / OpenSearch Servers AssignedTo: gmcharlt(a)gmail.com ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org With the OAI-PMH:archiveID syspref it is possible to decide what the first part of Koha's OAI-PMH identifiers should look like. The last part, however, is always the biblionumber of the record. In some settings this might work just fine, but in other settings there might be an identifier in MARC field 001 (at least for MARC21 and NORMARC, not sure about UNIMARC) that would make more sense as an identifier for OAI-PMH records. Two possibilities: - Create a syspref that lets a library choose whether to use biblionumber or 001 as identifier for OAI-PMH (this would make it possible to have something specific in 001, but still use biblionumbers for OAI-PMH if the library so wishes) - Change Koha to always use 001 as the (last part of the) identifier for OAI-PMH. (This way, if alibrary needs to have something specific in 001 they can, but that will also automatically be used for the OAI-PMH identifier. There should be an easy way to make sure 001 is always equal to the biblionumber for libraries that do not need to use 001 for something specific). Thoughts? -- 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 7159] New: Add branchcode to circulation.pl search
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '11

22 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7159 Bug #: 7159 Summary: Add branchcode to circulation.pl search Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com It would be nice to see the branchcode in the patron search results on circulation.pl. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 10

[Bug 7152] New: Koha should make it easy for librarians to attach covers using Open Library
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '11

22 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7152 Bug #: 7152 Summary: Koha should make it easy for librarians to attach covers using Open Library Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: robin(a)catalyst.net.nz QAContact: ian.walls(a)bywatersolutions.com While currently Koha can fetch covers from Open Library, it doesn't make it easy for them to be added. We should have adding the OL covers be part of the cataloguing process. This would also extend to writing the OLID into records, probably using 035. This will require a field with a prefix to be defined by OL. See http://www.loc.gov/marc/organizations/ for info on this. This will require two APIs to be defined by OL: a search-or-create interface that will find an ID for the current record if it can, and if not, it will create one; and a cover uploader interface that will allow us to upload a cover given an OLID. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 23

[Bug 7216] New: koha-restore doesn't set HOME
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '11

20 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7216 Bug #: 7216 Summary: koha-restore doesn't set HOME Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: jcamins(a)cpbibliography.com QAContact: ian.walls(a)bywatersolutions.com The koha-restore utility does not properly set the HOME directory for the system users it creates, resulting in problems with rebuild-zebra not cleaning up after itself. The koha-restore utility should set the HOME directory for the system users to match where it is putting the data (/var/lib/koha/$name) -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 9

[Bug 6929] New: koha-stop-zebra falls over if a zebra process isn't running
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '11

20 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6929 Bug #: 6929 Summary: koha-stop-zebra falls over if a zebra process isn't running Classification: Unclassified Change sponsored?: --- Product: Koha Version: master 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 If you have many instances, and one of them doesn't have a zebra process, /etc/init.d/koha-common stop will fail to stop the reset as soon as it sees one of these. -- 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 12

[Bug 6997] New: koha-remove leaves system in inconsistent state if there is an error
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '11

20 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6997 Bug #: 6997 Summary: koha-remove leaves system in inconsistent state if there is an error Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Packaging AssignedTo: jcamins(a)cpbibliography.com ReportedBy: jcamins(a)cpbibliography.com QAContact: koha-bugs(a)lists.koha-community.org If you accidentally delete one of the site configuration files (for example, the Apache conf file) for an instance, then run koha-remove to finish the removal process, the script will die when it tries to rm the nonexistent file, leaving any steps after that in the removal process undone. -- 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 6786] New: False detection of index names in Search; make index names case insensitive
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '11

18 Dec '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6786 Bug #: 6786 Summary: False detection of index names in Search; make index names case insensitive Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: ASSIGNED Severity: minor Priority: PATCH-Sent Component: Searching AssignedTo: m.de.rooy(a)rijksmuseum.nl ReportedBy: m.de.rooy(a)rijksmuseum.nl QAContact: koha-bugs(a)lists.koha-community.org An erroneous regex in Search.pm makes that some search expressions are marked ccl= queries while they do not contain an index name. Note that these queries contain a : or = (Users should not enter them if they do not intend to use indexes, but unfortunately they do.) Example: opac-search.pl?q=rembrandt+%3A contains the index name "an" (for authority); this search results in an 500 error. opac-search.pl?q=hals+%3A does not contain an index name and gives results opac-search.pl?q=vermeer+%3A does not contain an index name and gives results A tiny adjustment in the regex and a change in the loop structure makes the code slightly faster and solves the false index detections. While doing that, I included a comparison with lowercase. This makes index names in searches case insensitive. -- 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 19