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

[Bug 16102] New: Import batch into catalog very slow
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '19

20 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16102 Bug ID: 16102 Summary: Import batch into catalog very slow Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: tejoskumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Dear team, The batch import into catalog is very slow when compared to 3.20 version in 3.22.4. I used the same machine for the same number of records in koha 3.22 and it takes almost 8 hours to import the data for 30000 records. In 3.20 it was taking only 30 minutes to 1 hour for this activity to be completed. Using Ubuntu 14.04 and 4GB ram machine for importing the data and this is a fresh installation of ubuntu and koha. Iam not sure if this is a issue with KOHA or issue with my koha settings. I already reported in the koha mailing list for any solution to overcome the issue, but not received any response, hence posting it here. Thanks & regards Suresh Kumar -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17422] New: Holds amount per record produce error
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '19

20 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17422 Bug ID: 17422 Summary: Holds amount per record produce error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: jesse(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 56127 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=56127&action=ed… Screen shot of settings In the circulation and fines rules module, If you set Holds allowed count & Holds per record count for a circulation rule to each 999, koha will produce a template error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 17326] New: KOha not asking if the book is to be renewed when max book limit is reached
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '19

20 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17326 Bug ID: 17326 Summary: KOha not asking if the book is to be renewed when max book limit is reached Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: daltonfury42(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When I try to check out a book that I have already checked out, koha will ask me if I want to renew the book instead. But this does not work if I have already taken the maximum allowed number of books. In this scenario, I get the "Too many checked out." notification, but I think it is logical to allow renewal as it does not increase the number of books that the patron has taken. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 16292] New: Allowtoomanyoverride - Don't allow does not give any message
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '19

20 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16292 Bug ID: 16292 Summary: Allowtoomanyoverride - Don't allow does not give any message Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tejoskumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Dear team, When trying to issue more than the limit of items it stops issuing books, but the koha does not show any message/warning - this happens when Allowtoomanyoverride is Don't allow. When Allowtoomanyoverride is allow, it gives me a warning message do you wan't to override or issue. I feel system should tell that the limit reached. If this is not a system issue and I missed some system settings, please help me in setting the system preferences correctly. Iam using koha 3.22.05. Regards Suresh Kumar -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 17105] New: Do not see checkouts in the table of circulation.pl
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '19

20 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17105 Bug ID: 17105 Summary: Do not see checkouts in the table of circulation.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Saw this problem under 3.22 (but could probably have been master too): Circulation page lists a number of checkouts. But clicking Show checkouts does not list them in the table. What happened? This javascript error occurred: Sunday not defined. Comes from includes/calendar.inc. And should be a zero. (As value for the preference CalendarFirstDayOfWeek.) After toggling this preference a few times, I could not reproduce the problem anymore under 3.22 (Plack+memcache). Probably a cache problem somehow. Note that dbrev 3.21.00.015 moved the old value of Sunday to 0. Just leaving this note here some time for future troubleshooting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 19498] New: Translatability: Get rid of [% block_budget.count %] and similar
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '19

19 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19498 Bug ID: 19498 Summary: Translatability: Get rid of [% block_budget.count %] and similar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Examples: [% block_budget.count %] fund(s) are attached to this budget. [% count %] item(s) are attached to this record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 19721] New: Tabulation in the description of a patron category breaks the patron search. Cause : tabs must be escaped in JSON
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '19

19 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19721 Bug ID: 19721 Summary: Tabulation in the description of a patron category breaks the patron search. Cause: tabs must be escaped in JSON Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com === Reproduce === 1. Go to staff: /cgi-bin/koha/admin/categories.pl 2. Edit a category with existing patrons 3. Add a tab in the description here is one to copy for convenience: " " 4. Save the category 5. Go to /cgi-bin/koha/members/members-home.pl 6. Filters → Category → select the just edited one 7. Hit search, just below 8. Then you should see "Processing..." As if the request was still running forever === Cause === In the browser dev tools, we can see that the XRH request to "search" actually comes back. The response seems normal. Except that Firefox warns "SyntaxError: JSON.parse: bad control character in string literal at line 23 column 29 of the JSON data" Which points to our tab. Which invalidates the JSON: https://stackoverflow.com/questions/19799006/unable-to-parse-tab-in-json-fi… > The whitespace characters are: character tabulation (U+0009), line feed (U+000A), carriage return (U+000D), and space (U+0020). > Whitespace is not allowed within any token, except that space is allowed in strings. === Workaround === Remove the tab from the description of the category. In /cgi-bin/koha/admin/categories.pl One can use the filter in the table (called search). And search for a tab " " to get the "corrupted" ones. === Fix === It seems that we should escape the tabs (and CRs(\r) and LFs(\n)) Or just get rid of them. Another question is where? - Where the category form is processed? - early in the upper layers? (when the request just comes) - or in the lower layers? (if the category is managed by the ORM) - In the database itself with a trigger? - Other ideas? === Going further === How to find which other bugs like this one might cause hard to diagnose issues? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 19364] New: KOHA title search pulls documents with author matches
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19364 Bug ID: 19364 Summary: KOHA title search pulls documents with author matches Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: nikeshn(a)gmail.com Author results also appears when I limit my search to title only. I think it appears because KOHA indexing treats statement of responsibility as part of title. Other ILS systems pull only title matches from tag 245, 505 and 490 etc. We migrated from Millennium to KOHA and Millennium pulls only documents matches the word in title, series etc. For example : melm 245$a Title-cover:w,Title-cover:p,Title-cover:s,Title:w,Title:p,Title:s melm 245$c Author,Author-in-order:w,Author-in-order:p,Author-in-order:s melm 245$9 Cross-Reference:w,Koha-Auth-Number Here KOHA treats 245 $c (statement of responsibility ) as part of title. Live Example : I searched for Shakespeare in Title but document with Shakespeare as an Auhtor also appear in the search result. Please see the link below. https://opac.kustar.ac.ae/cgi-bin/koha/opac-search.pl?idx=ti&q=shakespeare -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 17131] New: Zebra index for Title is too broad
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17131 Bug ID: 17131 Summary: Zebra index for Title is too broad 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 54482 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=54482&action=ed… Test file One of the zebra index definitions in marc21/biblios/biblio-koha-indexdefs.xml for Title includes the entire 245 tag:  <index_data_field tag="245"> <target_index>Title:w</target_index> <target_index>Title:p</target_index> </index_data_field> Since 245$c can contain Author, this means that author names will show up in Title searches. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 20366] New: More information about orders linked to subscriptions on "Acquisition details" tab
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20366 Bug ID: 20366 Summary: More information about orders linked to subscriptions on "Acquisition details" tab Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org On the 'Acquisition detail' tab on bibliographic record, we cant' know if orders are placed on bibliographic or subscription level. It is quite complicated when several subscriptions are attached to this record to have a clear history of the acquisitions. It would be great for order managers if we could have 2 more columns on this tab, one with the 'aqorders.subsciptionid' and one with 'subscription.callnumber'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40