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

[Bug 27946] New: Add a charge per article request to patron categories configuration
by bugzilla-daemon＠bugs.koha-community.org 26 May '22

26 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27946 Bug ID: 27946 Summary: Add a charge per article request to patron categories configuration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We propose adding a charge field (scan fee) to the patron category configuration screen. Cost for Article scan request: $____ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 125

[Bug 29441] New: We should make our method returns consistent in Koha::Biblio
by bugzilla-daemon＠bugs.koha-community.org 25 May '22

25 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29441 Bug ID: 29441 Summary: We should make our method returns consistent in Koha::Biblio 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We now have a few of 'get_marc_*' accessors in Koha::Biblio, but their returns are really inconsistent. I feel like we aught to try and make them as consistent as possible so future developers can use them without having to dig through the code to see what they return. In `get_marc_notes` we return an array of note strings from the marc record.. these may be selective subfield concatenations and could be in various orders. In `get_marc_host` we return either a Koha::Biblio object or the Biblio object + the subfield g, as a string, from the current records marc21 773 field we used to find the host. In `get_marc_components` we return an array of MARCXML strings. I think we could do better here.. certainly with the `_components` and `_host` routines either consistently returning Koha::Biblio/Koha::Biblios or MARCXML string/strings for example. As for `get_marc_notes`, this is a little different.. we could possibly return an array of MARC::Field objects for later processing, or perhaps we aught to have a second naming scheme for returning strings from MARC/Metadata vs retuning a marc/metadata object/string itself? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 20608] New: Elasticsearch - relevancy weights proposition for unimarc in mappings.yaml
by bugzilla-daemon＠bugs.koha-community.org 25 May '22

25 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20608 Bug ID: 20608 Summary: Elasticsearch - relevancy weights proposition for unimarc in mappings.yaml 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 This is the mappings updated in mappings.yaml see bug 18316 for the code evolution. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 27770] New: ES: Deprecated aggregation order key [_term] used, replaced by [_key]"
by bugzilla-daemon＠bugs.koha-community.org 25 May '22

25 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27770 Bug ID: 27770 Summary: ES: Deprecated aggregation order key [_term] used, replaced by [_key]" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net Will be needed for ES 7 prove t/db_dependent/Koha/SearchEngine/Elasticsearch/Search.t [DEPRECATION] Deprecated aggregation order key [_term] used, replaced by [_key] - In request: {body => {aggregations => {subject => {terms => {field => "subject__facet",include => "[eE][aA][sS][yY].*",order => {_term => "asc"},size => 1000}}},from => 0,query => {query_string => {query => "*"}},size => 0},ignore => [],method => "GET",mime_type => "application/json",path => "/koha_kohadev_mydb/_search",qs => {},serialize => "std"} -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 30141] New: ElasticsearchCrossFields enabled returns no search results on OPAC
by bugzilla-daemon＠bugs.koha-community.org 25 May '22

25 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30141 Bug ID: 30141 Summary: ElasticsearchCrossFields enabled returns no search results on OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org ElasticsearchCrossFields is a great syspref to enable if you need to search across indexes, for example your search term includes both title and author keywords. We've discovered this only works on the staff client, and returns no results when searching on the OPAC. After some investigation, this is because the OPAC will add a `suppress:false` to the search query, to hide records that are suppressed in OPAC. I'm not sure why, but this combination of suppress:false and ElasticsearchCrossFields means no results are returned in the OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 18316] New: Add weighting/relevancy options to ElasticSearch
by bugzilla-daemon＠bugs.koha-community.org 24 May '22

24 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18316 Bug ID: 18316 Summary: Add weighting/relevancy options to ElasticSearch 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 167

[Bug 24176] New: Make datelastborrowed a configurable column in holdings_table
by bugzilla-daemon＠bugs.koha-community.org 23 May '22

23 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24176 Bug ID: 24176 Summary: Make datelastborrowed a configurable column in holdings_table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some librarians would find it hand if datelastborrowed would show in the holdings_table as a configurable column. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 29381] New: Auto-renewal digest messages are sent on every cron run
by bugzilla-daemon＠bugs.koha-community.org 23 May '22

23 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29381 Bug ID: 29381 Summary: Auto-renewal digest messages are sent on every cron run Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)iki.fi QA Contact: testopia(a)bugs.koha-community.org Depends on: 18532 If you have patrons with checkouts that have auto-renewal enabled and the patron has checked in their messaging preferences that they want auto-renewal messages as digests then they get every day / cron run a message with al list of their checkouts that has auto-renewal enabled. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18532 [Bug 18532] Messaging preferences for auto renewals -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 30222] New: Auto_renew_digest still sends every day when renewals are not allowed
by bugzilla-daemon＠bugs.koha-community.org 23 May '22

23 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30222 Bug ID: 30222 Summary: Auto_renew_digest still sends every day when renewals are not allowed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 29381 The non-digest auto-renew notice checks to see whether or not the auto-renew error on the issue has changed since the previous day. If the error is not new, the notice doesn't generate. In the auto-renew-digest, we don't do that check. For any error other than auto_too_soon, the patron will be notified every day. Bug 29381 tried to address this, but did not correct the whole issue. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29381 [Bug 29381] Auto-renewal digest messages are sent on every cron run -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 30278] New: Auto renewal should be moved to an object method
by bugzilla-daemon＠bugs.koha-community.org 23 May '22

23 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30278 Bug ID: 30278 Summary: Auto renewal should be moved to an object method 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 29381 and bug 30222 both required reviewing the conditions under which auto renewal notices are sent. It would be better if the renewals were handled by a unit tested subroutine We should have: Koha::Patron->auto_renew_checkouts Koha::Checkouts->filter_by_auto_renew->renew the renewal can report back on the status and then notify patron, depending on settings -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5