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

[Bug 18317] New: Allow check out of already checked out items trough sip
by bugzilla-daemon＠bugs.koha-community.org 14 May '25

14 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18317 Bug ID: 18317 Summary: Allow check out of already checked out items trough sip Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: marianne.rolfsen(a)kul.oslo.kommune.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We see the need to have the ability to allow already checked out material to be checked out by an another patron automatically when using the automat (sip). Today a patron is not allowed to check out already checked out material when using the automat (sip).(In the staff client you can override this if you scan the barcode). There are several reason for allowing this: Case 1: If a patron, patron no.1, fails to deliver the item properly (the item is still on loan on his account) and the item is placed on the shelf where it belongs. The next patron(no.2) who picks it up and borrows it, can in this way correct the error of patron no.1 without contacting the staff. Today we risk that patron no.1 will receive fines even though he has delivered it. Or even worse patron no.2 has borrowed it (failed to see og ignored the message on the automat) and patron nr. 1 gets the fines. Case 2: If a patron has an item on loan that belongs to another branch, has no renewals left and wishes to borrow it again. He will be able to do so if there are no one on the waiting list. Because we have many branches that are open without any staff present, this feature is even more important. The patrons will be much more self-sufficient - also during the hours when the library is open but without staff. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 47

[Bug 24101] New: Due date to on-site loans according to the calendar and possibility to renew on-site loans
by bugzilla-daemon＠bugs.koha-community.org 14 May '25

14 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101 Bug ID: 24101 Summary: Due date to on-site loans according to the calendar and possibility to renew on-site loans Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: inkeri.hakulinen+bugz(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have reading rooms, where patrons can have their on-site loans available for them for a long time - even a year or more! (That is, if no one else needs that item in the meanwhile, and makes a hold for it.) We wish to be able to distinguish the on-site loans from the checkouts they take home. The on-site option is good for this, because it shows clearly to the patrons and to the staff that the loans are on-site. However, we need two improvements to Koha for this. First, we need the option to set the due date automatically according to the calendar and the circulation rules, taking into account the holidays and the loan period that is set to the patron and to the item. In addition, we need the option for the patrons to be able to renew their on-site loans, too. Now the on-site loans are non-renewable, so if the patron needs them longer than what is set to due date originally, it would be good for them to be able to renew the loans themselves through our OPAC. Now the renewal is impossible altogether. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 30845] New: OMNIBUS: Move holds checks into CanBookBeReserved/CanItemBeReserved
by bugzilla-daemon＠bugs.koha-community.org 14 May '25

14 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30845 Bug ID: 30845 Summary: OMNIBUS: Move holds checks into CanBookBeReserved/CanItemBeReserved 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 We have a number of holds checks: not for loan opacitemholds OPACHoldsIfAvailableAtPickup which are only checked in the script, and not our modules The api uses CanBook/CanItem BeReserved for checking validity of holds and is missing these checks We need to move the checks and cover them with unit tests -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 23232] New: Enable the option to use the onscreen keyboard on the basic cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23232 Bug ID: 23232 Summary: Enable the option to use the onscreen keyboard on the basic cataloguing editor 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: koha-bugs(a)lists.koha-community.org, m.de.rooy(a)rijksmuseum.nl, testopia(a)bugs.koha-community.org Depends on: 17178, 23231 Bug 17178 introduced the Mottie on screen keyboard https://github.com/Mottie/Keyboard for the advanced cataloguing screen. It would be helpful to have this option available on the standard editor as well. Catalogers may still have the requirement to enter foreign or special characters when in this mode. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17178 [Bug 17178] Add a popup/keyboard shortcuts for diacritics and symbols in the advanced cataloging editor https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23231 [Bug 23231] We display too many layout options for the onscreen keyboard in the advanced cataloguing editor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. You are on the CC list for the bug.

1 13

