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

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

[Bug 21060] New: Article requests: Null borrowernumber when borrower is deleted and keep request data for statistics
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21060 Bug ID: 21060 Summary: Article requests: Null borrowernumber when borrower is deleted and keep request data for statistics 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 When a patron is deleted the article requests will also be deleted. This can leave holes in statistics. It would be nicer to cancel them and null the borrowernumber instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 20973] New: Article requests: Can't tell which library filled an article request
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '25

09 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20973 Bug ID: 20973 Summary: Article requests: Can't tell which library filled an article request 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, kyle(a)bywatersolutions.com In a multi branch setting any library might fill an article request, but at the moment only the pick-up library is stored. There is no way to tell which library actually filled the request which is important for statistics. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 21697] New: Free-floating subdivision cannot be manage correctly in Koha
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '25

06 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21697 Bug ID: 21697 Summary: Free-floating subdivision cannot be manage correctly in Koha Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: hector.hecaxmmx(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Koha doesn't have right authority frameworks to deal with free-floating subdivisions records 180, 181, 182, and, 185. These fields needs their own frameworks to work properly an to be searchable headings. When you prepare this kind of records in ISO2709 file and export them to Koha, Koha treat well as free-floating subdivisions but there aren't frameworks to deal with. So the heading are stored but not searchable. You can see this in module C4::AuthoritiesMarc lines 350-367 sub GuessAuthTypeCode { my ($record, $heading_fields) = @_; return unless defined $record; $heading_fields //= { "MARC21"=>{ '100'=>{authtypecode=>'PERSO_NAME'}, '110'=>{authtypecode=>'CORPO_NAME'}, '111'=>{authtypecode=>'MEETI_NAME'}, '130'=>{authtypecode=>'UNIF_TITLE'}, '148'=>{authtypecode=>'CHRON_TERM'}, '150'=>{authtypecode=>'TOPIC_TERM'}, '151'=>{authtypecode=>'GEOGR_NAME'}, '155'=>{authtypecode=>'GENRE/FORM'}, '180'=>{authtypecode=>'GEN_SUBDIV'}, '181'=>{authtypecode=>'GEO_SUBDIV'}, '182'=>{authtypecode=>'CHRON_SUBD'}, '185'=>{authtypecode=>'FORM_SUBD'}, }, NOTE: These records are not usable in biblio records but serves to librarians to take decision when creating complex-headings. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 22501] New: OPAC course reserves notes should allow html links
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '25

05 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22501 Bug ID: 22501 Summary: OPAC course reserves notes should allow html links Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Some libraries have been using the public notes field to point to electronic resources, this functionality has been removed by HTML filtering the content. We should allow the use of a $raw filter on these fields as they can only be entered by staff -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 18676] New: Optionally delete fast add items and records on return
by bugzilla-daemon＠bugs.koha-community.org 27 May '25

27 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18676 Bug ID: 18676 Summary: Optionally delete fast add items and records on return 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 In some libraries fast adds are used for ILL or other material that's not supposed to stay in the catalog after circulation was completed. It would be nice if there as an option to automatically delete fast add items and records (if it was the last item) when the item is checked-in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 20258] New: Offer circcontrol options at library level rather than at system-wide level.
by bugzilla-daemon＠bugs.koha-community.org 27 May '25

27 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20258 Bug ID: 20258 Summary: Offer circcontrol options at library level rather than at system-wide level. Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The following is a slight simplification of our complex structure, but it outlines how Koha is not offering us a 100% satisfactory circulation experience. We have 6 college libraries all marked as closed in weekends, with users permitted to borrow (let’s say for simplification) a maximum of 15 items from across the 6 libraries. (All loan rules are the same at all 6 college libraries). All users belong to one of these libraries. Our new kit-loaning library has opened 24/7 and it offers a loan of one laptop and loans of up to three accessories (headphones etc.) with a loan period of 4 hours. No users belong to this library. Policy is to allow loans from this library to be in addition to loans from the normal 6 libraries. Having circcontrol set to either the rules from where the item is from, or the library the user is logged in at both fail to work as (even ignoring the new library) the maximum loans increases from 15 overall to 15 per library (6*15=90)- totally unacceptable here. The only option for now has been to set circcontrol to use the rules applicable to the library the user is from. This fails in two ways. Loans from the 24/7 library made at weekends are being pushed out as due on Monday (as all the libraries consulted for rules are marked as closed). Additionally the only way to allow the loans from the 24/7 library to be additional to the 15 maximum, has been to increase the maximum loans to 15+4=19. Users can of course now take 19 items out from the six main libraries, as the loan entitlement is not being compartmentalized. Option 1. We continue to put up with what we have. Option 2. We set up a second instance of Koha for only the 24/7 library, or source another product to manage loans from that library. Option 3. Move circcontrol to the library level, leave the 6 libraries with circcontrol at each library using the rules for where the user is from, and lower the maximum loans to 15 at each library. Change circcontrol for the 24/7 library to use circcontrol set to use the rules for the library the user is logged in at (or possibly where the item is from). With the calendar for the 24/7 being consulted now the weekend loan period would be right, and the loans maxima should also be right (15 from the six college libraries plus 4 for the 24/7 library using the different circcontrol. Can anyone offer any other alternatives? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3