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

[Bug 33255] New: Update the manual with information on searching with Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33255 Bug ID: 33255 Summary: Update the manual with information on searching with Elasticsearch 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 Maybe I missed it, but I didn't find any Elasticsearch specific information in the wiki for things like truncation, using indexes, boolean, fuzzy etc. There has recently been a nice blog post about searching that could be a starting point: https://bywatersolutions.com/education/monday-minutes-elastic-search Especially the linked cheat sheet: https://drive.google.com/file/d/17-YVjG6IJKeDmDCKuF7ZYvcTfzDYyxwa/view Some more sources to draw from maybe: https://bywatersolutions.com/education/elastic-searching https://bywatersolutions.com/education/elastic-search-configuration -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 33304] New: Report schedule form time input element attribute type changed to improve valid time value entry
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33304 Bug ID: 33304 Summary: Report schedule form time input element attribute type changed to improve valid time value entry 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: adam.styles(a)esa.edu.au QA Contact: testopia(a)bugs.koha-community.org Created attachment 148518 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=148518&action=e… report schedule start time input fix Hello community, I offer an enhancement for the task scheduler form: /cgi-bin/koha/tools/scheduler.pl via scheduler.tt The time input element currently has an 'text' value for type attribute. This requires a user to enter a valid time string for any scheduled report manually which is no fun. I have created patch in scheduler.tt that changes the type attribute value from 'text' to 'time' which makes the input of valid time easy. This change leveraged standard web form principles of html5 and would be compatible with any modern browser such as chrome, firefox and safari etc. Patch incoming. Thoughts and feedback invited. Thanks. 8-) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 16791] New: Explanation of callnumber.pl plugin
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16791 Bug ID: 16791 Summary: Explanation of callnumber.pl plugin Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: eb(a)efdss.org QA Contact: testopia(a)bugs.koha-community.org Perhaps a brief explanation of what callnumber.pl is meant to do would be a useful addition to the manual. I am not certain what its function is, though I discovered that it doesn’t do what I was hoping it would. See bug 13615 for a long winded query. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 29188] New: Expired serial subscriptions can still receive issues
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29188 Bug ID: 29188 Summary: Expired serial subscriptions can still receive issues 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In the manual, it says "If your serial subscription has expired you won’t be able to receive issues." But that is not actually true. Expired subscriptions can still generate new issues and you can still receive them. To stop a subscription from generating new issues, you have to close it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 31638] New: [DOCS] Log viewer - Expand section and add descriptions for objects and actions
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31638 Bug ID: 31638 Summary: [DOCS] Log viewer - Expand section and add descriptions for objects and actions 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org In the manual, there is currently no description or information about how to use the objects and action fields in the log viewer. The section could also be expanded. Resources to help with this: - SQL Reports Library. https://wiki.koha-community.org/wiki/SQL_Reports_Library#action_logs - ByWater Solutions. Monday Minutes : Using the Logs. 18 January 2021. https://bywatersolutions.com/education/to-log-or-not-to-log - Mailing list thread: https://lists.katipo.co.nz/pipermail/koha/2022-September/058489.html Manual reference: https://koha-community.org/manual/22.11/en/html/tools.html#log-viewer -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 30618] New: Important and mandatory select fields not highlighted on additem.pl
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30618 Bug ID: 30618 Summary: Important and mandatory select fields not highlighted on additem.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If one tries to add an item and mandatory or important select field isn't filled, field isn't highlighted like input fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28546] New: Framework default value special var for year in Manual
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28546 Bug ID: 28546 Summary: Framework default value special var for year in Manual Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org There is a mistake (or change) in framework default value special vars. In manual : There are several values that you can use here that will be replaced automatically when a new record is created: <<MM>> - the current month, 2 digits <<DD>> - the current day of month, 2 digits <<YEAR>> - the current year, 4 digits <<USER>> - the username of the currently logged in user For example: a default of "<<MM>>/<<DD>>/<<YEAR>>" (without quotes) will print the current date in the form of "01/21/2021" See https://gitlab.com/koha-community/koha-manual/-/blob/master/source/administ… But in Koha code in cataloguing/addbiblio.pl : $value =~ s/<<YYYY>>/$year/g; $value =~ s/<<YY>>/$shortyear/g; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28501] New: Document how to use the search configuration page
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28501 Bug ID: 28501 Summary: Document how to use the search configuration page Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Keywords: Manual 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 In the manual there is currently no information on how to use the search configuration page for Elasticsearch. I am especially thinking of: - How to add a field/subfield to an existing index - How to create a new index to use for search -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 21250] New: Auto-self-checkout not fully compatible with two-branch library setup
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21250 Bug ID: 21250 Summary: Auto-self-checkout not fully compatible with two-branch library setup Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org We use a two-branch library setup, both with auto-self-checkout enabled, so patrons log in with their cardnumber via the pre-defined staff user account (see below). The problem is that since the internal self-checkout user also has to be assigned to exactly one branch, that branch will be used as "current location" when a patron checks out a book. So, it's the self-service account's branch that's used instead of the patron's/borrower's branch. >From looking at the code it seems that C4::Circulation->AddIssue() is using "C4::Context->userenv->{branch}" where "$borrower->{'branch'}" should probably be used instead, since the current user's branch isn't relevant (even wrong) in the auto-self-checkout context. FYI, we use the following config (if relevant at all): - Koha 18.05.01-2 - AutoSelfCheckAllowed: Allow (AutoSelfCheckID/AutoSelfCheckPass) - CircControl: the library the item is from - HomeOrHoldingBranch: the library the item is from Thank you. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 25165] New: Explain all the cataloging plugins
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25165 Bug ID: 25165 Summary: Explain all the cataloging plugins 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The only one that I could find in the manual is the cn_browser plugin, the upload plugin and a vague mention of unimarc 1XX plugins. https://koha-community.org/manual/19.11/en/html/administration.html#edit-ex… (towards the end of the section) As of writing this (19.12.00.071) this is the list of plugins: - barcode - barcode_manual - callnumber-KU - callnumber - cn_browser - dateaccessioned - macles - marc21_field_005 - marc21_field_006 - marc21_field_007 - marc21_field_008 - marc21_field_008_authorities - marc21_field_008_classifications - marc21_field_245h - marc21_leader - marc21_leader_authorities - marc21_linking_section - marc21_orgcode - normarc_field_007 - normarc_field_008 - normarc_leader - stocknumber - stocknumberAV - stocknumberam123 - unimarc_field_010 - unimarc_field_100 - unimarc_field_100_authorities - unimarc_field_105 - unimarc_field_106 - unimarc_field_110 - unimarc_field_115a - unimarc_field_115b - unimarc_field_116 - unimarc_field_117 - unimarc_field_120 - unimarc_field_121a - unimarc_field_121b - unimarc_field_122 - unimarc_field_123a - unimarc_field_123d - unimarc_field_123e - unimarc_field_123f - unimarc_field_123g - unimarc_field_123i - unimarc_field_123j - unimarc_field_124 - unimarc_field_124a - unimarc_field_124b - unimarc_field_124c - unimarc_field_124d - unimarc_field_124e - unimarc_field_124f - unimarc_field_124g - unimarc_field_125 - unimarc_field_125a - unimarc_field_125b - unimarc_field_126 - unimarc_field_126a - unimarc_field_126b - unimarc_field_127 - unimarc_field_128a - unimarc_field_128b - unimarc_field_128c - unimarc_field_130 - unimarc_field_135a - unimarc_field_141 - unimarc_field_210c - unimarc_field_210c_bis - unimarc_field_225a - unimarc_field_225a_bis - unimarc_field_4XX - unimarc_field_686a - unimarc_field_700-4 - unimarc_leader - upload -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7