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

[Bug 34270] New: Upgrade and prune jQueryUI assets in the staff interface
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34270 Bug ID: 34270 Summary: Upgrade and prune jQueryUI assets in the staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 34114 With the elimination of our dependency on jQueryUI Sortable by Bug 34114 we will be left with only autocomplete as a jQueryUI dependency. We can trim down our jQueryUI assets to reflect this and upgrade at the same time. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34114 [Bug 34114] Replace the use of jQueryUI sortable -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 35007] New: Self checkout system (SCO) - table heading row background colour in tabs is inconsistent
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35007 Bug ID: 35007 Summary: Self checkout system (SCO) - table heading row background colour in tabs is inconsistent Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org In the OPAC self checkout system, the tables in the tabs (such as Checkouts, Holds, and Charges) have different header row colours. For the checkouts tab, the header row is consistent with other tables in the OPAC. For the other tabs (such as Checkouts and Holds), the table heading row has a white background. To replicate (using KTD): 1. Enable the SelfCheckInModule and WebBasedSelfCheck system preferences (if not already enabled). 2. Check out some items to the koha user. 3. Place some holds for the koha user. 4. Add a charge to the koha user (Patrons > koha (42) > Accounting > Create manual invoice). 5. Go to the self checkout system page: <yourlocalhostname>:8080/cgi-bin/koha/sco/sco-main.pl 6. Log in as the koha user 7. Note that: - for the Checkouts tab: the table has a coloured background and looks consistent with other tables in the OPAC - for the other tabs (Holds and Charges): the table heading row for both tables has a white background -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 35631] New: Default Z39.50 target syntax to match sys pref marcflavour
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35631 Bug ID: 35631 Summary: Default Z39.50 target syntax to match sys pref marcflavour Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When setting up a new Z39.50 target, the Syntax currently defaults to UNIMARC. It would be really helpful to have it default to whatever the system preference marcflavour is set to (UNIMARC or MARC21). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 26586] New: Koha should return a SIP2 64 response to a 63 request for fee items
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '24

13 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26586 Bug ID: 26586 Summary: Koha should return a SIP2 64 response to a 63 request for fee items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com At the moment, we're supporting SIP 2.0 for the 63 Patron Information Request, but the 3M SIP2 Protocol Extensions outlines a 7th position "fee items". If a SIP2 client sents a Y in that position, Koha will close the connection. At the very least, it should just return a 64 response and just not send any fee item info back. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 35247] New: Add new route to simply list old reserves by patron id
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '24

13 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35247 Bug ID: 35247 Summary: Add new route to simply list old reserves by patron id 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: thibaud.guillot(a)biblibre.com CC: tomascohen(a)gmail.com Hi everyone, I purpose to add a new endpoint to list all old reserves by patron id. The definition is the same than "hold" definition and it just a new route to display old reserve for see cancellation reason or cancellation date for example. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[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 11 Nov '24

11 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