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

[Bug 30269] New: Use objects directly to display holds on request.pl
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '24

17 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30269 Bug ID: 30269 Summary: Use objects directly to display holds on request.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 request.pl fetches holds objects, then loops over them to build a hash for display - we don't need this intermediate step. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 23622] New: Add the ability to edit suspensions like fines would be edited.
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '24

17 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23622 Bug ID: 23622 Summary: Add the ability to edit suspensions like fines would be edited. Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We want to be able to edit suspensions and see the suspension history of a patron on their circulation record, just as a fine and other charges would be in a library that charges fines. We want to be able to edit a suspension, to change the expiry date on it, to extend it, to waive it, or to mark it complete. In addition we need to be able to input a staff note as to the reason why this happened. This should be on the account tab on the Fines link from the lefthand navigation menu. The last thing we want any staff member to do is delete a suspension, as that gives a false report on the patron re returning materials to the library. At the moment we can only delete a suspension, but we may want to shorten it. If we delete it there is nowhere to record the reason why that is associated with the suspension. At the moment the suspension either remains or can be removed completely but often situations might arise where some compromise is required depending on circumstances. The ability to edit suspensions allows for greater flexibility in dealing with patron suspensions. Messy patron records result. Without the ability to edit it can mean greater difficulty in dealing with issues in relation to suspensions which in turn impacts on staff time and customer service and satisfaction. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 34962] New: Add a system messages feature to Koha to report issues and failures in a more visible way
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34962 Bug ID: 34962 Summary: Add a system messages feature to Koha to report issues and failures in a more visible way 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Many web projects have a "system messages" area to report cron failures and things like that. These messages are often dismissable. I think it would be great to have a "system messages" table that we could insert things into to make staff aware that something has failed. What I'm imagining is something like wrapping cronjob code in a try/catch and reporting cronjob failures. This would dovetail with action logs. Action logs lot you got searching for issues. This would put the issue right in front of you and would be trigger by actual failures. It could be used to report records with malformed MARC. It could be used to report items that are missing a required field that Koha assumes exists to function, and so on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 29731] New: UNIMARC 100$a 17-19 Target Audience Code
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '24

14 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29731 Bug ID: 29731 Summary: UNIMARC 100$a 17-19 Target Audience Code Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org Problem UNIMARC 100 $a/17-19 Target Audience Code It is not possible to use the "#" symbol. Unused positions are filled with space characters "#". For example, when you need to use "x##". https://cdn.ifla.org/wp-content/uploads/files/assets/uca/unimarc_updates/BI… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 30547] New: Plugin for coded data 123p UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '24

14 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30547 Bug ID: 30547 Summary: Plugin for coded data 123p UNIMARC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org Please, add plugin for coded data 123p UNIMARC $p Planet (Mandatory for planets other than Earth, Not repeatable) $p/0-1 Planet ea Earth ju Jupiter ma Mars me Mercury ne Neptune pl Pluto sa Saturn ur Uranus ve Venus zz Other $p/2 Satellite s The body whose co-ordinates are recorded in subfields $d-$g is a satellite of the planet coded on pos. 0-1. y Not applicable: the body whose co-ordinates are recorded in subfields $d-$g is the planet itself, as coded on pos. 0-1. https://archive.ifla.org/VI/8/unimarc-concise-bibliographic-format-2008.pdf -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 26314] New: "Volumes: show volumes" showing regardless of whether there are volumes linked to the record
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26314 Bug ID: 26314 Summary: "Volumes: show volumes" showing regardless of whether there are volumes linked to the record 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 Depends on: 15851 When cataloguing multi part records with sets and volumes, we currently show a link to "Show volumes" on the set record. The link is always shown on a set record, even if there are no linked volumes. Bug 15851 solves the same issue for analytics. volumes would be a great next step. At the moment Show volumes is only shown on monographs, but we could add the feature for serial records as well. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15851 [Bug 15851] "Analytics: Show analytics" showing regardless of whether they have analytics -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 98

[Bug 35099] New: Cannot load records with invalid marcxml
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35099 Bug ID: 35099 Summary: Cannot load records with invalid marcxml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org After bug 26314 we cannot load records with marcxml issues - the get_volumes_query calls Koha::Biblio->metadata->record and does not catch the exception -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 20202] New: Link EDI account to Create Edi order
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20202 Bug ID: 20202 Summary: Link EDI account to Create Edi order Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: cunha(a)monterey.org QA Contact: testopia(a)bugs.koha-community.org Currently to send create an EDI order you click "Create EDIFACT order" and are taken to a page to select, if you have multiple EDI accounts, your vendor account from a drop-down menu. It would be great if the Vendor and EDI account could be linked, so there would be no possibility of sending the order to the wrong account. We started with the ByWater beta version of EDI, that was the way it worked in beta. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 29573] New: MARC Framework Subfields Visibility Setting Not Obeyed for 5XX
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29573 Bug ID: 29573 Summary: MARC Framework Subfields Visibility Setting Not Obeyed for 5XX Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jialun(a)toa.edu.my QA Contact: testopia(a)bugs.koha-community.org Created attachment 127988 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=127988&action=e… Tag 583 Subfield constraints I've recently upgraded to version 21.05.05.003 and encountered an issue with the when viewing an item inside the OPAC (opac-detail.pl) while using Normal view inside the Title notes. Our librarians have configured the one of the Subfields for MARC Framework 583 to be hidden in the OPAC but visible for Intranet and Editor. It was working fine in version 20.11 but once we upgraded to version 21.05 it appeared inside the OPAC despite the visibility setting. I've tested changing the Subfields Visibility setting by enabling either OPAC or Intranet only but there was not changes in the OPAC or Staff Client either. The Title Notes were still visible. Thank you in advance for your help! -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 27365] New: Koha doesn't check marcxml field size is < 10000 and fails in various places
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27365 Bug ID: 27365 Summary: Koha doesn't check marcxml field size is < 10000 and fails in various places Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi ISO standard >The core of the framework is a MARCXML schema that allows lossless round-trip >conversion of an ISO 2709 MARC 21 record and an XML-encoded MARC 21 record. Thus a field size is 9999 bytes max. But /usr/share/perl5/MARC/File/USMARC.pm doesn't care: my $direntry = sprintf( "%03s%04d%05d", $field->tag, $len, $dataend ); and if len >= 10000 it silently creates a bogus directory with a length of 13 rather then 12. These non-conformed marxml will fail in various places. Export, search results list with elasticsearch which store ISO 2709 record in index and use them as data source in results list. eg: Easy to trigger in french UNIMARC with 359 (sorry in french) https://www.transition-bibliographique.fr/wp-content/uploads/2019/02/B359-2… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55