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

[Bug 29925] New: Add a 'set new password' page for patron's with expired passwords
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '22

30 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29925 Bug ID: 29925 Summary: Add a 'set new password' page for patron's with expired passwords Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Add a new page that will accept: 1 - Current password 2 - New password/confirmation 3 - Compare old and new password and confirm they are distinct, do not submit otherwise 4 - Save/update patron's password upon submission 5 - Update patron's password expiration -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 29926] New: Add ability for superlibrarians to edit password expiration dates
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '22

30 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29926 Bug ID: 29926 Summary: Add ability for superlibrarians to edit password expiration dates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org For single patrons and for patches we should allow the superlibrarian to set/update password expiration dates -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 23930] New: No permissions SSO login to staff client should redirect to a custom URL
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '22

29 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23930 Bug ID: 23930 Summary: No permissions SSO login to staff client should redirect to a custom URL Change sponsored?: Sponsored Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Presently if a patron tries to login to the staff client and they have insufficient permissions they are re-directed back to the Koha login page with the message: 'Error: You do not have permissions to access this page'. This is fine when the staff client authentication is the native Koha login, but when you have a SSO implemented then logging in via the Koha login page and then being re-directed to a native koha login form does not make sense. We'd like to implement a syspref InsufficientPermissionRedirectURL which the staff client re-directs to if the authenticating patron does not have permission to view the staff client. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 31148] New: Add link to MARC import tools from Cataloging
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '22

28 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31148 Bug ID: 31148 Summary: Add link to MARC import tools from Cataloging 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl While the MARC import tools are in the "Tools" module, they're strongly related to the Cataloging module. I think it would be good to have links from the Cataloging module page to the MARC import tools. We can wrap them in the same permissions that are used on tools-home.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 28125] New: All OPAC holds blocked when OPACHiddenItems contains incorrect values
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28125 Bug ID: 28125 Summary: All OPAC holds blocked when OPACHiddenItems contains incorrect values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 15448 >From bug 15448, we're now checking OPACHiddenItems to see if something is hidden before we allow a hold on it. However, the manner in which that check is performed causes a problem if the syspref contains incorrect values. To recreate: - make sure OPACHiddenItems is empty - find a holdable item on the OPAC, confirm you can place a hold on it - enter "itemlost: [AB]" in OPACHiddenItems (an incorrect value because itemlost can only contain 1 bit) - confirm your item is not hidden from the OPAC but you are told it is not available for holds You'll see the same behavior if you use an incorrect field name, like "lost" or "itemtype." Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15448 [Bug 15448] Placing hold on specific items doesn't enforce OpacHiddenItems -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[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 30039] New: Add published_on column to missing issues table on claims.tt
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30039 Bug ID: 30039 Summary: Add published_on column to missing issues table on claims.tt 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be handy if there was a 'Published on' column on the Missing issues table ( #claimst ) on claims.tt There is already a 'Since' column corresponding to serial.planneddate. Thh 'Published on' column would correspond to serial.publisheddate -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[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 30905] New: Show waiting recalls in patron account on checkouts tab
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30905 Bug ID: 30905 Summary: Show waiting recalls in patron account on checkouts tab 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 19532 When a hold is ready for pick-up we show this on the left in the patron account, so it cannot be missed easily. We should do the same for recalls. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19532 [Bug 19532] Recalls for Koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[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