January 2022 - Koha-bugs - lists.koha-community.org

[Bug 29094] New: Placing holds via SIP2 does not check if a patron can hold the given item
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29094 Bug ID: 29094 Summary: Placing holds via SIP2 does not check if a patron can hold the given item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When placing holds via SIP2, there is no holdability check. This seems very incorrect. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 26377] New: Clearly label parts of subscription-add.pl that relate to optional item records
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26377 Bug ID: 26377 Summary: Clearly label parts of subscription-add.pl that relate to optional item records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com On the first screen of subscription-add.pl, there are several fields that set values to be applied to created items. They're only needed if you are creating item records when receiving serials. It'd be very helpful to move these so that they are all grouped together and clearly labeled. It might even be reasonable to hide them if not set to create item records. These fields relate to the item record: - Call number - Library - Location - item type - item type for older issues -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 29632] New: Callnumber sorting is incorrect in Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29632 Bug ID: 29632 Summary: Callnumber sorting is incorrect in Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com It looks like we are not sorting cn_sort as a raw field, but sorting the analyzed version. To recreate: 0 - Be using ES with Koha 1 - On records with single item, add callnumbers: VA65 E7 R63 1984 VA65 E7 T35 1990 VA65 E45 R67 1985 2 - Add public note 'shrimp' or something to make them easily searchable as a group 3 - Search for 'shrimp' 4 - Note E45 comes last, it should come first Problem may be here: 1122 sub _sort_field { 1123 my ($self, $f) = @_; 1124 1125 my $mappings = $self->get_elasticsearch_mappings(); 1126 my $textField = defined $mappings->{data}{properties}{$f}{type} && $mappings->{data}{properties}{$f}{type} eq 'text'; 1127 if (!defined $self->sort_fields()->{$f} || $self->sort_fields()->{$f}) { 1128 $f .= '__sort'; 1129 } else { 1130 # We need to add '.raw' to text fields without a sort field, 1131 # otherwise it'll sort based on the tokenised form. 1132 $f .= '.raw' if $textField; 1133 } 1134 return $f; 1135 } We need to enforce raw for cn-sort, or we need to index it unanalyzed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 26751] New: Fatal exception if only one repo defined
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26751 Bug ID: 26751 Summary: Fatal exception if only one repo defined Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It seems that it always expects an array. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 24633] New: Add support for gitlab searching of plugins
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24633 Bug ID: 24633 Summary: Add support for gitlab searching of plugins Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org As the title says, add support for gitlab to the work started in bug 23975 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 24634] New: Support display of changelog files for plugins
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24634 Bug ID: 24634 Summary: Support display of changelog files for plugins Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Well maintained plugins should include a changelog file in their package. We should support displaying this changelog from the plugin management pages. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 24635] New: Support display of readme files for plugins
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24635 Bug ID: 24635 Summary: Support display of readme files for plugins Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org Depends on: 23975, 24634 Well maintained plugins should include a readme file in their package. We should support displaying this readme from the plugin management pages. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23975 [Bug 23975] Add ability to search and install plugins from GitHub https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24634 [Bug 24634] Support display of changelog files for plugins -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 19684] New: Colon char in MARC data breaks facets
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '22

25 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19684 Bug ID: 19684 Summary: Colon char in MARC data breaks facets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When a MARC data used in some facet contains colon char ":", this facet is broken it leads to no result. This is because all colon are replaced by = which is a CCL syntax char -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 26931] New: Volumes tab should show all volumes
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '22

23 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26931 Bug ID: 26931 Summary: Volumes tab should show all volumes 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 24857 This may want to just get folded into 24857, but filing separately to start. In the volumes interface defined by 24857, we haven't explicitly defined how many volumes to show or how to paginate them, so if you have volumes in excess of your RESTdefaultPageSize syspref those volumes cannot be seen. We should make it show them all. Or paginate, but showing them all would be more consistent with other bits of the catalog. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24857 [Bug 24857] Add ability to create "Volumes" for records, and assign items to volumes -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 26276] New: When merging biblios with volumes, preserve all volumes
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '22

23 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26276 Bug ID: 26276 Summary: When merging biblios with volumes, preserve all volumes 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When merging bib records with attached volumes, only the volumes connected to the preserved biblionumber are kept. To recreate: - create bib Test 1 - create Volume 1 on bib Test 1 - create bib Test 2 - create Volume 2 on bib Test 2 - select bibs Test 1 and Test 2 for merge - selet Test 1 as the bib number to be maintained - complete merge - confirm your final bib has just one volume, Volume 1 We should keep all volumes, merging them all into the final bib. Additionally, and volume-level holds on the deleted bib do merge onto the final bib, but end up as bib-level holds. They should be kept as volume-level. Could be this wants to be a separate bug. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3