[Bug 29985] New: Cashup summary shows unexplainable odd amounts
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29985 Bug ID: 29985 Summary: Cashup summary shows unexplainable odd amounts 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com I performed some transactions testing bug 27779 in a fresh ktd instance. I used amounts like 4.50 or 10.00 or 1.55, nothing with more decimals, but I still ended up with this: Cash register: This is a register. Period: to 2022-01-31 21:22:40 Type Total Total 0.0499999999999998 Cash -0.0499999999999998 I have no idea how this can happen, since all amounts in my accountlines and account_offsets are only in 5 cent steps. With the patch from 27779 applies it also shows even amounts: Cash register: This is a register. Period: to 2022-01-31 21:22:40 Type Total Refund against Manual fee - 6 Refund against New card fee - 6 Manual fee 4.55 USB Stick 1.5 Total 0.0499999999999998 Cash -0.0499999999999998 As this should only be additions/subtractions, I have no idea how this could happen unless we have a bug somewhere? Also display should be using Price (CurrencyFormat) system preference, but it doesn't, display remains unchanged with FR option. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 31045] New: Add a housebound notification to staff interface
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31045 Bug ID: 31045 Summary: Add a housebound notification to staff interface Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Similar to the notification for curbside pickup or purchase suggestions, it would be nice to add a housebound delivery notification reminder. Otherwise staff would need to know, remember, or otherwise maintain a list of patrons who need housebound services outside of Koha. If combined with bug 26545 where patrons can update info or request a delivery through the OPAC, the overall module becomes much more useful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30380] New: No suggestions ASKED letter transported by email
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30380 Bug ID: 30380 Summary: No suggestions ASKED letter transported by email Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org C4/Suggestions line 487 calls GetPreparedLetter with status==ASKED in the letter code parameter, causing warning at line 583 in C4/Letters: No suggestions ASKED letter transported by email Since we have no ASKED notice, we should either check the status and not call Letters or add this notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 17643] New: The bug 3333 breaks intranet search results in column Location
by bugzilla-daemon＠bugs.koha-community.org 12 May '25

12 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17643 Bug ID: 17643 Summary: The bug 3333 breaks intranet search results in column Location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: christophe.croullebois(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The Bug 3333 corrects in Opac by setting notforloan=1. But it has a side effect on intranet search result page due to the use of authorized value on 'notforloan'. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 30723] New: Allow for notices to have custom header/footer includes
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30723 Bug ID: 30723 Summary: Allow for notices to have custom header/footer includes 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries like to add the same custom header/footer to many notices/slips. It would be handy if there was a way to set a custom header/footer and then call on it in each notice/slip where you'd like to have them. That way you would not have to add the same header/footer content to each notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 27730] New: Innocent changes to framework silently delete bibliographic data
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27730 Bug ID: 27730 Summary: Innocent changes to framework silently delete bibliographic data Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P3 Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: ian.bays(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you copy and change a framework and either delete a subfield in the new framework or mark the subfield tab as "ignore", then any bib data with data in that subfield, when saved in the new framework will be silently destroyed with no option to undo. Test Plan to confirm behaviour: 1. Create bib record in default framework with minimal data, but add tag 365 (as it has a number of subfields all visible) and populate subfields a through h with "fa" through "fh". Save the record and with sql check the contents of the metadata. (I found this SQL gives enough information substituting the correct bib number of the saved record: select tagfield, tagsubfield, frameworkcode, tab, hidden, (select ExtractValue(metadata, '//datafield[@tag="365"]/subfield[@code>="a"]') from biblio_metadata where biblionumber = 37002 and (select frameworkcode from biblio where biblionumber = 37002) = marc_subfield_structure.frameworkcode) tv from marc_subfield_structure where frameworkcode in ('', 'TEST') and tagfield = '365'; ) 2. Copy the default framework to a TEST framework and set (say 365$b to tab ignore and delete 365$d). (I used export the default framework to a csv, create new TEST framework and import from the saved default csv) 3. Edit the bib record and change framework to TEST framework (settings > change framework) and save the record. 4. Run the SQL again and observe the data from subfields b and d have both disappeared from the metadata. If you were to rerun these tests you may need to reload memcache to ensure the newly changed frameworks are picked up. I understand it has been broadly known by some long-term Koha users that deleting a subfield from the framework has this effect, but both these situations potentially cause bib data to be silently and permanently delated from the database. Many users will be unaware and may not discover the problem for some time. Potential solutions might include: a) For subfields not in the framework or with tab "ignore" allow the data to be saved as is on saving for edit; b) When selecting "change framework" detect if data would be lost and alert the user with an option to back out of the change without losing data; c) Do not allow deletion of a subfield from a framework and do not allow the "ignore" option for the tab. If a field is to be ignored but hidden there are plenty of visibility options in the framework. NB: The current delivered default framework has 13 subfields set to the "ignore" tab. I cannot see what purpose these serve as no data can survive within them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17