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

[Bug 16251] New: Material type is not correctly set for Rancor 008 widget
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '19

05 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16251 Bug ID: 16251 Summary: Material type is not correctly set for Rancor 008 widget Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This should likely use the same mapping as the old widget: Field 008/18-34 Configuration If Leader/06 = a and Leader/07 = a, c, d, or m: Books If Leader/06 = a and Leader/07 = b, i, or s: Continuing Resources If Leader/06 = t: Books If Leader/06 = c, d, i, or j: Music If Leader/06 = e, or f: Maps If Leader/06 = g, k, o, or r: Visual Materials If Leader/06 = m: Computer Files If Leader/06 = p: Mixed Materials -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 19719] New: Add a ‘Collection’ column in the patron loans data table.
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '19

02 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19719 Bug ID: 19719 Summary: Add a ‘Collection’ column in the patron loans data table. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jesse(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1 - Add the Collection code (ccode) to the issues table -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 19506] New: Staged Marc Import should warn if the selected encoding does not match MARC 21 leader
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '19

23 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19506 Bug ID: 19506 Summary: Staged Marc Import should warn if the selected encoding does not match MARC 21 leader Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Mis-matches between character encodings will cause diacritics be incorrectly imported into Koha. If the imported marc record is MARC8 encoded and imported as UTF-8, diacritics will be converted to the REPLACEMENT CHARACTER '�'. A UTF-8 encoded file imported as MARC8 will try to render the multi-byte UTF-8 characters as MARC8, resulting in garbage text. MARC21 stores its encoding in leader position 09 - Character coding scheme (http://www.loc.gov/marc/bibliographic/bdleader.html) The accepted encodings are '#' for MARC8 and 'a' for UTF-8 (although Koha exports ' ' for MARC8). Koha should check the leader for MARC21 records and warn if the selected encoding does not match the encoding of the marc record, giving the user the opportunity to change the encoding or download fresh records with the correct encoding. [I couldn't tell if this was an issue for UNIMARC] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 16660] New: Elasticsearch broken if OpacSuppression is activated
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '19

17 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16660 Bug ID: 16660 Summary: Elasticsearch broken if OpacSuppression is activated Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When OpacSuppression is active, you can't search using Elasticsearch. The error shown is: Unable to perform your search. Please try again. By adding a die we coaxed it into a better error message: Can't use string ("(HASH(0xcfe2548)) not Suppress=1") as a HASH ref while "strict refs" in use at /home/katrin/kohaclone/Koha/SearchEngine/Elasticsearch/Search.pm line 99. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 16690] New: Installing DB on remote server fails without *.* permissions
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '19

17 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16690 Bug ID: 16690 Summary: Installing DB on remote server fails without *.* permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: mtompset(a)hotmail.com Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org KohaDB: 192.168.71.250 > CREATE DATABASE koha_ils; > GRANT ALL ON koha_ils.* TO 'kohauser'@'192.168.71.251' IDENTIFIED BY 'kohapass'; > FLUSH PRIVILEGES; > QUIT; KohaApp: 192.168.71.251 Do an install. Hack the kohaconf username, hostname, passwords to match. Try to run the web install steps. You will get told you don't have enough permissions. Why? Because 'hostname' is 192.168.71.250 to connect to the DB, but the app server is 192.168.71.251, and you should be checking against those GRANTS in installer/install.pl around line 116. Hacked in a <webserver> tag to the kohaconf and used that value instead in the script. Everything works. -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 20650] New: Switch single-column templates to Bootstrap grid: Various, part 3
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '19

16 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20650 Bug ID: 20650 Summary: Switch single-column templates to Bootstrap grid: Various, part 3 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 19980 This patch will convert several unrelated templates to use the Bootstrap grid: - patroncards/print.tt - patron_lists/add-modify.tt - plugins/plugins-disabled.tt - plugins/plugins-upload.tt - tools/tools-home.tt - virtualshelves/merge.tt Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19980 [Bug 19980] Omnibus: Update single-column templates to use Bootstrap grid -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 20089] New: Does Koha::Database->schema always return a connected object?
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '19

14 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20089 Bug ID: 20089 Summary: Does Koha::Database->schema always return a connected object? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org My log says no: DBD::mysql::st execute failed: MySQL server has gone away [for Statement "SELECT `me`.`variable`, `me`.`value`, `me`.`options`, `me`.`explanation`, `me`.`type` FROM `systempreferences` `me` WHERE ( `me`.`variable` = ? )" with ParamValues: 0='opacgroupresults'] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832. I see them quite often, always for preferences. Note that we do not test the cached $database->{schema} in sub schema. If we do, we will however add some time. ( 0.0043 instead of 0.0003 ) What do you think? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20270] New: SIP2 Connection Issue
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '19

09 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20270 Bug ID: 20270 Summary: SIP2 Connection Issue Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: aniltiwari86(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Created attachment 72087 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=72087&action=ed… SIP Log Hi, We have Installed Koha 17.05.06.000, and created multiple SIP users to integrate with RFID Kiosk. When we are trying to connect with one kiosk it works perfectly. If we try to connect more Kiosk the SIP2 is not responding to 93 packet. Can you please suggest what could be the issue. Regards, Anil -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 19012] New: Note additional columns that are required during patron import
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '19

06 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19012 Bug ID: 19012 Summary: Note additional columns that are required during patron import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We say 'branchcode' and 'categorycode' are required - this is true, but so are surname and cardnumber -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 20607] New: Elasticsearch - ability to add a relevancy weight in mappings.yaml file
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '19

06 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20607 Bug ID: 20607 Summary: Elasticsearch - ability to add a relevancy weight in mappings.yaml file Change sponsored?: --- Product: Koha Version: unspecified 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 The code could be able to inject mappings and weight if a mapping in mappings.yaml file contains boost-in-simple-search: Exemple: Personal-name: label: Personal-name mappings: - facet: '' marc_field: 100abcdefghjklmnopqrstvxyz marc_type: marc21 sort: ~ suggestible: '' - facet: '' marc_field: 100abcdefghjklmnopqrstvxyz marc_type: normarc sort: ~ suggestible: '' type: '' boost-in-simple-search: 4 4 is added in field weight in table search_field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26