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

[Bug 18827] New: Elasticsearch mappings - not displayed or retrieved in saved order
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '23

07 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18827 Bug ID: 18827 Summary: Elasticsearch mappings - not displayed or retrieved in saved order Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The mappings listed under 'Biblios' and 'Authorities' are draggable - this allows ordering of fields. The ordering affects the id field in the search_marc_map table When retrieving for display or mapping we are not ordering by the this field. In general I am not sure if we are gaining anything with this ordering: https://www.elastic.co/guide/en/elasticsearch/guide/current/_sorting.html " When sorting on fields with more than one value, remember that the values do not have any intrinsic order; a multivalue field is just a bag of values. Which one do you choose to sort on?" I think we can switch to the idea that a single field per index should be chosen for ordering: author = 100 (only make this one sortable) author = 700 author = 245c or, in the case of authorities, we should expect a single field to populate the field for sorting (100, 110, 150 ... are alldefined as 'main-heading' - but each record should only have a single one of these field) -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 24709] New: Advanced editor - show space after delimiter visually
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24709 Bug ID: 24709 Summary: Advanced editor - show space after delimiter visually 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: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Catalogers would like to visually see if there is a space after the delimiter in the Advanced editor, much like what was done for Bug 24452 - Advanced editor - show multiple spaces visually -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 29849] New: Add ability to dismiss fund warning for a session
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29849 Bug ID: 29849 Summary: Add ability to dismiss fund warning for a session Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When setting up a fund, one can provide an amount and/or percentage of money expended beyond which to warn the user. Once that limit has been exceeded, all subsequent orders against that will generate a warning. It would be helpful to be able to dismiss this warning and have Koha remember that for the session, so subsequent orders against the same fund do not repeat the message. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26077] New: Batch Item Deletion Error Occurring Frequently with more than 5, 000 records
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26077 Bug ID: 26077 Summary: Batch Item Deletion Error Occurring Frequently with more than 5,000 records Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Submitting in response to an internal ticket from a library partner. We experience time out error messages when using the the batch item delete tool. Basically when attempting to delete anything more than approx 5,000 records. This has happen in the past and we were recently upgraded to 19.11. Can you adjust for us to have the ability to batch delete on a larger scale? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 24793] New: TinyMCE for HTML notices
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24793 Bug ID: 24793 Summary: TinyMCE for HTML notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, what do you think about TinyMCE editor for HTML notices? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31128] New: REST API item not_for_loan_status doesn't respect biblio level fallbacks
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31128 Bug ID: 31128 Summary: REST API item not_for_loan_status doesn't respect biblio level fallbacks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com Outside of the UI, the not for loan status is coded to fallback to biblio level not for loan settings if the item is found to be loanable at the item level. We should respect that in the API too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 32119] New: Cannot add new guarantee
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '23

04 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32119 Bug ID: 32119 Summary: Cannot add new guarantee Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 31422 Can't call method "id" on an undefined value at /kohadevbox/koha/members/memberentry.pl line 662 eval {...} at /kohadevbox/koha/members/memberentry.pl line 932 To recreate: go to a patron detail view, click "add guarantee" Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31422 [Bug 31422] Library limitations might cause data loss when editing patrons -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 28658] New: With SearchMyLibraryFirst if library isn't set for the opac, try to guess it by checking branchip
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '23

03 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28658 Bug ID: 28658 Summary: With SearchMyLibraryFirst if library isn't set for the opac, try to guess it by checking branchip Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org If the SearchMyLibraryFirst syspref is set, the OPAC uses the logged in users branchcode to limit searches to their library. If it's an anonymous session that doesn't happen. This tries to guess the client library by checking for the client ip address in each libraries branchip setting. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 25631] New: Adding ability to alter the expiration date of the hold from the Patron's Account
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '23

03 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25631 Bug ID: 25631 Summary: Adding ability to alter the expiration date of the hold from the Patron's Account Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, for a hold expiration date to be changed, it would need to happen from the Item's Record (Hold), or the patron themselves can edit/add an expiration date. It would be nice to be able to add/edit an expiration date to the patron's hold from their Holds Summary on the Patron detail page. members/moremember.pl circ/circulation.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 27311] New: Don't pass borrowernumber to check_password plugin hook
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '23

03 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27311 Bug ID: 27311 Summary: Don't pass borrowernumber to check_password plugin hook Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org check_password is implemented in two places: 1. In Koha::Patron::set_password https://git.koha-community.org/Koha-community/Koha/src/branch/master/Koha/P… 2. In Koha::Patron::store https://git.koha-community.org/Koha-community/Koha/src/branch/master/Koha/P… The call to the plugin inside Koha::Patron::store comes before this line: $self = $self->SUPER::store; which means there is not yet a borrowernumber to pass to the plugin, and this never worked. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8