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

[Bug 21330] New: Add xslt for authority normal view in OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21330 Bug ID: 21330 Summary: Add xslt for authority normal view in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, It would be fine to have a xslt stylesheet for authority normal view in OPAC (opac-authoritiesdetail.pl). Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 74

[Bug 27793] New: Store Contents of FTX segment of EDI quotes for inclusion in orders
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27793 Bug ID: 27793 Summary: Store Contents of FTX segment of EDI quotes for inclusion in orders 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: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A number of vendors send data in the FTX segment of EDI quotes, and expect this to be returned in the subsequent order. This may indicate the form of item to be supplied (electronic v physical book) or data entered to indicate that the order is the result of a special request. The standard is somewhat misleading on this as it encourages use of FTX for encoded delivery priority info. However this appears to be obsolete in practice and examination of numerous quotes show no suppliers using it this way, whereas some suppliers (e.g. proquest) are making the contents of this segment fundamental to their procedures ensure FTX content is saved (in vendornote) and that the saved note is included in an order sent as a result of the quote -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 23838] New: Add ability to view item renew history
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23838 Bug ID: 23838 Summary: Add ability to view item renew history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It should be possible, when viewing a patron's circulation history, to view details of an item's renewals. Each renewal should be displayed as: Renewed on <renewal date> by <renewed by> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 119

[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 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 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 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