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

[Bug 23036] New: Optionally order facets by result hits
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '21

05 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23036 Bug ID: 23036 Summary: Optionally order facets by result hits Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: jhannert(a)nmc.edu QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Facets on the left sidebar of the OPAC currently sort alphabetically. It would be nice to allow administrators the option to order them by number of results, with most hits at the top of the list. I understand that this, like the displayFacetCount preference, would be highly dependent on the value of the maxRecordsForFacets. Still, this type of sorting for facets is common in discovery systems and, I think, something our patrons expect. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 25838] New: Sort facets values by number of occurrences (Zebra)
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '21

05 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25838 Bug ID: 25838 Summary: Sort facets values by number of occurrences (Zebra) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Actually with Zebra facets values are sorted alphabetically. This is a comment from Bug 12478 : << Bug 12478: Display facet terms ordered by number of occurrences By default ES returns the facet terms ordered by most used, which makes sense. This patch removes resort done in the scripts (catalogue/search.pl and opac/opac-search.pl) and moves it to the module. For Zebra it's now done in C4::Search::getRecords, and there is no change to expect (still alphabetically). >> Looks like the sort by number of occurrences is already done in C4::Search::getRecords, it is an additionnal code that re-sort alphabetically. This patch proposes to remove it in order to have same sort order between Zebra and ES. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 22445] New: Ability to define a url for custom cover images
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '21

05 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22445 Bug ID: 22445 Summary: Ability to define a url for custom cover images Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- So far we have cover images from a list of webservices, COCE, locally, but we cannot define a custom url. -- You are receiving this mail because: You are watching all bug changes.

1 152

[Bug 25534] New: Add ability to send an email specifying a reason when canceling a hold
by bugzilla-daemon＠bugs.koha-community.org 04 Oct '21

04 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25534 Bug ID: 25534 Summary: Add ability to send an email specifying a reason when canceling a hold 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries would like to be able to cancel a hold with the option to specify a reason. Providing a reason would generate an email to that patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 125

[Bug 24488] New: Holds to Pull sometimes shows the wrong 'first patron' details
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '21

30 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24488 Bug ID: 24488 Summary: Holds to Pull sometimes shows the wrong 'first patron' details 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The query that pulls the information for the Circ -> Holds to pull table is incredibly complex and doesn't always pull the correct information. It has a bunch of commands in it that repeatedly reorders the results (group_concats and counts). This means the order of the results cannot be guaranteed to be the same with every execution, and sometimes we see the wrong 'first patron' for the given date selection. It's hard to test because it only happens sometimes, but I have been able to reproduce it this way: - Place two holds for two different patrons on the same biblio - Check the Holds to pull, it'll show the details of the first patron - Change the reservedate for the second hold in the database to be yesterday - Check the Holds to pull, it shows the details of the wrong hold under 'first patron' but shows the correct details 'under earliest hold date' - Change the date selection, it doesn't fix itself -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 211

[Bug 25727] New: Update the Select2 JS lib
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '21

29 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25727 Bug ID: 25727 Summary: Update the Select2 JS lib Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org In order to benefit from the last feature of Select we should upgrade to the version 4. For instance it adds the ability to dynamically create new entries https://select2.org/tagging -- You are receiving this mail because: You are watching all bug changes.

1 62

[Bug 20206] New: Should GetItemnumberFromBarcode ignore leading zeroes?
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '21

27 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20206 Bug ID: 20206 Summary: Should GetItemnumberFromBarcode ignore leading zeroes? 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org GetItemnumberFromBarcode will not find 51320 if it should be 051320. Could we need that? I noticed that Excel stripped leading zeroes and we got missing messages in Inventory. Anyone interested in a patch like the attached one? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 25003] New: Clearly identify when JavaScript errors are caused by OPACUserJS/IntranetUserJS
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '21

24 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25003 Bug ID: 25003 Summary: Clearly identify when JavaScript errors are caused by OPACUserJS/IntranetUserJS 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a page within Koha has been broken by code introduced via the UserJS sysprefs, we should make that clear in the browser console. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 23819] New: Allow status to be set during creation of a purchase suggestion
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '21

23 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23819 Bug ID: 23819 Summary: Allow status to be set during creation of a purchase suggestion Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Here is the workflow where this would be helpful: 1. Patron asks if we have a book. 2. Staff member checks in catalog that we don't have it, offers to make purchase suggestion. 3. Staff members fills out purchase suggestion and currently: Saves the suggestion and has to edit again to be able to edit status to "Sent to Adult Librarian" Would be nice if they could instead set that status on creation to reduce clicks. In this case 3 would say: 3. Staff member fills out purchase suggestion and sets status to "Sent to Adult Librarian" then saves purchase suggestion. Lisette -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24454] New: currency formatting from JS
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '21

23 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24454 Bug ID: 24454 Summary: currency formatting from JS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com API calls in OPAC brings raw JSON. We need a way to format data into the configured currency from JS. -- You are receiving this mail because: You are watching all bug changes.

1 28