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

[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 22938] New: Public Notes on an Item that are on Course Reserve to show up on catalogue/detail.pl page
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '25

04 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22938 Bug ID: 22938 Summary: Public Notes on an Item that are on Course Reserve to show up on catalogue/detail.pl page Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently, when a public note is added to an item when it is put on Course Reserve, this public note is only visible when the user is seeing this item in the Course Reserve module course-details.pl or the OPAC opac-course-details.pl. It would be very helpful to also see this public note from the detail.pl page for circulation staff. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 27935] New: Allow item search fields to be defined from database fields rather than MARC tags
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27935 Bug ID: 27935 Summary: Allow item search fields to be defined from database fields rather than MARC tags Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The item search fields interface allows one to specify MARC tags to be used as custom search fields. It'd be handy to also have the option of specifying database fields, for the various bib/item values that don't get stored in the MARC. This would be handy for folks who don't or can't use reports and therefore rely on item search. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 23781] New: SMS and messaging preferences for recalls
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23781 Bug ID: 23781 Summary: SMS and messaging preferences for recalls Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Add the option for users to receive notices by SMS for recalls. This requires adding recalls to messaging preferences. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 87

[Bug 25901] New: Add option for ClaimsReturnedWarningThreshold to count only unresolved claims
by bugzilla-daemon＠bugs.koha-community.org 28 May '25

28 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25901 Bug ID: 25901 Summary: Add option for ClaimsReturnedWarningThreshold to count only unresolved claims 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Coming out of conversation on bug 25733, some libraries would like this threshold to only count claims that have not been resolved. I think this will need to be another syspref. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17