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

[Bug 20058] New: Option to use shelving location instead of homebranch for sorting
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20058 Bug ID: 20058 Summary: Option to use shelving location instead of homebranch for sorting 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: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com By default a checkin response via SIP2 has homebranch in AQ. AQ is used for sorting by our (Gothenburg University) machines. The provided patch adds a syspref to select permanent_location instead of homebranch as the value put in AQ. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 19966] New: Add ability to pass objects directly to slips and notices
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19966 Bug ID: 19966 Summary: Add ability to pass objects directly to slips and notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha spends an incredible amount of time on parsing and processing parameters passed in to slips and notices. It would be immensely more efficient to be able to pass objects directly to GetPreparedLetter so it doesn't need to do any fetching / processing on them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 22678] New: Set 'Koha::Logger' as the default mojo logger for the REST API
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22678 Bug ID: 22678 Summary: Set 'Koha::Logger' as the default mojo logger for the REST API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com Target Milestone: --- Bug 18205 tries to do allot of things in one bug.. this is an alternate implementation limited down to just replacing the default Mojo::Log logger in the Mojolicious app with a Koha::Logger instead. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 22347] New: Translatability of ILSDI results for getavaibility
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22347 Bug ID: 22347 Summary: Translatability of ILSDI results for getavaibility Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- It would be very useful if we could translate information provided by ILS-DI as availability status, availability msg. It would be useful when you use it with a discovery tool which can't translate it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 18086] New: overduerules table is lacking foreign key constraints
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18086 Bug ID: 18086 Summary: overduerules table is lacking foreign key constraints Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The overduerules table has no foreign key constraints to any for the related tables. The columns for branchcode, categorycode, letter1, letter2, and letter3 should all be foreign keys. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 101

[Bug 16698] New: UpdateItemLocationOnCheckin preference needs a gui editor
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16698 Bug ID: 16698 Summary: UpdateItemLocationOnCheckin preference needs a gui editor 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 14576 adds a new syspref that accepts YAML for determining how the rules are applied. While there are other prefs accepting values in the same way, we should not expect users to understand YAML text formatting and should offer an easier option for entering the data We should decide on a best practice here for adding these guis. One option is to add pages on admin, however, I think this could get overwhelming the more sysprefs that use this method. I would propose adding a popup editor that will allow for easy entry, this editor will populate the syspref value so that advanced users can still access directly. Welcome to hear other thoughts, will proceed as proposed until then. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 18533] New: MARC::Record->encoding does not handle UNIMARC records
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18533 Bug ID: 18533 Summary: MARC::Record->encoding does not handle UNIMARC records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 18152 Regarding bug 18152 MARC::Record->encoding should not be called directly from our codebase. C4::Charset::SetMarcUnicodeFlag should call MARC::Record->encoding for MARC21 and NORMARC but does the UNIMARC trick for UNIMARC records. It seems that MARC::Record->encoding calls should be replaced with C4::Charset::SetMarcUnicodeFlag everywhere. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18152 [Bug 18152] UNIMARC bib records imported with invalid 'a' char in label pos.9 -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 23758] New: Advanced editor should have a widget to automatically populate when a biblio was first entered
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '24

06 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23758 Bug ID: 23758 Summary: Advanced editor should have a widget to automatically populate when a biblio was first entered Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hayleymapley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be useful for libraries who use the Advanced Editor to have the ability to automatically populate a field with the current date the first time a biblio record is entered. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[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 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