September 2020 - Koha-bugs - lists.koha-community.org

[Bug 20388] New: Elasticsearch - Ability to add index from UI
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20388 Bug ID: 20388 Summary: Elasticsearch - Ability to add index from UI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com Currently indexes only coming from mapping.yaml. We need to add some using UI (admin/searchengine/elasticsearch/mappings.pl) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 213

[Bug 23840] New: Overlap of top menu
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23840 Bug ID: 23840 Summary: Overlap of top menu Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: fraktik(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 94403 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=94403&action=ed… picture of graphical overlap of top menu For more then one or two SHORT links in IntranetNav variable in Staff Client Preferences (Appearance) and variable window size there is some interval of page width, when an visual overlap between top menu from the right one (user/library related & Help) to the left one(general) happen. In previous version this do not happen (right menu jump one row down instead). Examples of both is shown in an attachment: 19.05: https://i.imgur.com/4aVrcRt.png 18.11: https://i.imgur.com/y4iJeMD.png -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 18194] New: Elasticsearch should be able to add new indexes
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18194 Bug ID: 18194 Summary: Elasticsearch should be able to add new indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 14899 added a configuration page for elastic search indexes. It would be nice to allow for the addition/deletion of indexes as well as their configuration -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 23357] New: overdue_notices.pl can send library doubled emails for patrons with no email/sms if both transports enabled
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23357 Bug ID: 23357 Summary: overdue_notices.pl can send library doubled emails for patrons with no email/sms if both transports enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz In overdue_notices.pl we have a check to avoid sending a patron two notices if they are missing an email address and an sms number, however, we don't apply this check to generating the notice content and so send the library the same info twice -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 23497] New: Notices defaulting to print
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23497 Bug ID: 23497 Summary: Notices defaulting to print 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Why is it that Koha defaults to printing? Shouldn't the default be no notification, and we have to select which notices are printed, if any? Right now, if a patron doesn't have an e-mail selected as the form of notification, the notice defaults to print. I would like to suggest that a print column be added, and if nothing is checked, nothing is generated. Maybe in the notices tab for the patron a place holder could be made saying that patron opted for no notification, or something like that? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 23558] New: REST API: Get an ILL request
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23558 Bug ID: 23558 Summary: REST API: Get an ILL request 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: black23(a)gmail.com Method GET /ill_requests/{ill_request_id} https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22440] New: ILL API response objects inconsistent with other endpoints
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22440 Bug ID: 22440 Summary: ILL API response objects inconsistent with other endpoints Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- The response object returned from the /api/vi/illrequest GET route isn't consistent with response objects supplied by other routes, such as the patrons route. We have an RFC for this route here: https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC Josef has made some initial recommendations on what the properties should be named to make them consistent with other routes. We could do with expanding this RFC to make it complete, including a spec on how object embedding should be done since, to date, this is the only route that does this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 66

[Bug 23557] New: REST API: Add ILL request
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23557 Bug ID: 23557 Summary: REST API: Add ILL request 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: black23(a)gmail.com Method POST /ill_requests https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 26477] New: Emaillibrarianwhenholdisplace may be change to specify email as per library choice
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '24

04 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26477 Bug ID: 26477 Summary: Emaillibrarianwhenholdisplace may be change to specify email as per library choice Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: mishravk79(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Hello Emaillibrarianwhenholdisplace may be more helpful if we make it customisable as per choice of the library. It will help library to specify the email of librarian who is dealing with Hold related services in the library. Thanking You -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 23984] New: Local cover 'thumbnail' size is bigger than 'imagefile' size in biblioimages table
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '24

04 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23984 Bug ID: 23984 Summary: Local cover 'thumbnail' size is bigger than 'imagefile' size in biblioimages table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: arouss1980(a)gmail.com, jonathan.druart(a)bugs.koha-community.org, lucas(a)bywatersolutions.com, magnus(a)libriotech.no, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, tomascohen(a)gmail.com Depends on: 21987 Blocks: 23963 The original resolution to this issue, bug 21987, caused a nasty regression and has since been reverted. Opening this bug so we may pursue a new route to goal. +++ This bug was initially created as a clone of Bug #21987 +++ We use local cover images in our setup, and also resize the covers we scan to a width of 160px before uploading and attaching them to a Koha bibliographic record (we upload one cover per biblio). While using phpMyAdmin to view the contents of the 'biblioimages' table (relevant screenshot here: https://imgur.com/a/cSEVLBI) we noticed that the size of the BLOBs for the 'thumbnail' column was in some cases twice as big as that of the 'imagefile' column. In fact, this happens for more than 50% of uploaded covers as you can see from the output of the SQL queries below: mysql> SELECT COUNT( * ) AS count FROM biblioimages WHERE LENGTH( thumbnail ) > ( LENGTH( imagefile ) * 2 ) ; +-------+ | count | +-------+ | 1356 | +-------+ mysql> SELECT COUNT( * ) AS count, SUM( LENGTH( imagefile ) ) AS images_size, SUM( LENGTH( thumbnail ) ) AS thumbnails_size FROM biblioimages ; +-------+-------------+-----------------+ | count | images_size | thumbnails_size | +-------+-------------+-----------------+ | 2347 | 68323933 | 115839686 | +-------+-------------+-----------------+ It would appear that for each 160px-wide JPG with 24-bit depth that we have uploaded, the 'imagefile' column has been populated with an PNG of 8-bit depth with the same dimensions as the uploaded file, whereas the 'thumbnail' column contains a 24-bit PNG image with a width reduced to 140 pixels. I've tracked down the creation of resized 24-bit PNGs to this code: https://github.com/Koha-Community/Koha/blob/master/C4/Images.pm#L182-L183 Do thumbnails for covers need to be true colour (24-bit) images? Also, why is it that _scale_image() returns an image of 8-bit depth if the source image's dimensions are less than 600x800? (i.e. when no resizing is performed) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21987 [Bug 21987] Local cover 'thumbnail' size is bigger than 'imagefile' size in biblioimages table https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23963 [Bug 23963] Visible reduction in image quality -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6