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

[Bug 20443] New: Move C4::Members::Attributes to Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '24

16 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20443 Bug ID: 20443 Summary: Move C4::Members::Attributes to Koha namespace 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 119

[Bug 25395] New: Enumchron needs to sort numerically
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '24

16 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25395 Bug ID: 25395 Summary: Enumchron needs to sort numerically 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: mkstephens(a)lancasterseminary.edu QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is a follow-up to bug 13420. 13420 was resolved by changing the sort for serials items. The underlying issue with enumchron still exists and affects all items in multi-volume series (not just serials). Is it possible to sort this field numerically by whole number first and then alphabetically? Part of the solution needs to include escaping prefixes like v., vol., no., etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 34842] New: t/db_dependent/Illrequest/Config.t is failing is the DB has been upgraded
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '24

15 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34842 Bug ID: 34842 Summary: t/db_dependent/Illrequest/Config.t is failing is the DB has been upgraded Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Test Suite Assignee: pedro.amorim(a)ptfs-europe.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 32911 Blocks: 34841 There is a lot of failures: # got: 'ILLLIBS' # expected: 'IL' I think we should adjust the atomic update from bug 32911 and set the syspref to "IL" if the config was "ILLLIBS". What do you think Pedro? To recreate: root@kohadevbox:koha$ perl /kohadevbox/misc4dev/run_tests.pl --run-db-upgrade-only kohadev-koha@kohadevbox:koha$ prove t/db_dependent/Illrequest/Config.t Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32911 [Bug 32911] Remove ILL partner_code config from koha-conf.xml and turn it into a system preference https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34841 [Bug 34841] The test suite is failing is the DB has been upgraded -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 32911] New: Remove ILL partner_code config from koha-conf.xml and turn it into a system preference
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '24

15 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32911 Bug ID: 32911 Summary: Remove ILL partner_code config from koha-conf.xml and turn it into a system preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com CC: katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com Depends on: 21548 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21548 [Bug 21548] ILLLIBS patron category / partner_code seems extraneous -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 34584] New: Remove Twitter share button from the OPAC
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '24

15 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34584 Bug ID: 34584 Summary: Remove Twitter share button from the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Since Twitter doesn't exist anymore we should remove its share button from the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 26195] New: Add a way to specify authorised values should be expanded [OAI]
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '24

15 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26195 Bug ID: 26195 Summary: Add a way to specify authorised values should be expanded [OAI] Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It is not uncommon to prefer descriptions to codes when exposing the library data through OAI. I propose we add a configuration option (off by default) that allows such a thing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 17536] New: Remove Duplication of receipting code in EDI
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '24

15 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17536 Bug ID: 17536 Summary: Remove Duplication of receipting code in EDI 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 When the Current Koha/EDI.pm was written the api to Acquisitions::ModReceiveOrder was unstable as a result the process was duplicated in Koha::EDI as the interface has stabilised EDI should revert to using the Acquisitions interface and remove the duplicate code. This should guard against bugs from incompatibilities and allow it to take advantage of enhancements in C4::acquisitions (e.g. new handling of Standing Orders) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 29450] New: Allow flatPickr to instantiate in any order
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '24

15 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29450 Bug ID: 29450 Summary: Allow flatPickr to instantiate in any order Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Currently, we automatically instantiate a flatPickr instance for any input fields that have the flatpickr class. This instantiation is handling within a loop and works well in most cases. However, if the the input is paired so we have a start/end date pair and the start date is pre-populated with the template you are faced with javascript errors. This is because the pre-populated value triggers our onClose function that resides in the instantiation settings. The onClose looks for the associated 'end' input and grabs the flatpickr instance to set the minDate property.. but as we've not yet hit the end input field the flatpicker instance for that field doesn't yet exist. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 26802] New: Improve speed with records with many items
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '24

14 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26802 Bug ID: 26802 Summary: Improve speed with records with many items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org Koha has a performance problem displaying records with many items in search results and details pages. For example, Koha takes around 20/30 seconds to process a record XML with 1000 items using XSLT. The Koha's response speed reduces even more with bigger items counting. Maybe we can improve Koha speed with some decisions: - Don't use the complete XML (record without items) for XLSTs processing. - Add pagination to the items table (like is done with other Koha tables) and JS load. Test case (search results): - Add some records with 1000 items and the same title - Try to do a search for the title Test case (details and other record views): - Add one records with 1000/2000/3000 items - Try to open the record -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 35896] New: Items from Unimarc sample data do not contain itemtype
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '24

12 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35896 Bug ID: 35896 Summary: Items from Unimarc sample data do not contain itemtype Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibault.keromnes(a)univ-paris8.fr QA Contact: testopia(a)bugs.koha-community.org If you create a new sandbox with Unimarc, the items in the sample data have no itemtype (which is now mandatory) Left empty it now breaks the Opac details page (see BZ 32747) so if you don't know about it you cannot test a unimarc patch on the opac. Wasn't sure which component and severity to choose, so feel free to change it -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7