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

[Bug 18017] New: [Unimarc] Importing biblios from Z39.50 servers duplicates related authorities
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18017 Bug ID: 18017 Summary: [Unimarc] Importing biblios from Z39.50 servers duplicates related authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is a unimarc bug only: When importing biblios from Z39.50, related authorities are wrong matched by the linker. This causes duplicates of authorities. The problem come from a bad marc definition in unimarc/authorities/authority-koha-indexdefs.xml which does not create a index for matching an entire heading. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 26234] New: Default DataTables must know our own classes
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '21

07 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26234 Bug ID: 26234 Summary: Default DataTables must know our own classes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org We have different classes we can use to set specific behaviours on table columns: title-string, string-sort, anti-the and NoSort. We should not need to pass them to the DataTable constructor, we could teach it that we always want to apply them. It will avoid bug like bug 26233 -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 16825] New: Add API route for getting an item
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '21

06 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16825 Bug ID: 16825 Summary: Add API route for getting an item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: larit(a)student.uef.fi QA Contact: testopia(a)bugs.koha-community.org Add API route for getting an item GET /api/v1/items/{itemnumber} Gets one Item -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 93

[Bug 24699] New: Split items.uri on OPAC detail page
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '21

06 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24699 Bug ID: 24699 Summary: Split items.uri on OPAC detail page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org See 24697 (counterpart) -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 25728] New: Add the ability to create a new authorised value within the cataloguing module
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '21

05 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25728 Bug ID: 25728 Summary: Add the ability to create a new authorised value within the cataloguing module 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 If you are editing a bibliographic record, then you realised that you need a new authorised values, you have to go to the admin module, and reload the page. It would be handy to create it directly from the cataloguing module. -- You are receiving this mail because: You are watching all bug changes.

1 70

[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 01 Oct '21

01 Oct '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