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

[Bug 21472] New: Links in Additional Formats section of bib details do not work
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21472 Bug ID: 21472 Summary: Links in Additional Formats section of bib details do not work Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul(a)flo.org QA Contact: testopia(a)bugs.koha-community.org The links that appear under the heading Additional Formats, built using data from 776 fields, are hardcoded to be like this in the OPAC: /cgi-bin/koha/opac-search.pl?q=control-number:__________ And like this in the staff interface: /cgi-bin/koha/catalogue/search.pl?q=control-number:__________ The blanks are filled in with the contents of the 776 field, subfield $w, with any parenthesized organization code stripped. Thus, for example, a 776 field like this: 776 08 $i Online version: [...] $z 9781938168000 $w (OCoLC)895896190 Would yield a staff URL like this: /cgi-bin/koha/opac-search.pl?q=control-number:895896190 But that link won't work, at least not in our case; control numbers found in 035 $a are indexed as other-control-number, not control-number, and the organization code is not stripped when indexing. However, a link like this does retrieve the bib record with the 776 field given above: /cgi-bin/koha/catalogue/search.pl?idx=other-control-number,phr&q=(OCoLC)895896190 These links are built in /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/xslt/MARC21slim2OPACDetail.xsl (lines 808 ff.) and /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2intranetDetail.xsl (lines 756 ff.); for example, the latter looks like this:  <xsl:if test="marc:datafield[@tag=776]"> <span class="results_summary add_physical_form"> <span class="label">Additional physical formats: </span> <xsl:for-each select="marc:datafield[@tag=776]"> <xsl:variable name="linktext"> <xsl:choose> <xsl:when test="marc:subfield[@code='t']"> <xsl:value-of select="marc:subfield[@code='t']"/> </xsl:when> <xsl:when test="marc:subfield[@code='a']"> <xsl:value-of select="marc:subfield[@code='a']"/> </xsl:when> <xsl:otherwise> <xsl:text>No title</xsl:text> </xsl:otherwise> </xsl:choose> </xsl:variable> <xsl:if test="@ind2=8 and marc:subfield[@code='i']"> <xsl:call-template name="subfieldSelect"> <xsl:with-param name="codes">i</xsl:with-param> </xsl:call-template> <xsl:text>: </xsl:text> </xsl:if> <xsl:choose> <xsl:when test="marc:subfield[@code='w']"> <a> <xsl:attribute name="href"> <xsl:text>/cgi-bin/koha/catalogue/search.pl?q=control-number:</xsl:text> <xsl:call-template name="extractControlNumber"> <xsl:with-param name="subfieldW"> <xsl:value-of select="marc:subfield[@code='w']"/> </xsl:with-param> </xsl:call-template> </xsl:attribute> <xsl:value-of select="$linktext"/> </a> </xsl:when> <xsl:otherwise> <xsl:value-of select="$linktext"/> </xsl:otherwise> </xsl:choose> <xsl:if test="position() != last()"> <xsl:text>; </xsl:text> </xsl:if> </xsl:for-each> </span> </xsl:if> The template "extractControlNumber" extracts the control number (minus parenthesized prefix) from the value in 776 $w. Unfortunately, this template is used elsewhere so I'm not sure it's safe to change it so that it does *not* strip the parenthesized prefix. Perhaps we could add a second parameter to it that specifies whether or not to strip it, with the default set to true. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 22439] New: Duplicated code in PrepHostMarcField and prepare_host_field
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22439 Bug ID: 22439 Summary: Duplicated code in PrepHostMarcField and prepare_host_field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- The C4/Biblio.pm subroutines PrepHostMarcField and prepare_host_field both do the same thing, so should be merged. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70

[Bug 16122] New: Item record needs to keep Local Use count
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16122 Bug ID: 16122 Summary: Item record needs to keep Local Use count 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Like the "issues" field in the items table, there should be a field for "local_use" to keep the count of local uses. While this information is kept in the statistics table, it is a task to acquire, and if a library wants to keep bloat down on their tables, the statistics are pruned on a regular schedule, which means loss of valuable data. This counter would keep that valuable information in one field in each item record, rather than having a separate field for each instance in the statistics table. Unless it is vital to someone to know the exact moment a local use occurred, I am suggesting that this piece of information not be recorded in the statistics table any longer. This would significantly reduce the growth of the statistics table in general. Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 164

[Bug 26423] New: Cannot find patron with no cardnumber attached to hold, if HidePatronName system preference set
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26423 Bug ID: 26423 Summary: Cannot find patron with no cardnumber attached to hold, if HidePatronName system preference set Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When system preference HidePatronName is set, there is showing only patron cardnumber when looking at title holds. If patron has no cardnumber, there is showing nothing. There is no way to find the patron attached to hold. There should be a link to patron even when no cardnumber. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 19524] New: Share patron lists between staff
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19524 Bug ID: 19524 Summary: Share patron lists between staff Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jesse(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries would like to allow arbitrary lists to be used by all librarians with the 'manage_patron_lists' permission. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 18397] New: Sent notices for...: Display email address ( including which field it's taken from)
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18397 Bug ID: 18397 Summary: Sent notices for...: Display email address (including which field it's taken from) 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: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org Display in Home > Patrons > Sent notices for... the email address and the field where it is taken from. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 22263] New: Command line script to populate or update items.cn_sort
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22263 Bug ID: 22263 Summary: Command line script to populate or update items.cn_sort Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Sometimes cn_sort might be incorrect (wrong configuration when loading the items) or even empty (migration issue). It would be nice to have a script that allowed recalculating and updating the cn_sort field in items. This would be a maintenance script. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 26480] New: With UseControlNumber on, "Show analytics" link doesn't show on parent record
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26480 Bug ID: 26480 Summary: With UseControlNumber on, "Show analytics" link doesn't show on parent record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - turn off EasyAnalyticRecords - turn on UseControlNumer - find a bib, create a new child record from it - in the parent bib, confirm there is no "Show analytics" link - turn off UseControlNumber - confirm link now shows in parent record -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 25652] New: Holds Daily is not looking at Item Type when Not Allowing Holds
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '26

09 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25652 Bug ID: 25652 Summary: Holds Daily is not looking at Item Type when Not Allowing Holds Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 If a library has a rule that allows 5 holds daily on DVDs and 50 holds daily on the BOOK rule, Koha will count the first 5 holds regardless of item type and not allow any more of that item type (DVD) for a hold, but will allow more BOOK holds. 423 my $today_holds = Koha::Holds->search({ 424 borrowernumber => $borrowernumber, 425 reservedate => dt_from_string->date 426 }); Koha should be looking at Item Type when determining whether a hold can be placed in this today_holds search. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 17120] New: Specify number of rows per page in report and initial run
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '26

09 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17120 Bug ID: 17120 Summary: Specify number of rows per page in report and initial run Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I think we could enhance reports so that the &limit= parameter could be initially set with the report settings and stored in a field in the table. I also think we could have the drop down available on the parameters page when running the report the first time. If you have a report you know that would run well and could be completely shown with more rows, why not have the option to initially set it differently than the default? The LIMIT command in SQL is okay and works for actually limiting the total number of results, but does weird things if you specify a number larger than 20. The results still span multiple pages, plus it doesn't give you options while running like this would. -- You are receiving this mail because: You are watching all bug changes.

1 10