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

[Bug 29615] New: Add library pull down to simple search in the staff interface
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '22

19 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29615 Bug ID: 29615 Summary: Add library pull down to simple search in the staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This would be like OpacAddMastheadLibraryPulldown, but for the staff interface. A library pull down would display at the end of the simple search input field that allows to limit on a specific library right away. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

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

19 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 19 Feb '22

19 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 19 Feb '22

19 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 19 Feb '22

19 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 29804] New: Koha::Hold->is_pickup_location_valid explodes if empty list of pickup locations
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29804 Bug ID: 29804 Summary: Koha::Hold->is_pickup_location_valid explodes if empty list of pickup locations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Due to bug 28871, there's a problem in production when checking if a pickup location is valid using Koha::Hold->is_pickup_location_valid. I file this bug because the other one is blocked and is not clear what path it will take, but this is affecting users. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 29786] New: Holds to pull report shows incorrect item for item level holds
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29786 Bug ID: 29786 Summary: Holds to pull report shows incorrect item for item level holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 When running holds to pull it can show the wrong item for an item level hold. This is because we simply get the first barcode from the list of items that can fill the hold. The issue seems to come from 'get_items_that_can_fill' in Koha::Holds This does not take into account that an item level hold can only be filled by one item To recreate: 1 - Find a record with many items available 2 - Place an item level hold for an item on the record, not the one with lowest itemnumber 3 - Run 'Hold to pull' report 4 - Note the barcode does not match -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 29647] New: Update po files in manual repository
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29647 Bug ID: 29647 Summary: Update po files in manual repository Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: david(a)davidnind.com At the moment some of the po files in the manual repository are quite outdate compared to the po files on pootle. Before branching out the manual, could we do a general update on all po files for the manuals 21.05 and 20.11? I know it would help a lof for German, but I think doing it for all languages every half year would be good as a lot of people are not aware of the process and wouldn't ask for updating. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[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 29634] New: Map biblio.medium to 245$h by default (MARC21)
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '22

18 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29634 Bug ID: 29634 Summary: Map biblio.medium to 245$h by default (MARC21) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 11529 added a medium field in the biblio table, but it is not linked to 245$h in the default marc21 framework. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13