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

[Bug 30293] New: ODS report download inserts apostrophe in front of numerical results
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30293 Bug ID: 30293 Summary: ODS report download inserts apostrophe in front of numerical results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When numerical report results are downloaded as ODS format, an apostrophe is inserted in front of the numbers. The result of this is that most functions in spreadsheet programs will not work since the software then doesn't consider those values numbers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 30332] New: SRU does not work via https
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30332 Bug ID: 30332 Summary: SRU does not work via https Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I tried to add an SRU service for https://www.obvsg.at/en/catalogues/access-via-sru. They only provide access via https. So I set it up like this: Server name: OBVSGT Hostname: https://services.obvsg.at Port: 443 Database: sru/OBV-LIT Additional SRU Options: operation=searchRetrieve, sru=get, sru_version=1.1 SRU search field mappings: title=alma.title,isbn=alma.isbn,srchany=alma.all_for_ui,author=alma.creator,issn=alma.issn,subject=alma.subjects,dewey=alma.dewey_decimal_class_number This produces a valid URL when calling _create_connetion in C4::Breeding. But the SRU API always returned errors: 235 Database does not exist. So I tried to figure out what Koha is actually sending, but failed, because this seems to happen in some C code via ZOOM. But we have a lot of working SRU setups via plain http. So I hacked up a quick proxy, launched that on a non-https port, and now it works. So I assume that Zoom has a problem with https, which is very annoying, because more and more services will switch to https only in the future (or already have switched) Any ideas what to do here? I will attach my proxy script in a minute, so you can see for yourself... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 20200] New: Show MARC 770 Supplement/Special Issue Entry on detail pages
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '22

16 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20200 Bug ID: 20200 Summary: Show MARC 770 Supplement/Special Issue Entry on detail pages 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Currently 770 is not shown in Koha on the detail pages. We should add the display of this field. Examples: 770 08 _iAnfangs darin, später selbst. _aGesellschaft für Verbreitung von Volksbildung _tJahresbericht der Gesellschaft für Verbreitung von Volksbildung _dBerlin, 1872 _w015234347 770 08 _iBeil. ab 1902 _aDie Volks-Bibliothek _dBerlin, 1896 _w014944286 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 27901] New: cancelling acq order does not delete item record, causes error
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '22

16 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27901 Bug ID: 27901 Summary: cancelling acq order does not delete item record, causes error Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Prior to 20.05 when an order was cancelled from the basket, the item created when the order was placed was deleted also. In 20.05, users now get the message: An error has occurred. The order has been cancelled, although one or more items could not have been deleted. To recreate: 1. Add biblio and item to basket 2. Cancel the order and delete the biblio 3. Get the error message 4. Verify that the Holdings table still shows the item, but the acq correctly shows the cancellation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 30730] New: Holds to Pull should not list items with a notforloan status
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '22

16 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30730 Bug ID: 30730 Summary: Holds to Pull should not list items with a notforloan status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, nick(a)bywatersolutions.com The holds to pull list (pendingreserves.pl) is mistakenly showing titles where there are no available items and telling staff to pull items with negative notforloan statuses that should keep them off the list. To recreate: - have a bib with 2 items, both holdable. Give one of these items a notforloan status with a negative value (like Ordered in the testing docker data). - place a title-level hold on your bib - confirm your bib is showing on Holds to Pull as expected, prompting staff to pull the item that does not have a not for loan status (correct!) - take the item that does not have a not for loan status and check it out to a different patron, make sure not to fill or cancel your hold - reload Holds to Pull, see your title is still listed and now Koha is directing staff to the item with a notforloan status In building this list, we start by getting only the bibs that have at least one holdable item, but then we neglect to actually exclude the non-circulating items from the final output. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 30935] New: Holds to pull shows wrong first patron
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '22

