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

[Bug 35353] New: Add api endpoint to fetch patron's previous holds
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '24

13 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35353 Bug ID: 35353 Summary: Add api endpoint to fetch patron's previous holds 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: kyle(a)bywatersolutions.com CC: tomascohen(a)gmail.com We have an endpoint to fetch a patron's current holds ( /api/va/patrons/$id/holds ) but some external services need to get previous holds to see if they were completed/canceled/etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 17318] New: Make 'Normalization rule' configurable on matchpoint definition
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '24

12 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17318 Bug ID: 17318 Summary: Make 'Normalization rule' configurable on matchpoint definition Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently, there's a free text field on matchpoint definition, that is of no use, as the code does some default normalization no matter what you put there (se screenshot). As pointed out on 17304 and other bugs, this normalization routine is counter productive. The purpose of this bug is to introduce a way for defining the normalization rules we'd like to apply. IT will make use of bug 17302 to have a small (but useful) list of normalization routines. This could be expanded if needed, or we could even make plugins do it (that'd certaintly belong to another bug report). I don't think removing the 'feature' is a good move now, but we could consider it with broader discussion. Someone should rise it in koha-devel, meetings, etc. This will provide a way out, until we end that fine-grained discussion. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 20558] New: typo mts_authorized_value vs mts_authorised_value in admin/marctagstructure.pl
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '24

12 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20558 Bug ID: 20558 Summary: typo mts_authorized_value vs mts_authorised_value in admin/marctagstructure.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org What are the consequences of this? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 34953] New: Create page layout templates for CMS pages
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '24

12 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34953 Bug ID: 34953 Summary: Create page layout templates for CMS pages 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org It would be helpful to select a page layout that would insert some HTML into the CMS pages editor, and librarians could make their cusotmisations within that template. For example, a 3 column page, a 2 column page, a webform, etc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 22258] New: Elasticsearch - full record is not indexed in plain text
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '24

12 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22258 Bug ID: 22258 Summary: Elasticsearch - full record is not indexed in plain text 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 Target Milestone: --- This is to start a discussion - at some point we dropped the inclusion of the full record in plain text in the ES index A consequence is that data in a field that is not specifically indexed is no longer searchable. This is a change from zebra I believe where the entire record can be searched. I am not sure of the affect on relevancy, but I think we need t o find a way to support full record searching. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 37453] New: The new item-status.inc include should be used throughout the staff client
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '24

10 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37453 Bug ID: 37453 Summary: The new item-status.inc include should be used throughout the staff client Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We introduced a new item-status include in bug 28762; We should try to utilise it everywhere we can rather than having all the local different copy/pastes we have. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 35994] New: Need a easy way to see if biblio record or item is still in acquisition
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '24

09 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35994 Bug ID: 35994 Summary: Need a easy way to see if biblio record or item is still in acquisition Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org See also bug 35993. Checking for 005 would not be a good way to approach this question. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 37788] New: in UNIMARC 099$t and 995$h sould not both be indexed in ccode
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '24

08 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37788 Bug ID: 37788 Summary: in UNIMARC 099$t and 995$h sould not both be indexed in ccode Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org 099$t and 995$h are both indexed in ccode. I believe this is not good, as those two fields can contain different values. Is it possible to create a distinct index for 099$t ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36651] New: Add hint text in the search bar in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '24

08 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36651 Bug ID: 36651 Summary: Add hint text in the search bar in the OPAC 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I had this suggestion during a training yesterday. Some people were saying it was not obvious what the search bar was meant for, and it was suggested that maybe putting a hint text in the search bar would help understand. (Similar to the wiki search box https://wiki.koha-community.org/wiki/Main_Page, it says "Search Koha wiki" and when you start typing this text disappears.) It could be customizable, but the default could be something like "Search the library catalog". -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 23305] New: Add ability to append to item notes in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '24

08 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23305 Bug ID: 23305 Summary: Add ability to append to item notes in batch item modification Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It'd be useful to be able to append new text onto the end of itemnotes and itemnotes_nonpublic when performing a batch item modification, rather than simply overwriting any existing notes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17