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

[Bug 21255] New: memberetnry.pl is missing categories in the Category pull-down list
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '23

08 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21255 Bug ID: 21255 Summary: memberetnry.pl is missing categories in the Category pull-down list Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cnighswonger(a)foundations.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In some instances, when editing a patron, the Category pulldown under the "Library management" section is missing categories. I'm at a loss as to how to accurately describe the problem, but here goes: 1. The given patron's category shows up correctly on every other screen. 2. Navigating to the Patron Detail screen and selecting the edit option for Library use section results in the Modify Patron screen. 3. The heading on the Modify Patron screen displays the correct category. 4. However, the Category pulldown does not. 5. Furthermore, the pulldown does not even contain the correct category for the given patron. Doing a bit of looking around turned up a few things which may or may not be related. For the given patron: 1. The problem seems to be with the child category. 2. The Koha::Patron::Categories object may contain missing or incorrect category information. Here is a snip of the object returned for the 'C' category type by this line http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=members/memberent… 'attrs' => { 'bind' => [], 'join' => 'categories_branches', 'order_by' => [ 'categorycode' ], 'where' => { 'category_type' => 'C', 'categories_branches.branchcode' => [ 'JL', undef ] }, 'alias' => 'me' }, 3. The underlying data appears to be sound. 4. This was not a problem prior to upgrading a month ago. Unfortunately, I'm not sure what version this system was at prior to the upgrade. Maybe this will get the discussion started and someone with more knowledge of this area of the code can give some direction to it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 29755] New: SIP2 code does not correctly handle NoIssuesChargeGuarantees or NoIssuesChargeGuarantorsWithGuarantees
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '23

07 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29755 Bug ID: 29755 Summary: SIP2 code does not correctly handle NoIssuesChargeGuarantees or NoIssuesChargeGuarantorsWithGuarantees Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The sip code always checks noissuescharge as the limit for fines, never the other possible limits -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 23580] New: Add C4::Context->yaml_preference
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '23

06 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23580 Bug ID: 23580 Summary: Add C4::Context->yaml_preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I propose to add a way to retrieve the decoded YAML from (YAML) system preferences. This way we don't need to write code in vain for decoding them in-place. Also, I propose we move pipe-separated sysprefs into YAML lists. This raised on reviewing 22996. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 33376] New: Adding the option to modify/edit searches on the OPAC
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '23

06 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33376 Bug ID: 33376 Summary: Adding the option to modify/edit searches on the OPAC 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org We know have an "edit search" option on the staff interface, but it would be arguably more useful on the OPAC. Locally, I've had an edit search on the OPAC for years. Perhaps I should look at upstreaming that... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 33378] New: OPAC advanced search limits and OPAC facets no longer correspond
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '23

06 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33378 Bug ID: 33378 Summary: OPAC advanced search limits and OPAC facets no longer correspond 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you choose an advanced search limit in the OPAC of the item type "Books", that facet won't be selected in the OPAC search results. This appears to be due to a small change in what search qualifiers are used... -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 32728] New: ERM - Search header should change to match the section you are in
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '23

05 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32728 Bug ID: 32728 Summary: ERM - Search header should change to match the section you are in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: david(a)davidnind.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com The ERM module search header has three options: Search agreements, Search packages, and Search titles. If you click through the sidebar options (Agreements, Packages, and Titles) the search header doesn't change to reflect the area you are in. If you change the header to another option, for example 'Search titles', then perform a search, the header goes back to 'Agreement search'. To replicate: 1. Enable the ERM module: ERMModule system preference. 2. Go to the ERM module: Home > E-resource management. 3. Select the options from the sidebar menu (Agreements, Packages and Titles), and note that the ERM search header options don't change. 4. Add a minimal agreement, package and title. 5. Change the search header to another option, for example 'Search titles', then perform a search. Note that: - the appropriate sidebar menu option is highlighted, for example: 'Titles' - the search header changes back to 'Agreement search' This was noted as a potential issue when testing bug 32683 - Convert header search tabs to Bootstrap. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 28609] New: Popularity sort is broken
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '23

05 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28609 Bug ID: 28609 Summary: Popularity sort is broken Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de Bug 13976 reported that the sort by popularity was only alphabetic and not numeric. I cannot confirm that... because now it's broken. When sorting by popularity the result list is sorted by biblionumber instead, which is the usual fallback when values are identical. When searching issues:74 or popluarity:74 records where the items have this number of issues are found correctly. So it appears the index is there and filled, but somehow not working when used for sorting? Verified in 18.11 and 20.11. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 33125] New: 2nd sorting level of titles in results lists should be configurable
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '23

05 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33125 Bug ID: 33125 Summary: 2nd sorting level of titles in results lists should be configurable Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: anke.bruns(a)gwdg.de QA Contact: testopia(a)bugs.koha-community.org The sort order in the OPAC is year (008) and then biblionumber (ASC). This means that in a result list with more than one title matching the first sort criterion, the earlier entries usually appear before the more recent ones. (Exceptions are possible, of course, if a title from an earlier publication year is catalogued after titles published later). The criteria for the first sorting level are configurable in the system preferences OPACdefaultSortField and OPACdefaultSortOrder. Currently there seems to be no way to configure the 2nd sorting level. Not sure whether this is a Zebra only issue. Suggestion: Add system parameter to configure the second sorting level, similar to those for the 1st level mentioned above. Alternatively: sorting by biblionumber on the 2nd level should be descending instead of ascending so newer (more recently catalogued) titles appear before older ones. Steps to Reproduce: Prerequisites: - A Koha OPAC (perhaps Zebra is required?) - First sort criterion must be functional, so if it is the publication year, the year must be present in positions 7-10 in the 008 field of the records. To reproduce: - Search for something with more than one result matching the first sort criterion, e.g. search for all titles published in a specific year. Actual Result: - In the results list the titles from the same year appear in ascending order of their biblionumbers. Expected Results: - Either: the titles appear in descending order of biblionumber - Or: the second sorting level (criterion and asc/desc order) is configurable in additional system parameters similar to OPACdefaultSortField and OPACdefaultSortOrder. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 25939] New: Print multiple copies with quick spine label creator
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '23

04 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25939 Bug ID: 25939 Summary: Print multiple copies with quick spine label creator Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For libraries that purchase several copies of the same title, it'd be nice to have a quicker way to print several copies of the same spine label. Maybe something on spinelabel-home.pl that would let the user specify a number of copies? -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 29174] New: Availability colors are not consistent in the codebase
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '23

04 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29174 Bug ID: 29174 Summary: Availability colors are not consistent in the codebase Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org OPAC Results has three blocks: Available for loan, Available for reference (a subset of some not for loan categories, see pref Reference_NFL_Statuses and Not available (some not for loans, checked out, damaged, etc) The not available group is RED, the two available groups are GREEN. At least talking about opac-search. (And opac-shelves too.) But now we still need to address a few other spots where we use these colors: opac-detail shows the reference items RED! opac-basket does the same. Would you know more code locations? It seems that staff already uses another algorithm to choose for RED. On catalogue detail red is used only for damaged, lost, etc? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3