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

[Bug 34122] New: Updating Shelvingloc changes location of all related records
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34122 Bug ID: 34122 Summary: Updating Shelvingloc changes location of all related records Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Partners have reported that updating the shelving location on one item updates all of the items in the record regardless of their branch location. For example, Branch A has Item A located in the Genealogy department, and Branch B has it in their Reference section. Changing the location in Branch A to Genealogy will also change the shelving location for Branch B to Genealogy even if Branch B doesn't have a Genealogy shelving location. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 37455] New: Entering a valid cardnumber at checkin should redirect to checkout
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37455 Bug ID: 37455 Summary: Entering a valid cardnumber at checkin should redirect to checkout Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When one is in the checkout interface and scans in a patron cardnumber instead of an item barcode, Koha automatically redirects to checking out to the patron whose card was scanned. It would be great if it would do the same on the checkin screen. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 32707] New: ElasticSearch should not auto truncate (even if QueryAutoTruncate = 1) for identifiers (and some other fields)
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32707 Bug ID: 32707 Summary: ElasticSearch should not auto truncate (even if QueryAutoTruncate = 1) for identifiers (and some other fields) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com Koha with Zebra prevented auto truncation in some circumstances -- see the first return for ccl inside C4::Search:: buildQuery, before applying auto truncation, and setting $auto_truncation = 0 for some search fields. Koha with ElasticSearch applies auto truncation for all search fields, not paying attention to these special cases when it should not be done. This leads to various problems as described in bug 26508, 26608, etc. The solution would be to prevent auto truncation for certain search fields, above all – the identifiers. In addition, under no circumstances should a search field other than of text type be truncated (an attempt to truncate would generate an exception from ElasticSearch, e.g. number_format_exception for integer). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 36409] New: System preference name consistency - change EMail to Email for SerialsDefaultEMailAddress and AcquisitionsDefaultEMailAddress
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36409 Bug ID: 36409 Summary: System preference name consistency - change EMail to Email for SerialsDefaultEMailAddress and AcquisitionsDefaultEMailAddress Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com As identified in Bug 35457 (see comment number 7), the SerialsDefaultEMailAddress and AcquisitionsDefaultEMailAddress system preference names have a capital m. Other system preference that include 'Email' as part of their name don't have a capital m (such as KohaAdminEmailAddress - search for 'Email' in system preferences to find all occurrences). The system preference names should be changed for consistency: - SerialsDefaultEMailAddress --> SerialsDefaultEmailAddress - AcquisitionsDefaultEMailAddress --> AcquisitionsDefaultEmailAddress -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 35457] New: Move SerialsDefaultEMailAddress and SerialsDefaultReplyTo to serials preferences
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35457 Bug ID: 35457 Summary: Move SerialsDefaultEMailAddress and SerialsDefaultReplyTo to serials preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: System Administration 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 Depends on: 20755 As noted by Caroline on bug 20755, we should move the 2 mentioned system preferences to the serials tab. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20755 [Bug 20755] Allow separate email configuration for acquisition and serials emails -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 37272] New: Show only matching rules options for the type of record being imported in the MARC staging tool
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37272 Bug ID: 37272 Summary: Show only matching rules options for the type of record being imported in the MARC staging tool Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging 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: m.de.rooy(a)rijksmuseum.nl When staging MARC records for import, the form asks what type of records are being imported. When creating a matching rule, the form asks what type of records are being matched. However, when staging authority records for example, all the matching rules are displayed in the drop-down menu. I think it would be cleaner and easier to only show the matching rules for the type of record being imported. To recreate: 1. Create a matching rule for bibliographic records, if you don't already have one 1.1. Go to Administration > Record matching rules 1.2. Click New record matching rule 1.3. Fill out the form, making sure to use bibliographic type and bibliographic indexes - Code: ISBN - Description: 020$a - Match threshold: 1000 - Record type: Bibliographic record - Match point 1 - Search index: isbn - Score: 1000 - Tag: 020 - Subfield: a - Normalization rule: ISBN 1.4. Click Save 2. Create a matching rule for authority records, if you don't already have one 2.1. Go to Administration > Record matching rules 2.2. Click New record matching rule 2.3. Fill out the form, making sure to use authority type and authority indexes - Code: HEADING - Description: Authority headings - Match threshold: 100 - Record type: Authority record - Match point 1 - Search index: heading-main - Score: 100 - Tag: 100 - Subfield: a 2.4. Click Save 3. Go to Cataloging > Stage records for import 4. Click Choose file and choose a file (doesn't matter the file, we just need the rest of the form to be displayed) 5. Click Upload file 6. Choose Record type: Bibliographic 7. Check the matching rules --> All the matching rules are there, including the authority rules 8. Change the record type to Authority 9. Check the matching rules --> All the matching rules are there, including the bibliographic rules -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37447] New: In advanced search, the checkboxes in tabs could depend on the selected library
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37447 Bug ID: 37447 Summary: In advanced search, the checkboxes in tabs could depend on the selected library Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org At the bottom of Advanced search, in "Location and availability" block you can choose a library When you choose a library, the checkboxes displayed in tabs in the top of the page (Shelving location, item types...) could be dynamically be updated, to match the locations available for the selected library Currently you can update these checkboxes by connecting to another library, but it is cumbersome -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 37445] New: Feature that if enabled trims attribute from trailing whitespaces
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37445 Bug ID: 37445 Summary: Feature that if enabled trims attribute from trailing whitespaces Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37443] New: "Refine your search" Includes more than just requested result if the word includes an apostrophe
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37443 Bug ID: 37443 Summary: "Refine your search" Includes more than just requested result if the word includes an apostrophe 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: danyonsewell(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Have done some testing within KTD to make sure it is an upstream bug. Essentially if you are searching for a particular author, say for example Dennis O'Driscoll and you also have items from another author by the name of Dennis O'Malley If you search for O'Driscoll and use the "Refine your search" feature to select titles only by author Dennis O'Driscoll, you'll be given results by both Dennis O'Driscoll and Dennis O'Malley. After further testing I have narrowed it down to the apostrophe being the reason for this, I haven't figured out why just yet but it's a start. I have tried this on both 24.05 and 23.11 and the behavior is consistent. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29672] New: Increase performance of Koha::Plugins->call
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29672 Bug ID: 29672 Summary: Increase performance of Koha::Plugins->call Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Every call to Koha::Plugins->call do a lot of database queries: 1) One in GetPlugins searches for available plugin_class in plugin_methods table 2) One in Koha::Plugins::Base::is_enabled for each plugin returned by (1) 3) One or two in Koha::Plugins::Base::new for each plugin returned by (1) to check the install status and the installed version All of these requests only need to be made once per HTTP request at most. One could argue that it's needed only at Koha startup but that besides the point of this bug report. -- You are receiving this mail because: You are watching all bug changes.

1 56