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

[Bug 4925] New: Remove Smithsonian as a delivered z39.50 target
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '15

25 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4925 Summary: Remove Smithsonian as a delivered z39.50 target Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Z39.50 / SRU / OpenSearch Servers AssignedTo: gmcharlt(a)gmail.com ReportedBy: jwagner(a)ptfs.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 I propose to remove Smithsonian Institution as a delivered sample z39.50 target for several reasons. Its collection would seem to be of limited utility for most libraries. Also, and more important, I spent a long time working with them on search problems a while back. Something has changed on their server which seems to require particular search attributes to be sent as part of the search. As it stands now in Koha, only a raw (keyword) search and an author search will produce any results. A title search fails unless it's the full, exact title -- no partial entries. ISBN/ISSN, subject headings, LC call number, and other searches all fail even if a known entry is sent. Koha is using title attr 1=4 for all z39.50 title search, as near as I can tell, and Smithsonian says they're set to use 44. Similar for subject -- Koha is set to 21 and Smithsonian is using 121. A manual yaz z39.50 search specifying the right attributes does work on Smithsonian, but changing them would screw up other z39.50 searches that are now working properly. Any objections to just removing Smithsonian from the list? -- 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

[Bug 5515] New: Leading 'and' in search never returns a result
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '15

14 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5515 Summary: Leading 'and' in search never returns a result Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: bob-ewart(a)bobsown.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Searching on "and the band played on" returns no results. There are 3 biblios for that title, a book, a DVD and a video. The error log shows: [Thu Dec 16 17:18:27 2010] [error] [client 127.0.0.2] [Thu Dec 16 17:18:27 2010] search.pl: WARNING: query problem with kw,wrdl,rtrn=and band played ZOOM error 10014 "CCL parsing error" (addinfo: "Search word expected") from diag-set 'ZOOM' at /usr/share/koha/lib/C4/Search.pm line 346., referer: http://127.0.0.2:8080/cgi-bin/koha/mainpage.pl This happens with Koha 3.02.01 on openSUSE 11.3 (32-bit and 64-bit) and on Debian squeeze/sid (64-bit) with zebra. Searching on 'the band played on' gets all three records. -- 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 5711] New: Distinction between authors/additional authors in opac normal view (MARC21/XSLT)
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5711 Summary: Distinction between authors/additional authors in opac normal view (MARC21/XSLT) Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The patch for bug 5701 put the additional authors with their relator codes on their own line in the staff client and we should do the same in the OPAC. I suggest a further break out that looks like this: Author: Editor: Illustrator: Translator: Additional Authors: Otherwise the editor or translator will appear as an author and that's confusing I think to the patrons. Relator Codes here: http://www.loc.gov/marc/relators/relaterm.html -- 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 5533] New: marking item lost diff in two places
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '15

10 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5533 Summary: marking item lost diff in two places Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 Please see this screencast for details: http://screencast.com/t/6CJlMGQn2r42 Basically if you mark an item lost via edit items there is one behavior and if you mark it lost via the items tab there is another behavior. I think that the behavior that happens on the items tab is what we want (marking the item lost charges the patron the replacement fee). -- 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 49

[Bug 5025] New: discrepancy between opac doc-head-open.inc and staff doc-head-open.inc
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '15

09 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5025 Summary: discrepancy between opac doc-head-open.inc and staff doc-head-open.inc Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: gmcharlt(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The OPAC version includes a starting <title> tag, the intranet version does not. Hardly earth-shattering, but if there's no reason for the difference, reconciling them would might be a nice activity for a rainy day when there are no more important bugs to fix. -- 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 24

[Bug 6324] New: The upload directory (public) is not writable by the webserver.
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '15

30 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6324 Bug #: 6324 Summary: The upload directory (public) is not writable by the webserver. Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All URL: http://wiki.koha-community.org/wiki/Special:Upload OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Websites, Mailing Lists, etc AssignedTo: wizzyrea(a)gmail.com ReportedBy: mjr(a)ttllp.co.uk QAContact: koha-bugs(a)lists.koha-community.org Attempting to upload any file to the wiki produces the red error message "The upload directory (public) is not writable by the webserver." -- 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 5362] New: Simple (non-MARC) cataloging interface
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '15

20 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5362 Summary: Simple (non-MARC) cataloging interface Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: koha(a)cpbibliography.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 We would like to add a simple (non-MARC) cataloging interface back into Koha. The interface is described in more detail in the RFC on the wiki at http://wiki.koha-community.org/wiki/Simple_cataloging_interface -- 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 6515] New: can't set advanced notice days
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6515 Bug #: 6515 Summary: can't set advanced notice days Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org The Advance Notice 'Days in advance' selector shows a 0 even after choosing another value. If I edit this region and choose to be notified 10 days in advance and save, this value reverts back to 0. I tested this on master as of this morning - and am kind of hoping it's just a template issue. -- 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 6

[Bug 6344] New: Hold priority displayed incorrectly when "Toggle Lowest Priority" option is used
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6344 Bug #: 6344 Summary: Hold priority displayed incorrectly when "Toggle Lowest Priority" option is used Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Hold requests AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com If I toggle the lowest priority on a hold to "pin" it to the bottom of a hold's priority list, any holds I place after that will be displayed as being of lower priority. 1. Place a hold. 2. Set that hold to "lowest priority." 3. Place another hold. This hold will appear below the first. Running build_holds_queue.pl does not affect the appearance of the priorities. Only after one of the holds has been fulfilled will the priorities display correctly. 4. Check in a copy of the on-hold title. 5. The item will be allocated for the correct patron (not the one "pinned" to the bottom of the list." 6. Confirm. Now the hold list will appear correctly: The "pinned" hold will appear at the bottom. -- 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 2

[Bug 5985] New: Incorrect date in budgets and failed to edit funds children
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5985 Bug #: 5985 Summary: Incorrect date in budgets and failed to edit funds children Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nunyo(a)masmedios.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 3496 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3496 Image There are various problems: 1. When you create a budget, you can set an end date prior to the start date. 2. I can´t create funds children greater than the fund, but I can edit the children and make them bigger than the fund. 3. I can cut the fund budget but is lower than that of a child. After this, I can increase the child budget even above the total budget. And then I can also create new children over the fund budget but not above the total budget. -- 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 5