August 2019 - Koha-bugs - lists.koha-community.org

[Bug 23429] New: ilsdi.pl GetRecords documentation does not match output
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23429 Bug ID: 23429 Summary: ilsdi.pl GetRecords documentation does not match output Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: J.P.Knight(a)lboro.ac.uk QA Contact: testopia(a)bugs.koha-community.org The ILS-DI GetRecords self generated documentation no longer matches up with the output that the script generates. It probably should. :-) For example, the documentation says that the <item> element contains a <date_due> element. This was the case back in 16.x versions of Koha, but on our production 18.11.04 we no longer get this field, but we do get an <onloan> field in item instead (which luckily serves the same purpose as we need - we just need to know if each item is on loan or not). Here's the example format for the <item> part of the record generated by http://ourserver/cgi-bin/koha/ilsdi.pl?service=Describe&verb=GetRecords <items> <item> <biblioitemnumber>1</biblioitemnumber> <withdrawn>0</withdrawn> <holdingbranchname>Bibliothèque Jean Prunier</holdingbranchname> <notforloan>0</notforloan> <replacementpricedate>2008-08-20</replacementpricedate> <itemnumber>1</itemnumber> <location>Secteur Adulte</location> <itemcallnumber>R ABE</itemcallnumber> <date_due></date_due> <itemlost>0</itemlost> <datelastseen>2008-08-20</datelastseen> <homebranch>BIB</homebranch> <homebranchname>Bibliothèque Jean Prunier</homebranchname> <biblionumber>1</biblionumber> <holdingbranch>BIB</holdingbranch> <timestamp>2008-08-20 17:15:51</timestamp> <damaged>0</damaged> <cn_sort>R_ABE</cn_sort> <dateaccessioned>2008-08-20</dateaccessioned> </item> </items> And here's what we get out for an actual search: <items> <item> <onloan>2019-10-01</onloan> <holdingbranch>MAINLIB</holdingbranch> <location>MAIN</location> <datelastborrowed>2019-07-18</datelastborrowed> <biblioitemnumber>526315</biblioitemnumber> <permanent_location>MAIN</permanent_location> <datelastseen>2019-07-18</datelastseen> <withdrawn>0</withdrawn> <itype>LONG</itype> <notforloan>0</notforloan> <biblionumber>526315</biblionumber> <itemnumber>847332</itemnumber> <price>22.17</price> <dateaccessioned>2016-09-13</dateaccessioned> <issues>10</issues> <homebranchname>Main Library</homebranchname> <homebranch>MAINLIB</homebranch> <timestamp>2019-07-18 17:03:03</timestamp> <cn_sort>005_550000000000000_SPS_BRA</cn_sort> <itemlost>0</itemlost> <renewals>28</renewals> <barcode>040444587X</barcode> <damaged>0</damaged> <replacementpricedate>2018-02-01</replacementpricedate> <itemcallnumber>005.55 SPS/BRA</itemcallnumber> <holdingbranchname>Main Library</holdingbranchname> </item> </items> Note the <date_due></date_due> in the example is missing from the real output, which has <onloan>...</onloan> instead. I guess we need to decide if the documentation is just out of date with the code, or if the code should be generating things it isn't any more. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 22128] New: koha-remove fails mysql ERROR 1133 (42000) at line 2: Can't find any matching row in the user table
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22128 Bug ID: 22128 Summary: koha-remove fails mysql ERROR 1133 (42000) at line 2: Can't find any matching row in the user table Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- The script fails in in a GRANT command - the user does not exist This probably is due to changed behaviour of mysql 5.7ff From https://dev.mysql.com/doc/refman/5.7/en/grant.html#grant-overview: Note If an account named in a GRANT statement does not already exist, GRANT may create it under the conditions described later in the discussion of the NO_AUTO_CREATE_USER SQL mode. It is also possible to use GRANT to specify nonprivilege account characteristics such as whether it uses secure connections and limits on access to server resources. However, use of GRANT to create accounts or define nonprivilege characteristics is deprecated as of MySQL 5.7.6. Instead, perform these tasks using CREATE USER or ALTER USER. In my case mysql hosted a koha 16.11 database upgraded to 18.5 and the only existing user was koha_library@%. There was no user koha_library@localhost. mysql was running in the version (> 5.7)supplied with ubuntu 16.4 (Xenial). My solution to the problem was commenting out two lines in the script. diff /usr/sbin/koha-remove /usr/sbin/koha-remove_ori 71c71 < # GRANT USAGE ON \`koha_$name\`.* TO \`koha_$name\`@\`$mysql_hostname\`; --- > GRANT USAGE ON \`koha_$name\`.* TO \`koha_$name\`@\`$mysql_hostname\`; 73c73 < # DROP USER \`koha_$name\`@\`$mysql_hostname\`; --- > DROP USER \`koha_$name\`@\`$mysql_hostname\`; hhl@koha-VM-dev:~ > For a general solution the koha-remove script should be made more resilient and should not use deprecated mysql features. Since I am only very occasionally dealing with mysql and moreover I have no knowledge which user(s) have been used for koha instances in the past it is beyond my skills to define the proper revision of the script. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 20389] New: Indexing fields concatenated
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20389 Bug ID: 20389 Summary: Indexing fields concatenated Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: claire.hernandez(a)biblibre.com I would like to be able to specify multiple subfields to index as a value in a field. The subfields must be concatenated. Example 1: Author in unimarc in an authority: 700 1 $a Bermès $b Emmanuelle I could record a fields in mappings: author: "700a. .700b" I would have in the field indexed: author: "Emmanuelle Bermès" Example 2: in mappings: author: "700b., .700a" would give: author "Bermès, Emmanuelle" With solr, we managed it with indexing plugins. If it is too early for this, we could manage it in mappings configuration maybe. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 22846] New: Remove warning in the manual about needing StaticHoldsQueueWeight to use RandomizeHoldsQueueWeight
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22846 Bug ID: 22846 Summary: Remove warning in the manual about needing StaticHoldsQueueWeight to use RandomizeHoldsQueueWeight Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The paragraph in https://koha-community.org/manual/18.11/en/html/systempreferences.html#stat… saying Leaving StaticHoldsQueueWeight empty is contraindicated at this time. Doing so will cause the build_holds_queue script to ignore RandomizeHoldsQueueWeight, causing the script to request hold fulfillment not randomly, but by alphabetical order. is talking about (without mentioning it by number) bug 8562, which was fixed in bug 12803 comment 14. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 22304] New: Bugzilla blocked by UK mobile network EE
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22304 Bug ID: 22304 Summary: Bugzilla blocked by UK mobile network EE Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: Other OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: emma.perks(a)heartofengland.nhs.uk Target Milestone: --- Created attachment 84957 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=84957&action=ed… EE user screenshots - cannot connect to Bugzilla Hello, The bugs.koha-community.org website is blocked by mobile network EE in the UK. When trying to access it using 4G or mobile data provided by EE, the site is blocked due to the security certificate on Bugzilla. One person in the EE community thinks this is caused by EE not doing browser fallback. Several users have tried and all have the same problem independent of hardware. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 23055] New: Internal server error when trying to pay selected charges in fines accountant
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23055 Bug ID: 23055 Summary: Internal server error when trying to pay selected charges in fines accountant Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: costalc(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Internal server error when trying to pay fines. See file attached please. Plack log: ERROR PROCESSING TEMPLATE: undef error - : filter not found at /usr/share/koha/lib/Koha/Account.pm line 258. Tested in 19.05 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 16580] New: Explain the link between the autoBarcode preference and the cataloging plugin
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '19

