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

[Bug 28826] New: Facet sort order differs between search engines
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28826 Bug ID: 28826 Summary: Facet sort order differs between search engines Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In Zebra we sort the facets alphabetically by default - they are built in count order In Elasticsearch we display them as built, in count order There should be a configuration and we should sort them according to that -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 27155] New: Biblio and Item hooks should pass a deleted object on record deletion
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27155 Bug ID: 27155 Summary: Biblio and Item hooks should pass a deleted object on record deletion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org The biblio and item hooks now look up a record which is deleted already. We could pass the deletedbiblio or deleteditem? Especially on item deletion I am interested in receiving the biblionumber. The code for items differs between 19.11 and master. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 28510] New: Skip processing holds queue items from closed libraries when HoldsQueueSkipClosed is enabled
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '21

25 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28510 Bug ID: 28510 Summary: Skip processing holds queue items from closed libraries when HoldsQueueSkipClosed is enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests 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 Right now we skip closed branch's items as we iterate over all items looking for ones to fill a hold. If HoldsQueueSkipClosed is enabled, no items held be a closed library can be targeted, so it would be more efficient if we never selected the items from those branches to begin with. This is how the holds queue works if we are not using the transport cost matrix, so we should make it work the same way if we *are* using the matrix. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 28858] New: Table Settings should control Checked out by field in Circulation history
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '21

25 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28858 Bug ID: 28858 Summary: Table Settings should control Checked out by field in Circulation history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Koha Administration > Table Settings controls all whether fields are visible/can be toggled by users. 'Checked out by' is solely controlled by a system preference (RecordStaffUserOnCheckout) - and is not an option in the Table Settings controls. To replicate: - Set system preference: RecordStaffUserOnCheckout to 'record' - Check an item out to a patron - Go to that patron's Circulation history - cgi-bin/koha/members/readingrec.pl - Note that 'Checked out by' is visible and populated - Go to Koha > Administration > Table Settings - Choose Patrons - Choose Page: checkouthistory - Choose Table id: checkouthistory-table - Note that 'Checked out by' is not an option -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 28748] New: When hold is overridden cannot select a pickup location
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '21

23 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28748 Bug ID: 28748 Summary: When hold is overridden cannot select a pickup location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 28338 added a check of hold pickup locations for each hold item on a record When selecting an item that normally is not for hold there is no pickup dropdown, the hold is placed with no location To recreate: 1 - Enable AllowHoldPolicyOverride 2 - Set 'Default checkout, hold and return policy' - Hold policy 'From home library' Hold pickup library match 'Item's home library' 3 - Find a record with items from multiple libraries 4 - Attempt to place a hold on an item that normally wouldn't be allowed 5 - Notice these items have no holds dropdown 6 - Place the hold 7 - Note the pickup location is blank -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 28867] New: Use Bootstrap button menu and modal for adding patrons to lists
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28867 Bug ID: 28867 Summary: Use Bootstrap button menu and modal for adding patrons to lists Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 123858 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=123858&action=e… Screenshot showing Bootstrap button menu I propose to modify the patron search results page so that the controls for adding patrons to a new or existing list are Bootstrap style: A button menu for selecting a patron list, and a modal for entering the name of a new list. See attached. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 28047] New: Standardize: Call number, callnumber, Call no. etc.
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28047 Bug ID: 28047 Summary: Standardize: Call number, callnumber, Call no. etc. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We have various ways on how we use call number in the templates. It would help, also for translations, if we always used the same spelling/term. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 28084] New: Standardize: Cardnumber, Card number, Card
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28084 Bug ID: 28084 Summary: Standardize: Cardnumber, Card number, Card Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We have different spellings in the templates that could/should be standardized to one spelling to ease translation and documentation. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 16446] New: Allow librarians to add borrowers to lists by borrowernumber or cardnumber
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16446 Bug ID: 16446 Summary: Allow librarians to add borrowers to lists by borrowernumber or cardnumber Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice to be able to add borrowers to lists based on a supplied list of cardnumbers or borrowernumbers (that they could get from a report, for example). -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 28831] New: Results XSLT: Allow unavailable item grouping on status only for large consortia
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28831 Bug ID: 28831 Summary: Results XSLT: Allow unavailable item grouping on status only for large consortia 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 bug 26302: > 3 - Not blocker: it would be nice to have a '-1' option for > resultsMaxItemsUnavailable to preserve previous grouping - in large > consortia I know they have not wanted to display individual NFL items. This follow-up would make it possible to group by (sub)status and not on branch level first. -- You are receiving this mail because: You are watching all bug changes.

1 39