16 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30935 Bug ID: 30935 Summary: Holds to pull shows wrong first patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I've seen a couple of bugs on this and they're all 'Resolved' but I still see the problem. Maybe it's not the exact same thing... So I'm creating this in case. Someone else can test and tell me if I'm crazy or not. When a biblio has more than one hold (record-level), the 'First patron' column on the 'Holds to pull' report is not showing the actual first patron, but the last in the line. I tried it on a bywater sandbox, just in case it was my installation that was the problem, and it does the same thing. To test : 1) Place a record-level hold on a biblio with an available item 2) Check the Holds to pull page (circ/pendingreserves.pl) --> The biblio should appear in the list and the patron should appear in the 'First patron' column 3) Place a second record-level hold on the same biblio 4) Go back to the Holds to pull page --> The biblio is still there, but the patron in the 'First patron' column is the second patron 5) Place a third record-level hold on the same biblio 6) Go back to the Holds to pull page --> The biblio is still there, but the patron in the 'First patron' column is the third patron Other bugs I found that talk about this: Bug 24488 (Closed fixed), Bug 30337 (pushed to master) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 26835] New: Ability to remove Lost Items from Patrons Account without Checking in
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '22

16 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26835 Bug ID: 26835 Summary: Ability to remove Lost Items from Patrons Account without Checking in Change sponsored?: --- Product: Koha Version: master 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 Libraries all have unique ways of handling lost statuses. At the moment, Koha allows libraries to remove a lost item from the patron's account when set to a lost status and also to not remove it. Great! However, we would like to see Koha go one step forward after the library chooses to not remove the lost item from the patron's account, to allow for the item to be removed at a later date. A preference would be to have the Batch Item Modification allow for libraries to change an item's lost status to another lost status, and also remove it from the patron's account. Using the batch item modification will allow for libraries to do this operation in bulk ! Currently, if a library has the option to credit the patron if they do return a lost item, the library has no way of telling Koha (at check-in) don't refund, don't remove the lost status, just remove it from the patron's account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 23541] New: Duplicate Hold Notifications
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '22

15 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23541 Bug ID: 23541 Summary: Duplicate Hold Notifications Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In 18.11, it was reported that library patrons from several libraries were receiving duplicate hold notifications. This is not performing consistently, and hard to reproduce. Both Firefox and Chrome browsers have performed the same way. It would appear that the hold request has been sent twice and unfortunately, it can't be determined what is causing this. The patrons that have received duplicate hold notifications don't consistently get the duplicate hold notification, it is quite random. This duplicate hold notifications are occurring in Email form and a variety of email providers are doing this. These duplicate hold notifications are happening on holds on the shelf and checked in holds, this is happening sporadically during the day. The libraries that have reported this are not using SIP devices and only one is using a RFID scanner. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 30314] New: Microsoft font makes extra space in OPAC with Chrome, Edge, and Vivaldi browsers
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '22

15 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30314 Bug ID: 30314 Summary: Microsoft font makes extra space in OPAC with Chrome, Edge, and Vivaldi browsers Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Browser compatibility Assignee: oleonard(a)myacpl.org Reporter: frank(a)sydt.com.tw QA Contact: testopia(a)bugs.koha-community.org Created attachment 131850 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131850&action=e… Compare issue between Firefox and other browsers Dear All, We found an issue when using Microsoft font like the attached file in OPAC. When we set the font from Microsoft to Google font. The problem is fixed. The engineer said those browsers who had this issue, within the code, found an extra "user agentstylesheet" from Google. It seems not to influence the system work, but one Koha user reports this to us. So, we also report here and hope it is not a serious problem for all Koha users. Best regards, Frank Chou Shou Yang Digital Technology Co., Ltd. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 28420] New: Allow login via AzureAD OpenID-Connect
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '22

14 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28420 Bug ID: 28420 Summary: Allow login via AzureAD OpenID-Connect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: mark.jaroski(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi, At the World Health Organization our South-East Asian regional office uses Koha for their regional library, with access by all WHO staff in the region and selected staff worldwide. Since local user databases can present a security risk we require that all applications for staff be integrated with our identity provider which at the moment is Microsoft's AzureAD. AzureAD uses OpenID-Connect and is mostly drop-in compatible with Google's implementation, with the exception that in order to construct the URLs both for redirection and for validation you need to know the organization's Azure tenant ID. Because our system integrator is not interested in pursuing this integration I've taken it on myself, and so I've set up a development environment and have started working on the code. My plan is to set up the configuration parameters and to then use them in a very slightly altered copy of the current googleopenidconnect file. I think in the long run it would be better to have a generic OpenID-Connect configuration to allow integrations with other providers like Okta and OneLogin, but we don't need for the moment that so for now I'll just add the AzureAD provider. I'll read up on the rest of the contribution procedure, and I'll be back with a patch/PR in a few days. Best, Mark -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28