December 2021 - Koha-bugs - lists.koha-community.org

[Bug 15725] New: Merge permission
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '24

26 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15725 Bug ID: 15725 Summary: Merge permission Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice if Koha had a permission to limit access to the merge records option (Merge selected button) on the addbooks.pl search results page and the virtualshelves/shelves.pl page (lists). This is especially important in a consortial catalog environment where many people have cataloging permissions, but most probably shouldn't have the ability to merge records. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 19876] New: Koha::Account->pay() does not exit specific fine loop when balance is used up
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19876 Bug ID: 19876 Summary: Koha::Account->pay() does not exit specific fine loop when balance is used up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a patron selects specific fines to pay and enters an amount less than all of those fines the loop will continue through all fines. This can be problematic for lost fines which are not paid or not paid fully as they will be marked 'Paid for...' and returned -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 17138] New: UpdateFine() modyfies existing fine records even when there is no need
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17138 Bug ID: 17138 Summary: UpdateFine() modyfies existing fine records even when there is no need Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In C4/Overdues.pm: 574: # we're updating an existing fine. Only modify if amount changed 577: if ( $data->{'amount'} != $amount ) { for some numbers (e.g. 5.60) the comparison in line 577 fails ($data->{'amount'} is decimal(28,6) i.e. a string, and $amount may be a floating point number with no exact binary representation). E.g. when the fine amounts are multiple of 0.20, it fails for the 33.3% of the amounts (on average). Depending on the fine charging settings, this may trigger unnecessary database writes (and a lot of them). If 'Fine Charging Interval' is 1 day, this has very little practical consequences (misc/cronjobs/fines.pl script is usually run once per day, and all fines need an increase anyway). But if the charging interval is longer, e.g. 7 days, in a given day amount changes only for the 1/7 of the fines (again, on average), and over 60% of the database writes would be redundant. To reproduce: 1) run misc/cronjobs/fines.pl 2) add warn "AMOUNT ".$data->{'amount'}." vs $amount"; below line 577 in C4/Overdues.pm 3) run misc/cronjobs/fines.pl again 4) you'll see some warnings like 'AMOUNT 5.600000 vs 5.6' or: dump accountlines table after step 1), run the script 2nd time, dump the table again and compare the contents - some of the records would have a different timestamp. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 26662] New: Authority linking doesn't work with custom authority type
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26662 Bug ID: 26662 Summary: Authority linking doesn't work with custom authority type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you're using custom authority types, automatic linking via C4::Biblio::LinkBibHeadingsToAuthorities will never work. It's because C4::Heading::MARC21 has a hard-coded mapping of bib fields to authority types (instead of consulting the MARC bibliographic framework). This means if you're using "CORPO_NAME_AWSEOME" instead of "CORPO_NAME" for your authorities, you'll never get an automated match, since C4::Heading::_search (used ultimately by C4::Linker::Default) uses the hard-coded auth_type from C4::Heading::MARC21. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 22403] New: Temporary Card
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '24

18 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22403 Bug ID: 22403 Summary: Temporary Card Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- We are CONSTANTLY having to write out patron card numbers on post-its for patrons that forgot their library cards. It would be great if there were an option under the print options on the patron page to print a temporary card. It could print the barcode and number, and maybe have an optional customizable message. Even better, since patrons are prone to leave these lying around, maybe it prints a temporary number that ISN'T their card number, but it is a temporary secondary number linked to their account that expires in X amount of hours. We could hand that out to them, providing of course they provide a photo id to prove who they are. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

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