March 2015 - Koha-bugs - lists.koha-community.org

[Bug 5560] New: pagination option for lists
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5560 Summary: pagination option for lists Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Virtual Shelves AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Right now lists show 20 items per page and this is not changeable. I would like to see an option at list creation that lets me say how many items I want to show per page. -- 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 12759] New: Add ability to pass list contents to batch item modification/deletion tools
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12759 Bug ID: 12759 Summary: Add ability to pass list contents to batch item modification/deletion tools Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be a great timesaver if the records associated with a particular list can be passed into the Batch item modification and batch item deletion tools. At the moment I have to run a report to extract the item barcode numbers from the list then open the resulting spreadsheet and copy & paste these into the batch modification tool. Ideally the batch modification/deletion tools need another input option to choose a particular list (that you can access), or alternatively have a new option in the list view screen to pass selected records to batch modification/deletion. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 12904] New: Force browser to load new javascript files after upgrade
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12904 Bug ID: 12904 Summary: Force browser to load new javascript files after upgrade Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement 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 A common issue with Koha seems to be that the web browsers continue to use cached js files after an upgrade. If we append the version as a parameter, we can force the browser to update the javascript files. -- You are receiving this mail because: You are watching all bug changes.

1 44

[Bug 11626] New: Cannot receive serial issues after subscription expiry date
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11626 Bug ID: 11626 Summary: Cannot receive serial issues after subscription expiry date Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Some of our serials subscriptions were not renewed after 31/12/2013 but I cannot receive any of the outstanding 2013 issues unless I renew the subscription record (a couple of publishers are about 3 months late with their printing/postage schedules compared to the subscription/cover dates). For a couple of these titles we do not have a 2014 subscription so it is not appropriate to renew the subscription record. We should still be able to receive late issues after the subscription expiry date (the date published for these issues would in most cases be on or before the expiry date) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 13665] New: Retrieve facets from zebra is slow
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13665 Bug ID: 13665 Summary: Retrieve facets from zebra is slow Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 11232 With a 1 million biblio records installation (MARC21 + DOM), a search is very slow if facets are retrieved from zebra. Debugging, I found where the processing time is spent: In C4::Search::_get_facet_from_result_set, the line my $facet = $rs->record( 0 )->raw; can spent up to 3 seconds! Actually it's the ->record call, not the ->raw. In ZOOM->record, the time is spent in my $_rec = Net::Z3950::ZOOM::resultset_record($this->_rs(), $which); I stopped the track game at this point. So for instance, with a facet holdingbranch, (FacetMaxCount set to 20) the element zebra::facet::su-to:0:20" is set, $rs->size returns 962076, and the total execution time for _get_facet_from_result_set (only for this facet!) is 3.2sec. If I set FacetMaxCount to 1, I got: 0.3 sec, for 10: 1.67. So quite linear. Lets compare with yaz-client: Z> open unix:/home/koha/var/run/zebradb/bibliosocket Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 81 Name : Zebra Information Server/GFS/YAZ Version: 4.2.30 98864b44c654645bc16b2c54f822dc2e45a93031 Options: search present delSet triggerResourceCtrl scan sort extendedServices namedResultSets Elapsed: 0.009150 Z> base biblios Z> format xml Z> elem zebra::facet::holdingbranch:0:20 Z> f d Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 809470, setno 1 SearchResult-1: term=d cnt=809470 records returned: 0 Elapsed: 0.078905 Z> s 1+1 Sent presentRequest (1+1). Records: 1 Record type: XML <record xmlns="http://www.indexdata.com/zebra/"> <facet type="0" index="holdingbranch"> <term coccur="941" occur="103144">br1</term> [...] </facet> </record> nextResultSetPosition = 2 Elapsed: 1.393694 To compare with the old facet method, I calculated the time spend in C4::Search::GetFacets (for 20 facets): >From zebra (new): 9.3sec >From Records (old): 0.16sec (with maxRecordsForFacets = 20) >From Records (old): 1.85sec (with maxRecordsForFacets = 100) >From Records (old): 15.1sec (with maxRecordsForFacets = 1000) Note that the machine is a test machine (VE) and is quite slow. Firebug tells me that with the new method (20 facets), the total load page is ~30sec, with the old method (20 facets calculated from 20 records) is 8-9sec -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 12785] New: OPAC normal view displays unwanted ISBD punctuation
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12785 Bug ID: 12785 Summary: OPAC normal view displays unwanted ISBD punctuation Change sponsored?: --- Product: Koha Version: 3.14 Hardware: PC OS: Windows Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: pesenti411(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 30978 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=30978&action=edit Display of the punctuation in Opac normal view When displaying results in Normal view, the publisher data includes the punctuation. Could it be an error in cataloguing, or should I configure the OPAC differently? I use an image of Koha 3.14 in VIrtual Box on Windows 8.1 -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 7789] New: Add translations of item type and authorized value descriptions
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '15

24 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7789 Priority: P5 - low Change sponsored?: --- Bug ID: 7789 Assignee: frederic(a)tamil.fr Summary: Add translations of item type and authorized value descriptions QA Contact: koha.sekjal(a)gmail.com Severity: normal Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: I18N/L10N Product: Koha Created attachment 8471 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8471&action=edit Mockup of a possible implementation for Item Types Since descriptions of item types and authorized values are stored in the database, there is no way to translate them. This creates a problem if the descriptions in the database are in one language but your user has switched to another. I propose that we add a language column to the itemtypes and authorised_values tables. For existing installations the existing data would remain with an empty "language" value, and this option would be displayed by default. If a library adds a set of language-specific translations that set will be displayed when that language is chosen. I think the entry form would not require extensive updating, but the display of existing values in Administration might. I'm thinking that each language's values might be displayed in a separate tab. See the attached mockup. The tabs could be displayed based on enabled languages. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 12157] New: Batch delete for serial holdings
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '15

23 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12157 Bug ID: 12157 Summary: Batch delete for serial holdings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Request by a library: Currently we have to delete serial holdings one by one, it would be nice to be able to delete several (or many) at one time with a batch delete function for serial holdings. This would not necessarily have to delete the associated holding item, only the serial record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 13414] New: Enable right truncation with search by relevance
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '15

23 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13414 Bug ID: 13414 Summary: Enable right truncation with search by relevance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org Created attachment 34199 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=34199&action=edit Enable right truncation with search by relevance This patch slightly modifies build_weighted_query function (Search.pm) that defines the ranking levels for a search by relevance in order to make right truncation possible when QueryWeightFields syspref is activated (even ranked with little weight) it modifies the type of this syspref from boolean to choice in order to add this possiblity as a third option : Search by relevance with right truncation. Default remains Search by relevance (without truncation). -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 9768] New: Problem with grace period calculation and fine intervals >1
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '15

23 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9768 Bug ID: 9768 Summary: Problem with grace period calculation and fine intervals >1 Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With a fine interval > 1 there is currently no way to avoid a effective grace period. Fines can not start the day after the due date. Configuration: With grace period = 1 fine interval 5 (= weekly, the library is closed Sunday and Saturday) Result: The first fine ist set 7 days after the item was due. Monday, checkout Tuesday, item due Wednesday Thursday Friday Saturday, holiday Sunday, holiday Monday, Tuesday, first fine Grace period for fine intervals > 1 should describe the days between the due date and the day the first fine is set. CalcFines() in Overdues.pm: 266 my $days_minus_grace = $daystocharge - $data->{'firstremind'}; 267 if ($data->{'chargeperiod'} > 0 && $days_minus_grace > 0 ) { 268 $amount = int($daystocharge / $data->{'chargeperiod'}) * $data->{'fine'}; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10