02 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16580 Bug ID: 16580 Summary: Explain the link between the autoBarcode preference and the cataloging plugin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you have the 'barcode.pl' plugin enabled for the barcode field in your MARC framework, but the 'autoBarcode' preference is turned off, the plugin will appear to be active but won't do anything. I think there ought to be text explaining the connection, to be shown both on the system preference itself and when the barcode plugin is selected during framework editing. Or is there a time when one does something without the other? -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 23270] New: Auto barcodes not generated correctly when adding several items
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '19

02 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23270 Bug ID: 23270 Summary: Auto barcodes not generated correctly when adding several items Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: isabel.pineda(a)ds.edu.sv QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Auto barcodes that are generated by <branchcode>yymm0001 are not generated correctly automatically when adding several copies of a new item at once. The new items are missing the <branchcode> part. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 23401] New: Make koha-create more user friendly
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '19

02 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23401 Bug ID: 23401 Summary: Make koha-create more user friendly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net We just solved a problem on IRC where a new site was not indexing, because the records were UNIMARC and the site was MARC21, because /etc/koha/koha-sites.conf had not been edited priori to running koha-create. To avoid situations like this, we could display the config values (from /etc/koha/koha-sites.conf or another file specified with the --configfile option) that are about to be used and ask the user "does this look ok?". The configfile could have a setting to disable the question for those who are confident to avoid it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 22247] New: Koha::IssuingRule->get_effective_issuing_rule has no hard fallback
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '19

01 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22247 Bug ID: 22247 Summary: Koha::IssuingRule->get_effective_issuing_rule has no hard fallback Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- We don't yet make full use of this Koha::IssuingRule in koha, however I have now found that the get_effective_... method within it behaves differently to the some of the C4 modules which query the same table.. In C4::Circulation there is a hard coded default should the default rule not be set (*, *, *) which claims a loan of 0 days. This default either needs to be coded into get_effective_issuing_rule or a Koha::Exception thrown is such a rule is not found or something.... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3