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

[Bug 31618] New: Typo in POD for C4::ImportBatch::RecordsFromMARCXMLFile
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31618 Bug ID: 31618 Summary: Typo in POD for C4::ImportBatch::RecordsFromMARCXMLFile Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org 1572 =head2 RecordsFromMARCXMLFile 1573 1574 my ($errors, $records) = C4::ImportBatch::RecordsFromMARCXMLFile($input_file, $encoding); 1575 1576 Creates MARC::Record-objects out of the given MARCXML-file. 1577 1578 @PARAM1, String, absolute path to the ISO2709 file. The last line should say MARCXML, not ISO2709. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 31253] New: Item search in staff interface should call barcodedecode if the search index is a barcode
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31253 Bug ID: 31253 Summary: Item search in staff interface should call barcodedecode if the search index is a barcode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should run any inputted barcode through barcodedecode before passing it to any subroutines. This was missed during the initial development of bug 26351. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 26700] New: Remove unused C4/SIP/t directory
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26700 Bug ID: 26700 Summary: Remove unused C4/SIP/t directory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor 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 doesn't seem like C4/SIP/t is used, so we may as well remove it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 32245] New: Deleting news entries from Koha's staff start page is broken
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32245 Bug ID: 32245 Summary: Deleting news entries from Koha's staff start page is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface 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 When you try to delete a news entry from Koha's staff start page you get the confirmation question, but when you say yes, you end up in the HTML customizations with an empty page. The news entry is not deleted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 31651] New: Log message incorrect in Auth_with_shibboleth.pm
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31651 Bug ID: 31651 Summary: Log message incorrect in Auth_with_shibboleth.pm Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org There's a bad copy/paste of a log message in Auth_with_shibboleth.pm. The second occurance of `There are several users with $config->{matchpoint} of $match, matchpoints must be unique` should really read something like `No users with $config->{matchpoint} of $match found and autocreate is disabled` -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 24517] New: Zebra: date-entered-on-file misses 6th position
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24517 Bug ID: 24517 Summary: Zebra: date-entered-on-file misses 6th position Change sponsored?: --- Product: Koha Version: master 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Date entered on file is in MARC21 tag 008 position 00 to 05 (or 1-6 for normal humans). In Koha only the first 5 digits are indexed with Zebra. Does not really facilitate searching ;) <index_control_field tag="008" offset="0" length="5"> <target_index>date-entered-on-file:n</target_index> </index_control_field> <index_control_field tag="008" offset="0" length="5"> <target_index>date-entered-on-file:s</target_index> </index_control_field> <xslo:template match="marc:controlfield[@tag='008']"> <z:index name="date-entered-on-file:n"> <xslo:value-of select="substring(., 1, 5)"/> </z:index> <z:index name="date-entered-on-file:s"> <xslo:value-of select="substring(., 1, 5)"/> </z:index> Elasticsearch appears to do a better job: date-entered-on-file: label: date-entered-on-file mappings: - facet: '' marc_field: '008_/0-5' marc_type: marc21 sort: ~ suggestible: '' - facet: '' marc_field: '008_/0-5' marc_type: normarc sort: ~ suggestible: '' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 32478] New: Remove Koha::Config::SysPref->find since bypasses cache
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32478 Bug ID: 32478 Summary: Remove Koha::Config::SysPref->find since bypasses cache Change sponsored?: --- Product: Koha Version: master 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Using Koha::Config::SysPrefs->find('UpdateItemLocationOnCheckin')->get_yaml_pref_hash() to retrieve yaml sysprefs will bypass caching negating the very minor performance gain per call get_yaml_pref_hash was meant to achieve since it in some cases is being called repeatedly a very large number of times. Replacing it with C4::Context->yaml_preference('ItemsDeniedRenewal') will utilize the syspref cache and also not support a very small (not even valid) subset of YAML. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 29769] New: Claim return status cannot be changed without checking item in
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '23

16 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29769 Bug ID: 29769 Summary: Claim return status cannot be changed without checking item in Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the addition of bug 24279, libraries can no longer change the status of a claim return without checking the item in, which is not a desired behavior. Example: a library sets an item to claims return, looks for the item for three months per policy, item is not found, status needs to be changed from Claim to Lost so the patron is billed for the item. In this scenario, the item should not be checked in to clear the claim status. Marking the claim as resolved does not allow the status to be changed either. Perhaps this could be a setting with Claims Return system preferences as to whether staff are permitted to change the claim/lost status of an item from moredetail.pl? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 28618] New: Move t/lib modules to lib/Koha/Test
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '23

16 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28618 Bug ID: 28618 Summary: Move t/lib modules to lib/Koha/Test Change sponsored?: --- Product: Koha Version: master 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 29258] New: Add a value builder for filling in the vendor id in the item form
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '23

16 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29258 Bug ID: 29258 Summary: Add a value builder for filling in the vendor id in the item form 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using the acquisitions module the vendor field in the item form (item.booksellerid) will be filled with the id of the vendor record. Sometimes, there are items that will still be catalogued outside the acquisitions module, like older acquisitions or donations. To not have a mix of "string" vendor names and ids in the item field, it would be nice if we have a value builder/cataloging plugin that allowed to search for vendors and added the id to the form when editing/adding items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3