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

[Bug 27146] New: add pluggability to save/store on add/edit bibliographic data
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27146 Bug ID: 27146 Summary: add pluggability to save/store on add/edit bibliographic data 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: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl as discussed on IRC on 2.12.2020 on editing bibliograpic data cgi-bin/koha/cataloguing/addbiblio.pl quite often "functional defaults" are needed, like dates, sequence numbers and so on mostly those values should be transparent for the users ie those values must not be edited or even not seen by the users the only possibility at the moment (at least I am aware of) are the value_builder plugins /usr/share/koha/intranet/cgi-bin/cataloguing/value_builder which need a least some user intervention, like clicking the fields good examples are controlnumber 001 and 005 (maybe 003) which mostly would need no user intervention at all see bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 27095] New: Align data in the Compare Records function
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27095 Bug ID: 27095 Summary: Align data in the Compare Records function Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you import records using the stage records tool, and find a match, you have the option to compare the two records. However, when you view the records side by side, the marc fields do not line up (for a variety of reasons) making it difficult to compare the same field in each record. It is possible for the 610 (for example) marc field to be half a screen or more further down in one record than the other. It would be really helpful to have the fields line up next to each other. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 27094] New: Allow item types to be selected/deselected for use at bib level and item level
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27094 Bug ID: 27094 Summary: Allow item types to be selected/deselected for use at bib level and item level Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be really awesome to be able to decide which item types should show in the 942$c versus 952$y. For instance, if I have the item type of BEST that has a shorter checkout period for bestsellers, I want that at the 952$y, not at the 942$c. I want to see BOOK at the 942$c and not show BEST as an option. I would picture this being set in the item types set up, with checkboxes to determine whether or not this item type is visible in the dropdowns of the respective fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 27093] New: Barcode on label overlapped by text; unable to center
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27093 Bug ID: 27093 Summary: Barcode on label overlapped by text; unable to center Change sponsored?: --- Product: Koha Version: 19.11 Hardware: PC OS: Mac OS Status: NEW Severity: minor Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: lotsalegos2006(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 113998 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=113998&action=e… Sample barcode problem Unable to center barcode on label which causes overlapping and cutting off when printing (please see attached) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 27091] New: Document how Elasticsearch is supposed to work and implement respective configurations
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27091 Bug ID: 27091 Summary: Document how Elasticsearch is supposed to work and implement respective configurations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi CC: nick(a)bywatersolutions.com Elasticsearch is very flexible search engine and has many configuration options. We should document our expectations on how it should work and also because then it would allow the users to understand how to form their queries in the best possible way. After documenting the configuration we want based on the expectations we should tune the indexing and search configuration parameters accordingly. The bug 27070 makes the Elasticsearch searches more Zebra like by trying to match search keywords across all fields but is this exactly what we want in the end? What if we have only a number in the search query should we try to query numeric fields then only or also string fields? How should the weights work? For weight documentation we should have an basic configuration for it in our default mappings.yaml file so that we have some idea how it will be used in real world. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 27075] New: "Cancel charge" doesn't seem to appear in po files or on translate
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27075 Bug ID: 27075 Summary: "Cancel charge" doesn't seem to appear in po files or on translate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 24603 I am not sure why, but there appears to be a translation issue with the new "Cancel charge" button on the account in the staff interface. German po files are at 100% but I can't find it searching translate.kc.org. I also can't fit it outside the template using git grep. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24603 [Bug 24603] Allow to cancel charges in patron accounting -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27057] New: Add the ability to have a Override this entire Checkout transaction when Allowtoomanyoverride is turned on
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27057 Bug ID: 27057 Summary: Add the ability to have a Override this entire Checkout transaction when Allowtoomanyoverride is turned on Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice to allow staff to Override an entire Patron transaction when the library is allowing staff to AllowTooManyoverride. Right now, when a staff member is checking out to a patron that has gone over the limit of the number of checkouts, they have to override each checkout. A good example would be, a patron that has just returned all their books in the book drop and now want to checkout more- because the others have not been checked in, they have gone over their checkout total but the library would like to allow this. This enhancement would save a lot of clicking! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 27040] New: Allow definition of default value for NEW_CARD debit type
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27040 Bug ID: 27040 Summary: Allow definition of default value for NEW_CARD debit type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The NEW_CARD debit type is included in a new instal with a default value of $0. It cannot be edited. It would be helpful to give libraries a way to change that default value to whatever they charge for a new card, rather than requiring them to set the amount manually every time a new card fee is added to a patron account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30064] New: Dates in issues table on subscriptions tab in OPAC are not sorting correctly
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30064 Bug ID: 30064 Summary: Dates in issues table on subscriptions tab in OPAC are not sorting correctly 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The publication date and received date columns in the issues table in the OPAC are not sorting correctly. To recreate: - Create a subscription - Receive mulitple issues, manipulate the published and received dates to be in different months and years - Open the record in the OPAC and switch to the subscription tab - The sorting on top of the table indicates that it should be sorted by publication date - Verify it is not sorted correctly, also not after clicking on the column header -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 28997] New: Subscription table sorting in the opac
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28997 Bug ID: 28997 Summary: Subscription table sorting in the opac Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: janet.mcgowan(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Similar to the issues reported in Bug 27934, the subscription table is not sorting correctly. In opac-detail.tt <td class="publisheddate"><span title="[% latestserial.publisheddate | html %]">[% latestserial.publisheddate | $KohaDates %]</span></td> <td class="planneddate"><span title="[% latestserial.planneddate | html %]">[% latestserial.planneddate | $KohaDates %]</span></td> If these lines are changed to use data-order instead as per: <td data-order="[% reserveloo.waitingdate | html %]">[% reserveloo.waitingdate | $KohaDates %]</td> <td data-order="[% reserveloo.reservedate | html %]">[% reserveloo.reservedate | $KohaDates %]</td> they sort correctly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1