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

[Bug 20913] New: allow multiple if/unless statements in MARC modification template actions by adding AND/OR qualifiers
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20913 Bug ID: 20913 Summary: allow multiple if/unless statements in MARC modification template actions by adding AND/OR qualifiers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org Actions in MARC Modification templates have the following syntax: [action] all/first [field] (plus optionally... if/unless [field] [conditional]) But there is only the option for one if/unless. This is usually enough, but sometimes it would be useful to be able to add another qualifier linked with and/or. For example, libraries importing embedded items might want to apply a different shelf location or call number depending on the home location. In this case, they would want to do something like: Add/Update field '952c' with value 'Animals' IF field '984c' matches /^(57+[0-9]+.?.*)/ AND IF field '952a' matches 'Main' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 33311] New: Add preference for voice notices
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33311 Bug ID: 33311 Summary: Add preference for voice notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: support(a)shoutbomb.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 148568 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=148568&action=e… Message settings Current options for circulation notices do not include voice/phone. Can this option be added. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 9762] Log circulation overrides
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '23

15 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9762 --- Comment #8 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Lucas Gass from comment #7) > Solene, > > Most of this is working and this will be a great addition! A few things > though: > > -Do these strings need to translatable? > -This is going to need unit tests. The messages in action_logs are usually not translated, but they are also usually not sentences/text, but data changes in JSON and other machine friendly syntax. Could we use codes instead of plain text and then translate them on the action log viewer? This would make them translatable and we could also adjust the texts easier. I expected to find override in the descriptions or it being a new type of action. Maybe we could be a little bit clearer that these were all override actions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 11585] pubdate index not working well in UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '23

15 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11585 --- Comment #4 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- > However, I don't know what is meant by having the same functionality twice > on the page - I can see it only once in the search pulldown menu. When you click on 'more options' there is a separate date range search on the lower part of the page in staff and the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33539] New: Add capitalization checks for branchcodes and categorycodes to inconsistencies script
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '23

15 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33539 Bug ID: 33539 Summary: Add capitalization checks for branchcodes and categorycodes to inconsistencies script Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Through import or migrations and maybe other unknown ways you can end up with data that doesn't match the configured codes for libraries and patron categories in terms of capitalization. It would be nice to have some inconsistency checks for this in our scripts. A good starting point would be: * Check holdingbranch/homebranch in items * Check branchcode and categorycode in borrowers -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 32706] New: User search problem caused by branchcode errors
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '23

15 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32706 Bug ID: 32706 Summary: User search problem caused by branchcode errors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Searching users alphabetically fails when there are two similar branchcode types for the same value in the database: one written in uppercase and the second in lowercase Prerequisites 1. Create a new library with library code written in uppercase 1.1. Go to Administration > Libraries 1.2. Click on New library 1.3. Fill in the form Library code = uppercase code (for example TST ) Name = type a name (for example Test category ) 1.4. Save 2. Create several patrons in the TST library 2.1. Go to the patron module 2.2. Click on “new patron” 2.3 Fill the form Surname, First name, Card number, Library (Choose the same 'TST' library for all users that will be created) 2.4. Save Create other users (~10 ) 3. Export users 3.1. Go to the Report module 3.2. Click on Create from SQL 3.3. Type a Report name and paste the following query to the SQL field: SELECT borrowers.cardnumber, borrowers.surname, borrowers.firstname, borrowers.categorycode, borrowers.branchcode, borrowers.dateexpiry FROM borrowers WHERE borrowers.branchcode= <<branchcode|branches>> ORDER BY borrowers.cardnumber asc 4. Click on Save report then on 'Run report' 5. Choose the branch from step 1.3 and Click on Run the report 5. Download report results 6. Import user folders with lowercase branchcode 6.1. Open the file from step 5 6.2. Edit data 6.3. Remove half of the users from the file 6.4. In the "branchcode" column, replace each value with a lowercase branchcode (for example 'tst') 6.5. Save the file in .csv format 6.6. Go to Tools > Patron imports 6.7. upload the file 6.8. Click on Overwrite the existing one with this 6.9. Click on Replace only included patron attributes 6.10. Click on “Import” Test plan 1. Go to the Patron module 2. Click on a letter of the alphabet 'different' from the users created in step 2.2 --> Koha opens the results 3. Choose a last name letter from one of the users created in step 2.2 --> Koha freezes and it leaves the message “Processing” -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 28269] New: Order search should be possible with ISSN too
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '23

14 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28269 Bug ID: 28269 Summary: Order search should be possible with ISSN too Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: inkeri.hakulinen+bugz(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org At the order search ( koha/acqui/histsearch.pl ) there should be a possibility to search orders by ISSN. Serials don't have an ISBN, but ISSN. Often the serial names are long and similar to each other, so the short and exact searching by ISSN should be an option, too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 32684] New: Implement SIP patron status field "too many items lost"
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '23

14 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32684 Bug ID: 32684 Summary: Implement SIP patron status field "too many items lost" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The SIP patron status and information responses always return false foe "too many items lost". It would be reasonable to check the count of lost items still checked out to the patron and compare that to a threshold set in the sip config file. Though not all libraries operate in this way, it seems like a good and reasonable implementation as long is it is properly documented. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 31782] New: Patron lists - patron autocomplete search does not work
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '23

14 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31782 Bug ID: 31782 Summary: Patron lists - patron autocomplete search does not work 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org When adding a patron to a list, the autocomplete search does not work. Instead, you have to paste the patron card number or borrower number into the Add multiple patrons form. To replicate: 1. Go to Tools > Patrons and circulation > Patron lists. 2. Add a new patron list. 3. Go to add patrons page for the list. Note that there is a JavaScript in the web developer tools console [1]. 4. Type an existing name in the patron search box, for example: mary. 5. Note that the progress icon/circle appears very briefly, but the name is not autocompeleted. 6. Note also that there is a 400 bad request error in the web developer tools console.[2] [1] JavaScript error when viewing Add patrons page for a patron list: Uncaught TypeError: can't access property "_renderItem", $(...).autocomplete(...).data(...) is undefined patron_autocomplete http://127.0.0.1:8081/intranet-tmpl/js/autocomplete/patrons_22.0600062.js:20 <anonymous> http://127.0.0.1:8081/cgi-bin/koha/patron_lists/list.pl?patron_list_id=1:10… jQuery 2 e t [2] 400 bad request error when typing a name in the autocomplete field: GET http://127.0.0.1:8081/api/v1/patrons?term=mary Status: 400 Bad Request Version: HTTP/1.1 .. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 30980] New: Make patron selection more consistent
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '23

14 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30980 Bug ID: 30980 Summary: Make patron selection more consistent 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We have a number of places where one can select a patron as part of a process... but these selects vary wildly.. some are 'autocomplete', others allow for full search. I proposed using select2 consistently for the forms one's when reviewing bug 30578. It's worth investigating. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7