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

[Bug 11498] Prevent bypassing sco timeout with print dialog
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '25

10 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11498 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=40108 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 31642] New: Additional contents: Allow free text in location field for html blocks
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '25

10 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31642 Bug ID: 31642 Summary: Additional contents: Allow free text in location field for html blocks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org I ran into this limitation on e.g. bug 31503. I want to add locations that match authorised values for category CONSENT_TYPE. But Koha only allows a selected set of locations for html blocks. If we could allow picking a field from the combo or typing free text, we provide more flexibility in the use of this feature. Obviously this triggers a development discussion on field names. We have category, location and code. And their use becomes a bit unclear. Category is the most clear one. Although html and pages are quite similar. Location is opac or staff etc. for news and pages. But is used as a kind of block name for html_customizations. Code is used to group the records for default and translated languages for an item in all categories. The name is rather obscure. While describing this, bug 31383 comes to mind again.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 14479] Open 856 link in new tab
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '25

10 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14479 Gemma <gpanayi(a)rvc.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gpanayi(a)rvc.ac.uk --- Comment #5 from Gemma <gpanayi(a)rvc.ac.uk> --- I have also raised this in log 94446 as an issue for our staff. We would like the "856 to work in the same way in Koha as it behaves in Aspen, opening the resource in a new tab. Is it possible that this could be investigated again? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 40100] New: Label surname as last name in default language
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40100 Bug ID: 40100 Summary: Label surname as last name in default language Change sponsored?: --- Product: Koha Version: Main Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P1 - high Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, lucas(a)bywatersolutions.com CC: lucas(a)bywatersolutions.com According to the terminology page on the wiki (https://wiki.koha-community.org/wiki/Terminology) The Koha project uses American English. While it is technically correct, surname is not usually used in American English, last name is usually used. Since there are translations for UK English and NZ English, I propose the labels in the default interface should be Last name for American English. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 29872] New: Article requests: Include information on host record in article requests table
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29872 Bug ID: 29872 Summary: Article requests: Include information on host record in article requests table 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an article request is placed on an analytical record, it would be very helpful to display the information about the host record in the table of article requests. A first step would be to display the information from 773 and maybe create a search link for the record using the title or number from $w. If we can look-up the host record on server side, we could also provide a link with the biblionumber could also be provided. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 22265] New: Processing article requests requires borrowers permission
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22265 Bug ID: 22265 Summary: Processing article requests requires borrowers permission Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- I just noticed that you will only be able to see article requests if the staff patron has "borrowers" permission. You can still access the article requests page without the permission, but it will always show "no pending article requests". This dependency doesn't seem logical, especially since you can still access the page and it just seems like there are no requests. The problem seems to come from this part of the code: Koha::ArticleRequests: sub search_limited { my ( $self, $params, $attributes ) = @_; my $userenv = C4::Context->userenv; my @restricted_branchcodes; if ( $userenv and $userenv->{number} ) { my $logged_in_user = Koha::Patrons->find( $userenv->{number} ); @restricted_branchcodes = $logged_in_user->libraries_where_can_see_patrons; } # TODO This 'borrowernumber' relation name is confusing and needs to be renamed $params->{'borrowernumber.branchcode'} = { -in => \@restricted_branchcodes } if @restricted_branchcodes; $attributes->{join} = 'borrowernumber'; return $self->search( $params, $attributes ); } Not sure yet what the best way would be: Do we want to allow article request processing without borrowers? If no, we could hide article requests from view if the staff user doesn't have the required permission. If yes, what would be the consequence? (stuck on that one) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28652] New: Enforce maximum on article request charges
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28652 Bug ID: 28652 Summary: Enforce maximum on article request charges 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Just like we enforce a maximum charge for fines, rentals etc. we should not allow article request charges to pile up unlimited. See also bug 27946. Compare: maxoutstanding, OPACFineNoRenewals, MaxFine, noissuescharge, RentalsInNoissuesCharge. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20853] New: Show holding library for item level article requests
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20853 Bug ID: 20853 Summary: Show holding library for item level article requests 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice if more information about the item was shown for article requests on item level. At the moment the callnumber and the barcode is shown, but not all libraries assign unique callnumbers per item and not always barcodes for serial issues. It would be nice if we could at least show the holding library for the item. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20852] New: Make "All libraries" default organisation for article requests
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20852 Bug ID: 20852 Summary: Make "All libraries" default organisation for article requests 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At the moment the pick-up location a user selects in the OPAC will decide which library the article request shows up for in the interface. The tabs are organized by pick-up location. - There is no label stating it's the pickup location in the staff interface. - The pick-up library is not necessarily the library, that will the article request. So for processing new article requests the workflow is not ideal, as the library always has to switch to 'all libraries' in order to see requests they possibly have to process. As Koha allows article requests to be set on record level, Koha doesn't know which libraries might be able to fill the article request. So it might be best to optionally allow setting to "all libraries" and also adapt the note on the dashboard accordingly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 20684] New: Don't allow article requests on lost and missing items
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20684 Bug ID: 20684 Summary: Don't allow article requests on lost and missing items 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Article records on lost items or when all items are lost should not be possible. Maybe this could be changed into a general YAML based preference to rule out items by different criteria even (lost status, damaged status, collection). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2