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

[Bug 25252] New: Add script to export bib data to CollectionHQ
by bugzilla-daemon＠bugs.koha-community.org 02 May '20

02 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25252 Bug ID: 25252 Summary: Add script to export bib data to CollectionHQ 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: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We (PTFS-Europe) have been using this script to export catalogue data to CollectionHQ for many of our customers for a long time now, and it would be very useful if it could be incorporated into the core code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 15850] New: Correct JSHint errors in cataloging.js
by bugzilla-daemon＠bugs.koha-community.org 02 May '20

02 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15850 Bug ID: 15850 Summary: Correct JSHint errors in cataloging.js Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: koha-bugs(a)lists.koha-community.org, m.de.rooy(a)rijksmuseum.nl, testopia(a)bugs.koha-community.org Following coding guideline JS8: "Follow guidelines set by JSHint," some errors should be corrected in cataloging.js koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 43, col 31, The array literal notation [] is preferable. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 49, col 72, Use '!==' to compare with ''. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 99, col 13, 'i' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 116, col 17, 'id_input' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 182, col 37, 'olddiv' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 183, col 37, 'oldcontrol' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 108, col 18, 'j' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 108, col 26, 'j' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 108, col 46, 'j' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 109, col 27, 'j' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 109, col 59, 'j' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 110, col 28, 'j' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 220, col 21, 'inputs' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 226, col 25, 'anchors' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 227, col 30, 'j' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 176, col 21, 'CloneButtonPlus' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 280, col 13, 'i' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 280, col 17, 'len' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 287, col 13, 'i' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 287, col 17, 'len' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 296, col 13, 'oldcontrol' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 315, col 21, 'i' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 409, col 15, 'line' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 425, col 34, 'line' used out of scope. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 465, col 13, 'i' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 465, col 17, 'len' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 471, col 13, 'i' is already defined. koha-tmpl/intranet-tmpl/prog/en/js/cataloging.js: line 471, col 17, 'len' is already defined. -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes.

1 13

[Bug 15794] New: Allow the use of emojis as tags on records
by bugzilla-daemon＠bugs.koha-community.org 01 May '20

01 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15794 Bug ID: 15794 Summary: Allow the use of emojis as tags on records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org A library requested the ability to add emojis in the tag field on the opac. Entering an emoji now seems to scrub it clear and leave no value in the db but still enter a new tag. Subsequent attempts warn of repeated tags. -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 25262] New: [19.05.x] Cash register report truncates manual_inv values
by bugzilla-daemon＠bugs.koha-community.org 01 May '20

01 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25262 Bug ID: 25262 Summary: [19.05.x] Cash register report truncates manual_inv values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In 19.05 we have an odd situation. Accountlines accounttype is now VARCHAR(80) In the past it was 5, so in the "Cash register" report we truncated that MANUAL_INV values in our dropdown. At the moment the DB will save a long value, but only provide the truncated values for searching, and so transactions will not show up -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 25041] New: Links to 'pending' #ASKED tab in suggestions.pl is broken
by bugzilla-daemon＠bugs.koha-community.org 01 May '20

01 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25041 Bug ID: 25041 Summary: Links to 'pending' #ASKED tab in suggestions.pl is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Add several suggestions to Koha 2 - Set them in different status, leaving at least one pending 3 - Go to home page, note it shows count of pending 4 - Click the link on home page 5 - It does not take you to correct tab #ASKED anchor for tab was removed by: commit 4494e8ba6ca7d28972fcc1161c680ecf0b091f62 BUg 23594 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 24269] New: Authority matching in Elasticsearch is broken when authority has subdivisions
by bugzilla-daemon＠bugs.koha-community.org 01 May '20

01 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24269 Bug ID: 24269 Summary: Authority matching in Elasticsearch is broken when authority has subdivisions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com In C4/Heading/MARC21.pm when we call _get_search_heading we look at the heading and turn some subfields into terms so: 150 $aChess$xOpenings becomes 'Chess generalsubdiv openings' 126 my %subdivisions = ( 127 'v' => 'formsubdiv', 128 'x' => 'generalsubdiv', 129 'y' => 'chronologicalsubdiv', 130 'z' => 'geographicsubdiv', 131 ); 267 $heading .= " $subdivisions{$code} $value"; We don't do this when indexing into ES so we will never find matches for these records -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 25331] New: Master
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '20

30 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25331 Bug ID: 25331 Summary: Master 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: zerooneindo(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 13388] Add library pages to the OPAC
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '20

30 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13388 --- Comment #10 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hm, I have another thing to add - for some hosted systems like ours the branch email is a noreply and the replyto is the library's email. It all has to do with mail servers being picky about what they think is spam... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13388] Add library pages to the OPAC
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '20

30 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13388 --- Comment #9 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think you make a good point. Could we make showing the e-mail optional or protect it in some other way? (other than mailto even?) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13388] Add library pages to the OPAC
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '20

30 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13388 --- Comment #8 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- QA topic: Is it necessary to put the email of the branch in a form directly usable by a computer? Even with metadata indicating that it's an email address: the mailto link. Even without it, a clean email address is very recognizable. Because these are publicly accessible pages and **any generic** crawler for email addresses to spam will find them. That will be a different impact than being available in the public API (the current state), since now it requires a crawler made for Koha. The thing that made me think of it: (great and not too long resource BTW) https://softwareengineering.stackexchange.com/questions/46716/what-technica… > Don't put users' email addresses in plain text as they will get spammed to death. -- You are receiving this mail because: You are watching all bug changes.

1 0