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

[Bug 10950] Add preferred pronoun field to patron record
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10950 Heather <heather_hernandez(a)nps.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |heather_hernandez(a)nps.gov -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 27988] New: Record matching rule ElasticSearch broken
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27988 Bug ID: 27988 Summary: Record matching rule ElasticSearch broken Change sponsored?: --- Product: Koha Version: unspecified 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: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org Importing records using 'Record matching rule' with ElasticSearch (at least with remote ES installation) it is not working... I have not been able to test localy installed Log claims that no nodes are available, ** No nodes are available: [https://xxxxxx.xxxx:443] called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 100. at /usr/share/perl5/CGI/Compile.pm line 137. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 26592] XSS vulnerability when ysearch is used
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26592 Didier Gautheron <didier.gautheron(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |didier.gautheron(a)biblibre.c | |om --- Comment #25 from Didier Gautheron <didier.gautheron(a)biblibre.com> --- There's a fix in 20.05 git not in these patches which could be backport to 19.11: commit f67bd64dee422f380824a5520e7a383e3888da97 --- a/koha-tmpl/intranet-tmpl/prog/en/includes/js_includes.inc +++ b/koha-tmpl/intranet-tmpl/prog/en/includes/js_includes.inc @@ -103,11 +103,11 @@ var cardnumber = ""; if( item.cardnumber != "" ){ // Display card number in parentheses if it exists - cardnumber = " (" + ( item.cardnumber ? item.surname.escapeHtml() : "" ) + ") "; + cardnumber = " (" + ( item.cardnumber ? item.cardnumber.escapeHtml() : "" ) + ") "; } ie use cardnumber not surname if there's a cardnumber. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 27984] New: Add item field copynumber to holdingst in columns settings
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27984 Bug ID: 27984 Summary: Add item field copynumber to holdingst in columns settings Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, Item field "item_copynumber" is not present in columns settings (#biblio-detail) for holdingst. Could it be added? It is already available for course-items-table. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 9921] Make it possible to force 001 = biblionumber
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|In Discussion |RESOLVED CC| |nick(a)bywatersolutions.com --- Comment #74 from Nick Clemens <nick(a)bywatersolutions.com> --- There are many comments here, some about plugins as a workaround, moving to a new bug and removing the incremental option *** This bug has been marked as a duplicate of bug 27981 *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9921] Make it possible to force 001 = biblionumber
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921 --- Comment #73 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 118460 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=118460&action=e… Bug 9921: Remove option of 'incremental' and add tests -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15565] Place multiple holds at once for the same record in OPAC
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15565 --- Comment #249 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Martha Fuerst from comment #248) > I've tried testing this using the Bywater sandboxes, but I can't get the > pop-up to show up with the current test plan (step 6). When I set > maxreserves to 3, I still don't get an alert when trying to place 4 holds, > but only 3 holds are placed. I'll test this one again when I have a chance. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9921] Make it possible to force 001 = biblionumber
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=27978 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24836] New: (Optionally) Trigger MARC-Modification-Templates after record has been saved
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '21

18 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24836 Bug ID: 24836 Summary: (Optionally) Trigger MARC-Modification-Templates after record has been saved Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: simon.hohl(a)dainst.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is somewhat a followup on: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921 The solution using a Plugin for creating 001 values works, but I wondered if it could be achieved by, for example, copying over the 999c biblionumber to 001 after the record has been saved. This would basically solve the initial problem described in #9921. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 27938] New: Record the time the hold was placed
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '21

17 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27938 Bug ID: 27938 Summary: Record the time the hold was placed 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: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com At the moment, we record the time a hold was placed, but not the time. This would be useful information for libraries who have targets to supply holds within a certain number of hours from the moment the hold was placed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4