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

[Bug 29470] New: MARC21: Display 583 $x nonpublic note in staff interface
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '23

08 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29470 Bug ID: 29470 Summary: MARC21: Display 583 $x nonpublic note in staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In 583 there is a nonpublic note subfield that could be displayed on the detail page in the staff interface. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 24609] New: Add routes for getting and setting checkout due date
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '23

07 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24609 Bug ID: 24609 Summary: Add routes for getting and setting checkout due date 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: andrew.isherwood(a)ptfs-europe.com To allow the work in bug 24608 to proceed, we need an API route to allow the setting of a checkout's due date. I will add a GET route also. The proposed endpoints are: Return a checkout's due date: Method: GET URL: /checkouts/{checkout_id}/date_due Set a checkout's due date: Method: POST URL: /checkouts/{checkout_id}/date_due Body: { date_due: '2020-02-07 10:49:08' } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 28325] New: Build Mojolicious controller replacement for tools-home.pl
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '23

07 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 Bug ID: 28325 Summary: Build Mojolicious controller replacement for tools-home.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As per an email to koha-devel, I'm going to take the core Mojolicious code from Bug 26791, and try implementing it with a much simpler controller to replace tools-home.pl. The key prerequisites for the controller are authentication, authorization, and template rendering. It may be necessary to split out other bug reports to focus on refactoring Koha's existing code, rather than bolting an alternative onto Koha, which could just create maintenance woes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[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 32508] New: Translation gives incorrect menu text in system preferences
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '23

07 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32508 Bug ID: 32508 Summary: Translation gives incorrect menu text in system preferences Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: eb(a)efdss.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 144743 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144743&action=e… A partial list of the system preference menus with incorrect text Also in 22.11. This applies to English United Kingdom (en-GB) I don't know if it applies to other translations. Many, but not all of the system preferences are displaying incorrect menu items. For instance in the pulldown menu for UsageStatsCountry the list is almost entirely 'religious organization'. If I switch the system to English (en). Everything displays as expected. The OPAC and staff interface seem to be unaffected. I have attached a partial list of the menus. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[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