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

[Bug 34186] New: Adding subfield q to 110/710 to framework
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '24

04 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34186 Bug ID: 34186 Summary: Adding subfield q to 110/710 to framework Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.petritsch(a)wienmuseum.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The field 100, 130, 700, 730 have the subfield q which enables to add a name manually. For the fields 110, 710 this is not the case. Adding a q subfield manually while cataloging or permanently in the framework didn't do the trick either. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36805] New: Separate OPACSearchForTitleIn content from markup
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36805 Bug ID: 36805 Summary: Separate OPACSearchForTitleIn content from markup Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org The OPACSearchForTitleIn system preference expects the user to be able to enter their list of links using the correct markup for them to be displayed in the "More searches" Bootstrap dropdown. As Bug 35844 shows, this content can get out of date with Bootstrap upgrades. I think we might want to separate the link content from the markup. My suggestion is that we ask the user to enter each link on one line, with URL pipe-separated from link text, e.g.: https://worldcat.org/search?q={TITLE}|Other Libraries (WorldCat) We can parse that in the template: [% FOREACH line IN OPACSearchForTitleIn.split('\n') %] [% part = line.split('\|') %] <a class="dropdown-item" href="[% part.first | html %]" target="_blank">[% part.last | html %]</a> [% END %] Does that sound reasonable? -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 28082] New: Add acquisitions toolbar to vendors on vendor search page
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28082 Bug ID: 28082 Summary: Add acquisitions toolbar to vendors on vendor search page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org We can improve consistency and expand functionality be adding inclusion of the acquisitions toolbar include on the vendor search results page. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 31208] New: "Check for embedded item record data" should default to "No"
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31208 Bug ID: 31208 Summary: "Check for embedded item record data" should default to "No" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, "Check for embedded item record data" in stage-marc-import.pl defaults to "Yes", but I doubt that the majority of libraries would want to check for embedded item record data. (By extension, I think it would be good to default "How to process items:" to "Ignore items" instead of "Always add items" - just to be on the safe side.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 31755] New: Store biblio OPAC visibility in biblio table
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31755 Bug ID: 31755 Summary: Store biblio OPAC visibility in biblio table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, you have to interrogate the MARCXML to determine if a record is suppressed using OpacSuppression, and you have to iterate through all of a bib's items to see if it's hidden/suppressed using OpacHiddenItems and OpacHiddenItemsHidesRecord. As Tomas said at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31161#c21, it would make sense to have a "suppressed" field in the biblio table so that we can determine a biblio record's OPAC visibility using a simple SQL query. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 26168] New: Create admin Linux user "koha" which is member of all *-koha instance groups
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26168 Bug ID: 26168 Summary: Create admin Linux user "koha" which is member of all *-koha instance groups Change sponsored?: --- Product: Koha Version: unspecified 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org It would be useful to have an administrative Linux user "koha" which is a member of all *-koha instance groups. The high level use case is a non-root (daemon) service that can run "koha-shell kohadev -c 'command'". At the moment, you could just run that (daemon) service as root, but ideally it would be better to run it as a less privileged user. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 25635] New: overdue_notices.pl dies if no overdue rules are defined
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25635 Bug ID: 25635 Summary: overdue_notices.pl dies if no overdue rules are defined Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org overdue_notices.pl dies if no overdue rules are defined, but there are many cases where you might not want any overdue rules to be defined. (If you're running overdue_notices.pl within koha-foreach, koha-foreach will now die on the first instance it encounters that has no overdue rules defined.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 28232] New: koha-plack dies even when there is work to for multiple instances
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28232 Bug ID: 28232 Summary: koha-plack dies even when there is work to for multiple instances Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you run "koha-plack --stop $(koha-list --enabled --plack)", it won't stop any instances if the first instance in the list is already stopped. This doesn't really make sense. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 19306] New: Adding hooks to the plugin system
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19306 Bug ID: 19306 Summary: Adding hooks to the plugin system Change sponsored?: --- Product: Koha Version: unspecified 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: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org We've been working on adding hook functionality to the existing plugin system. This is very much proof-of-concept code at the moment, but here is how it works. 1. Somewhere in the code you add a hook-call with a name for that hook, and pass in some data relevant to that hook. 2. Each plugin with a method matching the hook name is called in sequence, with the data as input and returning data of similar form, which is then passed on to the next matching plugin. 3. The end result is returned back from the hook-call, is put back in place, and code execution is resumed. The PoC code adds a Koha::Plugins::Handler->run_matching() method that looks up the relevant loaded plugins (using GetPlugins) and calls Koha::Plugins::Handler->run() on each of them. If plugins are not enabled, or if there is no plugin matching the hook, the input data is returned back, resulting in unaffected operation. One hook is added in Koha::SearchEngine::Elasticsearch::QueryBuilder.pm, in build_query_compat with the name "build_query_before", which is simply run before the query parsing takes place. A very simple example plugin is available at: https://github.com/ub-digit/koha-plugin-build-query-example/releases This plugin edits a query beginning with "Provider:" to do "publisher:" instead. A simple example that when using Elasticsearch makes publisher links in the bibliographic detail view clickable. The current XSLT uses the Zebra based links, that result in an unusable search. This is not meant to be the solution to the Zebra/Elasticsearch conflict in the XSLT, but it's a simple demonstration of the hook feature. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 34662] New: Allow configuration of search type in main search bar
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '24

31 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34662 Bug ID: 34662 Summary: Allow configuration of search type in main search bar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 The top search bar defaults to different types of search depending on the page one is on. It would be helpful to make this configurable to allow for local preference. For example, when one is looking at a Normal view of a bib record (/cgi-bin/koha/catalogue/detail.pl?biblionumber=X), the top search bar defaults to Search the Catalog. But if one clicks to Holds on the same record (/cgi-bin/koha/reserve/request.pl?biblionumber=X), then the top search bar switches to Check Out. Our staff find this disruptive, but I don't expect a strong consensus across the community for how this should behave. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2