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

[Bug 8411] New: merging allows for creation of duplicate fields where not allowed
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8411 Priority: P5 - low Change sponsored?: --- Bug ID: 8411 CC: m.de.rooy(a)rijksmuseum.nl Assignee: gmcharlt(a)gmail.com Summary: merging allows for creation of duplicate fields where not allowed Severity: critical Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Cataloging Product: Koha See here : http://manual.koha-community.org/3.8/en/stafflists.html#mergebibrecs the merging bib records tool used to stop you from adding fields if they were not repeatable, but I was just able to add the two 001 fields to my destination record but the framework says it's not repeatable. For the 999 it didn't add it but didn't give me an error either. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 7571] New: Maintain exchange rate history
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7571 Bug #: 7571 Summary: Maintain exchange rate history Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha.sekjal(a)gmail.com Indian libraries need to maintain exchange rates across time. When items are invocied, sometime invoice date can be in the past, the actual cost needs to be calculated using the exchange rate as it stood on the inovice date. With this change Koha will store exchange rates for each currency along with "last update date". Invoicing and receiving pages will be changed to calculate actual cost based on exchange rates as on on invoice dates. -- 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 19

[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 12481] New: Staff client detail-view "next" link is greyed out when the last search result of any results page is clicked or navigated into
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12481 Bug ID: 12481 Summary: Staff client detail-view "next" link is greyed out when the last search result of any results page is clicked or navigated into Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: jseppal(a)student.uef.fi Reporter: jseppal(a)student.uef.fi QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)biblibre.com Blocks: 12261 When doing a staff client catalog search with more than 1 page of results and clicking the last result on any search result page, the top-left navigation button for "next" is greyed out. The expected behaviour would be to move into the next page of results. The "next" navigation should only be prevented when the very last search result is selected in the detail-view. As suggested in the linked bug 12261, this is a regression from my attempt to fix the issue with the navigation letting the user moving out of bound in relation to the result array. As suggested in bug 12261, the original cause was in part due to the total number of results not being carried in the search cookie. Secondly, the offset value that was being used in the navigation checks shouldn't be used in there (the checks for allowing movement within the results) because the cookie value is only updated upon a result click and not when the user is navigating using the detail-view. I wrongly submitted a patch to bug 12261 since it was already pushed. The patch brings the total number of search results available (as I think it was orignally planned, since the non-existing value was being used) to the browser.js which handles the navigation and makes use of that. I marked this as blocking 12261 - not sure if this is right... -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 13265] New: Still too many search cursor cookies
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13265 Bug ID: 13265 Summary: Still too many search cursor cookies Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We have multiple sites that are still exhibiting bug 11369. For whatever reason, the cookies on these sites are larger and thus the maximum of 10 is still too large. This setting should be controlled by a system preference to the number can be tailored on a per-site basis. -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 7879] New: Memoize::Memcached two times slower than it should be
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7879 Priority: P5 - low Change sponsored?: --- Bug ID: 7879 Assignee: gmcharlt(a)gmail.com Summary: Memoize::Memcached two times slower than it should be QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: dpavlin(a)rot13.org Hardware: All Status: NEW Version: rel_3_6 Component: Architecture, internals, and plumbing Product: Koha Created attachment 8791 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8791&action=edit Memoize::Memcached 2x speedup While profiling Koha with memcached turned on I was stunned by NYTProf results: Calls P F Exclus Inclus Subroutine 55 2 1 1.70s 1.70s Memoize::Memcached::EXISTS 55 2 1 1.68s 1.68s Memoize::Memcached::FETCH Code analysts showed that it generates two FETCH requests for each item. Attached patch fixes upstream module and might be beneficial on existing Koha installations which use memcached. It uses shared variable, and it's safe in CGI installations. Having shared variable showed another characteristic of current code: 55 2 1 33.8ms 33.8ms Memoize::Memcached::EXISTS 55 2 1 362µs 362µs Memoize::Memcached::FETCH This is good, but a little bit too fast. Examining hit and miss ratio stored in Koha::Persistant::stats it turns out that we are accessing memcache 106 times, but only 4 times for new values. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 12919] New: It'd be nice to be able to automate collecting all records added and deleted from the catalogue
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12919 Bug ID: 12919 Summary: It'd be nice to be able to automate collecting all records added and deleted from the catalogue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org In NZ almost all libraries participate in the National Union Catalogue, which means that libraries have to update their holdings periodically. So we created a system that runs as a cronjob and will generate a list of records added or updated in the catalogue, and a list of isbn of deleted records. These can be run as cron jobs with the output being emailed to a person or thing. Although this was initially designed to support the needs of NZ libraries, it is general enough that it can be used by anyone. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 10756] New: Carousel Display of New Titles on OPAC home page
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '15

11 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10756 Bug ID: 10756 Summary: Carousel Display of New Titles on OPAC home page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bob(a)calyx.net.au QA Contact: testopia(a)bugs.koha-community.org This feature displays recently added items to your Koha's main OPAC page, using a 'carousel' style display. This feature can be enabled/disabled via a Koha syspref, and requires memcached. This feature can be styled and configured using CSS. A demo of the feature (Koha-3.10) is available at http://demo.calyx.net.au This feature adds to Koha the ContentFlow library by JacksAsylum.eu (MIT license): http://jacksasylum.eu/ContentFlow/index.php Special thanks to Harvest Bible College, Australia for sponsoring this feature. Thanks also to Albany Senior High School,New Zealand and KohaAloha for an earlier prototype. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 13263] New: Printing Callnumber in Koha 3.16.04.000.
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '15

11 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13263 Bug ID: 13263 Summary: Printing Callnumber in Koha 3.16.04.000. Change sponsored?: --- Product: Koha Version: 3.16 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: os.jerwynfernandez(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 33610 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=33610&action=edit Wrong Callnumber Format Check the callnumber, whenever it is exported as a PDF file. Koha doesn't follow the format the way you want to print it. Character doesn't split normally and all letters are in caps. Please see attached file for reference. Thanks! -- You are receiving this mail because: You are watching all bug changes.

1 8

[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