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

[Bug 29419] New: suggest for purchase clears itemtype if bib exists
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '22

20 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29419 Bug ID: 29419 Summary: suggest for purchase clears itemtype if bib exists Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org >From the Submit a New Purchase Suggestion function, if the system recognizes the title in one way or another, the system will give the patron the message s message before proceeding with the purchase suggestion: A similar document already exists. Click on confirm your suggestion to ignore this message. At this point, the (document)item type has gone back to, "None." If the patron scrolls down and clicks on "Confirm your suggestion" anyways, and doesn't change the item type a second time, then this is where the system allows for the suggestion to be submitted without the item type. The item type needs to be retained. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 17703] New: Add ISSN column in serials claims table - fix
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '22

20 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17703 Bug ID: 17703 Summary: Add ISSN column in serials claims table - fix Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Bug 11861 added ISSN column in serials claims table, in a SQL query in C4::Serials::GetLateOrMissingIssues(). But this SQL query is in a if condition, the same change must be done in the else case. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 22308] New: spaces are not filtered when searching by issn in Serials module
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '22

20 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22308 Bug ID: 22308 Summary: spaces are not filtered when searching by issn in Serials module Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- In the Serials page, when you search by issn, it's frequent to get the issn by an initial copy-paste motion. It also frequent to pick a trailing space in the copy without paying attention to. Problem, the spaces (trailing or leading) are not filtered by the search, so you get no results. The search by issn should remove these spaces. Olivier Crouzet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29014] New: Unable to use full fledged Regular Expression with capture groups and repalce capability in MARC Modification Template Action Builder.
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '22

20 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29014 Bug ID: 29014 Summary: Unable to use full fledged Regular Expression with capture groups and repalce capability in MARC Modification Template Action Builder. Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: rajujogi.t(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The RegEx used in MARC Modification Template Action Builder does merely help to replace the value copied into a field/subfield from another MARK field/subfield with some text (user specified). It also allows to add some prefixes or suffixes to the value. However, it is not possible to replace the value with first few characters of the value. It is also not possible to change the case to UPPER or LOWER case. For this to work RegEx should allow for using capture groups and replacing the value with the captured part of the value. For converting to upper or lower case it should also allow for using utility modifiers such as \U (UPPER entire), \L (lower entire), \u (UPPER first character), \l (lower first character). For example if we want to copy only the first 3 characters from the author (100$a) subfield into Dewey (082$b) subfield and convert the case to UPPER case, we should be able to specify RegEx like this 's/^([a-z]{3}]).*$/\U$1/ig' and get the job done. Intended result of applying this MARC modification template to a biblio record : MARC Modification Template Action: copy first 100$a to 082$b and replace the value with RegEx: 's/^([a-z]{3}]).*$/\U$1/ig' Record before applying : 100$a - Akbar 082$b - some entry already existing or empty Record after applying modification template: 100$a - Akbar 082$b - AKB -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 27771] New: ES: The parameter include_type_name should be explicitly specified in put mapping requests to prepare for 7.0.
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27771 Bug ID: 27771 Summary: ES: The parameter include_type_name should be explicitly specified in put mapping requests to prepare for 7.0. 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] [types removal] The parameter include_type_name should be explicitly specified in put mapping requests to prepare for 7.0. In 7.0 include_type_name will default to 'false', and requests are expected to omit the type name in mapping definitions. - In request: {body => {data => {properties => {itemnumber => {type => "integer"},sortablenumber => {type => "integer"},sortablenumber__sort => {type => "integer"},subject => {type => "text"},title => {type => "text"},title__sort => {type => "text"}}}},ignore => [],method => "PUT",mime_type => "application/json",path => "/koha_kohadev_mydb/_mapping/data",qs => {},serialize => "std"} -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 28405] New: Add author info to the holds page (reserve/request.pl)
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28405 Bug ID: 28405 Summary: Add author info to the holds page (reserve/request.pl) Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org Currently if you are placing a hold on a record in the staff client and want to double-check the author of the title, you have to click off to another page. It would be helpful to have the author information below the title information as it is on other pages. Currently, author information is already present on the "Checkout history" page (catalogue/issuehistory.pl) and the "Items" page (catalogue/moredetail.pl) so it would add some consistency to have it also present on the "Holds" page (reserve/request.pl). -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 26704] New: Koha::Item store triggers should utilise Koha::Object::Messages for message passing
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26704 Bug ID: 26704 Summary: Koha::Item store triggers should utilise Koha::Object::Messages for message passing 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 During work on bug 18501 we introduced a way to pass back status information from the trigger action in the Koha::Item object. We have since formalised such a procedure with the introduction of Koha::Object::Messages in bug 26555. We should migrate the custom implementation found in Koha::Item to use the formalised version from bug 26555. This would also include the enhancements to he message passing that were added in bug 23091. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 26257] New: Move translatable strings out of subscription-add.tt and into subscription-add.js
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26257 Bug ID: 26257 Summary: Move translatable strings out of subscription-add.tt and into subscription-add.js Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr, testopia(a)bugs.koha-community.org Depends on: 21156 Strings defined for translation in subscription-add.tt can now be wrapped in the new translation function and put in subscription-add.js. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21156 [Bug 21156] Internationalization: plural forms, context, and more for JS files -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 28993] New: Switch magnifying class in staff detail pages to FA icon
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28993 Bug ID: 28993 Summary: Switch magnifying class in staff detail pages to FA icon Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It appears that bug 13327 switched the magnifying class shown on authority links in the OPAC detail pages to a FA icon. It would be nice to make the same change to the staff detail pages. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 23291] New: Allow selecting patrons by smsalertnumber in batch patron modification
by bugzilla-daemon＠bugs.koha-community.org 17 Feb '22

17 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23291 Bug ID: 23291 Summary: Allow selecting patrons by smsalertnumber in batch patron modification 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: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Use case: When SMS messages from Koha fail at the SMS gateway layer and a library receives the list of failed SMS messages in an SMS gateway report they may wish to restrict patrons by their smsalertnumbers so that they are prompted to correct their smsalertnumber. This patch would add a new file upload and text input to the Batch patron modification tool. The user will be able to upload a file of sms numbers (one per line) as they currently can with cardnumbers. Similarly, they will be able to paste in a list of smsnumbers into the text input area (one per line) as they can currently with cardnumbers. If a matching smsalertnumber cannot be found then the sms will be skipped. Once the list of patrons is returned building on the functionality added in Bug 13552 the librarian will be able to place restrictions on a batch of patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53